Privacy Policy

SiteCue is a website builder operated by SiteCue (“SiteCue”, “we”, “us”, “our”). We are the data controller for the personal data described in this policy, except for the site-visitor data covered in section 5, where we act as a processor for our users.

This policy covers the SiteCue marketing site, the editor and dashboard, sites published on *.sites.sitecue.org, and any custom domain connected through SiteCue. Our contact details are at the end of this policy.

It matters which hat we are wearing, because it changes who is responsible for your data:

• We are the controller. for data about you as a SiteCue account holder or visitor to our own marketing site — your account, billing, the content you create, and support you request.
• We are a processor. for data that other people submit to the sites our users build — for example, someone filling in a contact form on a published SiteCue site. There, the SiteCue user who owns the site is the controller; we only handle that data on their instructions. See section 5.

• Account data. Your email address, display name, and avatar, plus the account identifier from our sign-in provider, Clerk. Authentication — including your password and any two-factor settings — is handled by Clerk, and SiteCue does not store your password. The one exception is deleting your account: to confirm it's really you, the password you enter is sent to Clerk for verification and is never stored.
• Workspace and billing data. Your plan, the specific plan option you bought, your account-balance ledger, and a record of each payment or plan change (amount, type, date, and a receipt link). Your card number and billing address are collected and held by our payment provider, Dodo Payments, as Merchant of Record — not by SiteCue. We keep a reference to your Dodo customer record and, if you turn on auto-renew, a token that points to your saved payment method.
• Your content. The pages, text, settings, and files (images, video, audio) you add to build your sites. Uploaded files are stored in Cloudflare R2. Anything you publish becomes publicly accessible by design.
• AI prompts (only if you use an AI feature). If you use SiteCue’s AI site generator, the prompt you submit is sent to our AI provider (Anthropic) to produce a result, and we keep a per-month count of how many generations you have run. Please do not put personal or confidential information into AI prompts.
• Support and contact. If you write to us or use a contact form, we receive what you send — your name, email, and your message — so we can reply.
• Technical and security data. To run, secure, and rate-limit the service, we and our infrastructure providers process technical data such as IP address and request metadata. This is used transiently for operation, abuse prevention, and (for site analytics) to compute a privacy-preserving session hash; we do not keep a long-term log of your IP address tied to your identity. Our error-monitoring tool (Sentry) is configured to strip IP address, email, and submitted form content before any error report is sent.

We do not use third-party advertising trackers on the SiteCue marketing site, we do not run advertising cookies, and we do not sell or “share” your personal data for cross-context behavioural advertising (as those terms are used under California law). We do not buy personal data from data brokers.

If you add your own analytics or tracking (for example Google Analytics) to a site you build, that tool is governed by its own provider’s privacy practices, not ours — see section 5.

When you publish a site with SiteCue, you decide what to collect from your visitors. For that data, you are the controller and we are your processor — we handle it on your behalf and on your instructions. Specifically:

• Form submissions. When a visitor submits one of your forms, we store what they entered, along with their IP address and browser user-agent (used for spam scoring and abuse prevention) and a daily-rotating session hash. We then deliver the submission to the destinations you configured — a built-in inbox, a webhook, or an email/marketing provider you connect (for example Mailchimp, Kit, or Resend). Credentials you connect are stored encrypted.
• Built-in site analytics. If you turn on SiteCue analytics for a site, we record aggregate visits without cookies: page path, referrer, approximate country and device, and UTM tags. Visitors are counted using a hash that is re-salted every day, so it cannot be used to track someone across days or across sites. Raw events are kept briefly and rolled up into daily aggregates.
• Third-party code you add. You can add your own analytics, embeds, custom scripts, or fonts to your published sites. When you do, the visitor’s browser talks to those providers directly; SiteCue does not proxy or store those requests. You are responsible for those tools, including any cookie banner, consent, and privacy notice your site needs. (By default, published sites may load fonts from Google; you can switch a site to serve fonts locally so visitor browsers never contact Google.)

If you are a visitor wanting to access, correct, or delete data you submitted to a SiteCue site, please contact the owner of that site — they control it. We will help that owner respond, and we offer business users a data processing agreement (DPA) on request.

Under the GDPR and UK GDPR, we rely on these legal bases:

• To provide the service (contract). Authenticating you, saving your edits, publishing and serving your sites, and providing support.
• To bill you (contract / legal obligation). Taking payment for the plan you choose, issuing receipts, and keeping the financial records the law requires.
• To keep the service safe and working (legitimate interests). Preventing abuse, fraud, and spam; rate limiting; debugging; securing accounts; and understanding aggregate, non-identifying usage so we can improve SiteCue.
• To communicate (legitimate interests / consent). Sending service, security, and billing notices (you cannot opt out of these while you have an account), and optional product updates (which you can opt out of at any time).
• To comply with the law (legal obligation). Responding to valid legal requests and meeting tax, accounting, and regulatory duties.

SiteCue’s own product uses only the cookies it needs to function — there are no advertising cookies on SiteCue:

• Sign-in (essential). Clerk sets cookies to keep you logged in and to protect against cross-site request forgery.
• Site unlock (essential). When a visitor enters the correct password for a password-protected site, we set a signed cookie so they are not asked again on every page.
• Anti-abuse (essential). Cloudflare Turnstile may set a token to tell humans from bots on forms and sign-in.
• Analytics consent (essential). On sitecue.org, a cookie named sc_consent remembers whether you accepted or declined analytics, for six months. Recording your choice is itself strictly necessary, so this cookie does not require consent.

On our own website, sitecue.org, we use Google Analytics to understand how visitors find and use SiteCue. It is off until you accept: no analytics script loads and no analytics cookie is set unless you choose Accept in the cookie banner. If you decline, no analytics cookies are set and the site works exactly the same.

Our built-in site analytics use no cookies at all. Because the essential cookies above are strictly necessary to deliver features you ask for, they do not require consent. Any other cookies on a published site come from tools its owner chose to add, and consent for those is the owner’s responsibility. SiteCue provides a cookie-consent element that site owners can add to their site to collect that consent from their visitors.

We share personal data only with the service providers that help us run SiteCue (“subprocessors”). Each is bound by a contract that requires it to protect the data and use it only to provide its service to us:

We may also disclose data when required by valid legal process (a subpoena, warrant, or equivalent), to protect our rights or users’ safety, or in connection with a merger, acquisition, or sale of the business — in which case we will require the recipient to honour this policy. Where the law allows, we will notify the affected account holder of a legal request.

SiteCue relies on providers located in the United States and elsewhere, so your data may be transferred outside your country, including outside the EEA and the UK. Where we do this, we rely on an adequacy decision where one exists, or otherwise on appropriate safeguards such as the Standard Contractual Clauses (and the UK Addendum) in our agreements with those providers.

• Account and content. For as long as your account is open. After you close it, we delete your account data and unpublish your sites within 30 days, except where we must keep something longer (below).
• Site analytics. Raw events are kept for about 30 days; daily aggregates are kept for about 12 months.
• Form submissions. Kept until you (the site owner) delete them or close your account.
• Billing and tax records. Kept for as long as tax and accounting law requires (often up to 6–7 years). Card details are retained by Dodo Payments under their own retention rules, not ours.
• Security and diagnostic data. Kept only briefly for the purpose for which it was processed.

You can request deletion of your account at any time from Settings → Delete Account; your account and all data associated with it (including all of your sites, account information, and account history) are permanently deleted 14 days after the request, and you can cancel at any time before then by logging back into your account.

Depending on where you live, you have some or all of the following rights over your personal data. We will not discriminate against you for using them.

• EEA / UK (GDPR & UK GDPR). Access, correction, deletion, restriction, objection, portability, and the right to withdraw consent at any time. You also have the right to complain to your local supervisory authority — in the UK, the Information Commissioner’s Office (ICO).
• California (CCPA/CPRA). The right to know what we collect and why, to access and delete it, to correct it, to limit the use of sensitive personal information, and to opt out of the sale or sharing of personal information. We do not sell or share personal information, so there is nothing to opt out of, but the right stands. You may use an authorized agent.
• How to exercise them. Use the controls in your dashboard where available, or contact us using the details below.

To make a request, use our contact page and choose “Privacy / data request”. We may need to verify your identity before acting, and we will respond within the time the applicable law requires. If your request is about data you submitted to someone else’s SiteCue site, contact that site’s owner (section 5).

SiteCue is not directed to children and is not intended for them. You must be old enough to agree to this policy and to our Terms in your country — in the EEA, at least 16 (or the lower age, down to 13, set by your member state); in the UK and United States, at least 13. We do not knowingly collect personal data from children below these ages. If you believe a child has provided us data, contact us and we will delete it. If you build a site directed at children, you are responsible for complying with the laws that apply to it.

We use encryption in transit (HTTPS), encryption at rest for stored secrets, salted key-derivation (scrypt) for site passwords, access controls, and reputable infrastructure providers. No method of transmission or storage is ever completely secure, so we cannot guarantee absolute security — but we work to protect your data and to notify you and the relevant authorities of a breach where the law requires.

We may update this policy. If a change is material, we will post the update at least 30 days before it takes effect and notify registered users by email. The date at the top shows when this version took effect. Continuing to use SiteCue after a change takes effect means you accept the updated policy.

For any privacy question or request, use our contact page.

If you are in the EEA or the UK and we do not have an establishment there, you may also be entitled to contact a local representative; if we appoint one, their details will be added here.