Loading…
Loading…
What gatehousewp.com collects, why, and how to get it deleted: account and payment information, your site addresses, and the optional Cloud settings and shared rules you choose to manage. Visitor activity records stay on your sites.
Checkout and payment are processed by Stripe. Your card details go to Stripe and never touch our servers. We receive your email address, your name (if you provide it), and a Stripe customer reference so we can show your invoices and manage your subscription.
Signing in needs only your email address: we send you a one-time code (delivered through our email provider, Resend) and keep you signed in with a session cookie for up to 30 days. These sign-in services are run by Stytch. We keep a record of account activity (sign-ins, licence and billing changes) for security and support.
To activate a license we store the license key and the address of the site you activate it on, plus whether that site is a production, staging or local environment. You can free a site from your account at any time; deleting your account removes your licenses and site records.
Gate House Free does not contact gatehousewp.com for updates or install tracking. Gate House Pro and the complete legacy edition check for private updates only when a license key is saved. Those requests contain the site address, plugin version, environment type, product slug and license key. We keep a service record per site and delete it after about thirteen months of silence. Older clients may still send anonymous checks; those receive compatible responses but are no longer recorded as installs. We do not store IP addresses for this, and the key is never sent in a URL.
The plugin can send a once-a-day setup report: which provider and forms are configured, software versions, and two activity totals. It is off by default, needs your administrator’s explicit opt-in, shows you its exact contents before you opt in, and stops the moment you untick it. It never contains visitor data.
Your signed-in Cloud dashboard shows your activated sites and their optional setup reports. It uses the versions, configuration flags and aggregate counts already described above. Reports describe the latest submitted settings, not live uptime or individual visitors. Cloud email alerts are a separate, off-by-default preference in your account; when enabled, they go only to your account address and can be turned off there.
Cloud Reports reuse your optional aggregate setup reports and the outcomes of changes you requested. You can filter your sites, review reporting gaps and download CSV files from your account. Activity trends are daily averages of reported trailing windows; they are not exact daily totals or individual visitor records.
You can save client names and assign your connected sites to them for private dashboard views and report downloads. These labels belong to your account. Creating a client does not invite anyone or send email; the owner can separately grant teammates access to selected clients. Reports follow current assignments, including earlier site history. Client filters do not change your account-wide email preferences.
Account owners can prepare and explicitly publish reports for one client portal. A report stores the selected site addresses, approved reporting period, aggregate activity averages, setup and reporting coverage, safe protection-change outcomes, and the title, agency name and notes supplied by the owner. Drafts stay private. Reports exclude raw visitor records, provider credentials, rule values, staff identities and billing details.
Client recipients have separate email-bound portal invitations. We store the invited address, client, expiry, delivery status and acceptance or revocation dates; only a hash of the seven-day invitation token is stored. Recipients must verify their email and explicitly accept. Each read and download checks current access and publication. Site reassignment or loss of ownership makes the affected report unavailable. Owners can unpublish reports and revoke access; files a recipient has already downloaded cannot be recalled. Client invitations do not enable account alerts, weekly summaries or optional client report emails.
For scheduled reports, the agency owner separately reviews and approves a fixed selection of sites, branding and notes for automatic future preparation and publication. Accepted client recipients choose their own optional schedule: weekly, monthly, or twice a month on the 1st and 15th. Email starts off and can be stopped in the portal or through an explicit confirmation link without signing in. Opening that link alone changes nothing. Emails contain a reporting period and authenticated report link; private site details, metrics and notes stay in the portal. A message already handed to the provider cannot be recalled.
Account owners can invite teammates by email as Viewers or Operators, with access to all clients or selected client groups. We store the invited email, role, client permissions, invitation expiry and delivery status, and acceptance or revocation dates. Invitation links expire after seven days and require a matching verified sign-in plus explicit acceptance. We store a hash of the invitation token.
Teammates can view permitted site details and aggregate reports, including earlier reports for sites currently assigned to their clients. Operators can also see the current managed settings and Cloud rules for permitted sites, and review and apply versions the owner explicitly shares. Saved versions are private by default. Team access does not give teammates the owner’s billing records or license keys. Account-wide alert and weekly-summary emails remain separate owner preferences.
We record which account owner, teammate or site requested a management change. Owners can see the requesting teammate in command history. Revocation stops new access and pending delivery, but cannot recall a change already sent to WordPress. Teammates may leave an account from their Cloud access page.
A WordPress administrator can separately enable Cloud management for an eligible licensed site. We then receive the site address, plugin version, selected local attempt-limit and account-abuse settings, and the results of configuration changes you request. Each connection uses a separate management credential; the service stores its hash. Settings templates and their rollback snapshots contain only these selected settings. Shared rule lists require the additional consent described below. Provider credentials and visitor records are excluded. Your account controls its templates and selected-site rollouts. Turning management off in WordPress stops application there immediately; a Cloud disconnect cannot recall a change already delivered to the site.
You can create shared lists of IP addresses, IP ranges and email domains in your account. We store the rule values and actions you enter, list names and saved versions so you can review and apply them to selected sites. Each WordPress site must separately enable shared-rule management before we receive its current Cloud-managed rules, local rule count and application results. Its local rule values, visitor activity and provider credentials are not uploaded.
Turning shared-rule management off stops new rule application and erases that connection’s current rule snapshot from Cloud when the site reaches the service. Existing protection stays on the site until you explicitly remove its Cloud rules. Deleting a library list does not uninstall it from sites: it removes the saved list versions and completed raw rule-history snapshots, while minimal status and hash receipts remain for acknowledgement retries. Active consenting sites can continue to report their installed shared rules. Pending changes must finish or be cancelled before the list can be deleted.
We send transactional email only: your license key, sign-in codes, receipts and payment-failure notices, Cloud team and client portal invitations requested by account owners, Cloud health alerts and weekly summaries when you enable them, scheduled client report notifications when recipients choose them, and replies when you write to us. No newsletters unless you ask.
Weekly Cloud summaries have their own off-by-default account preference, separate from health alerts. They cover eligible production sites and go only to your account address through Resend. Turning them off cancels queued summaries; it cannot recall an email already being sent. Page filters do not change which sites are included in email.
Two functional cookies at most: your sign-in session, and a short-lived one while a sign-in code is pending. The store also loads Google Analytics to measure, in aggregate, which pages and offers people use: its _ga cookies distinguish one browser from another and last up to two years. That is measurement of this website only — no advertising, no profiling, no cross-site tracking, and nothing at all from your customers’ visits to your site: the plugin never loads it.
The store runs on Vercel with its database on Neon, sign-in on Stytch, email on Resend and payments on Stripe. Each processes your data only to provide its part of the service.
Email support@gatehousewp.com to access, correct or delete your data, or to close your account. We respond within 30 days and will tell you what we deleted. If you are in the EEA or UK, you also have the right to complain to your local data protection authority.
The plugin readme describes external service calls. Pro’s License tab also shows the exact optional setup-status payload before you consent. Without a saved license, new plugin versions send no private update requests or daily install check-ins.