Privacy Policy

BroadSite serves two different groups, and it matters which one you are:

• Account holders — people who sign up for BroadSite and publish sites. When we handle an account holder's own information (their email, their content), we act as the controller of that information.
• Site visitors — the public who visit a site published by an account holder. When a visitor submits a form on a published site, we collect that submission on behalf of the account holder who owns the site. For that visitor data we act as a processor — the account holder is the party who decides what to collect and why, and the account holder is responsible for having a lawful basis, giving notice, and honoring the privacy rights of their own visitors. If you are a visitor with a question about your data on a specific site, contact the owner of that site; we will support them in responding.

Account information (via Clerk). Sign-in and identity are handled by our authentication provider, Clerk. Through Clerk we receive and store your account email address and an account identifier, and we store your current plan. Clerk collects and processes your authentication details under its own privacy policy.

Billing information. Paid-plan billing is handled through Clerk and its payment processor. We never receive, store, or process your full payment-card number. We store only your plan and subscription status, which drives what your account can do.

Your site content. We store the HTML of the pages you publish, along with version history for those pages, and any images you upload for use on your sites.

Form submissions (collected for site owners, from their visitors). When a visitor submits a native form on a published site, we store the fields that form collects (for example, a name and email address the visitor typed) so the site owner can see them in their dashboard. Alongside each submission we store a one-way hashed version of the visitor's IP address (hashed with a server-side salt; the raw IP is never stored) used only for abuse-prevention and rate-limiting. We retain up to a fixed number of the most recent submissions per site (see Section 7, Data retention). As explained in Section 1 (A note on two kinds of people, and who is responsible), this data belongs to the site owner's relationship with their visitors; we hold it for them.

Images. Images you upload are stored in object storage operated through our hosting provider. Image files are served as-is from storage; we verify an uploaded file's real type and do not accept formats that could carry executable content.

Server logs and technical data. Like any web service, our servers generate operational logs (such as request metadata and errors) used to run, secure, and debug the Service.

No advertising trackers from us. BroadSite does not run advertising or analytics trackers on our own dashboard, and we do not sell personal information. Note, however, that on paid plans an account holder may add their own analytics or tracking scripts (for example, Google Analytics or a Meta Pixel) to the pages they publish. Those are the account holder's choice and the account holder's responsibility toward their visitors — not ours.

Published-page measurement (aggregate only). Published pages include a small first-party script that reports anonymous, aggregate interaction counts to the site owner — for example, page views, scroll depth, time on page, clicks on links and buttons, and whether a form was started. This script creates no identifier, sets no cookie and no local storage, does not follow visitors across sites, and is never sold or shared. What we store is a daily count per site, not a record of any individual visit. When a visitor arrives with campaign parameters (such as utm_source, gclid, or fbclid) or from another site, we also record the campaign or referring-site label as part of those daily counts, and attach that label to a form submission so the site owner knows which campaign produced the lead — again without creating any visitor identifier. As with form submissions (Section 1), these aggregate counts are produced for the site owner.

We use the information above to:

• provide, operate, and maintain the Service — authenticate you, publish and serve your sites, and show you your form submissions;
• process subscriptions and manage plans and billing through Clerk;
• protect the Service — prevent and investigate abuse, fraud, spam, and security incidents, and enforce our Terms and Acceptable Use Policy (this includes serving the report link on every page and reviewing reports);
• communicate with you about your account and the Service; and
• comply with law and respond to lawful requests.

Depending on where you live, you may have rights over your personal information — for example, to access, correct, delete, or export it, or to object to or restrict certain processing. Where we process account-holder personal data, we rely on the bases of performing our contract with you (running your account), our legitimate interests (securing and improving the Service, preventing abuse), and compliance with legal obligations. We are a small company and are not established in the EU, but we aim to honor reasonable requests consistent with applicable privacy laws (including the GDPR and the CCPA/CPRA where they apply).

To exercise any right, email support@broadsite.app from the address associated with your account. If your request concerns data on a site published by someone else (that is, you are a site visitor), please contact that site's owner; we will assist the owner as a processor.

Our two domains behave differently, on purpose:

• broadsite.page (your published sites) sets zero cookies. Published pages are served cookieless — no BroadSite cookies of any kind. Published pages also store no localStorage, no sessionStorage, and no device identifier of any kind from BroadSite. (An account holder on a paid plan could add their own scripts that set cookies; that is the account holder's choice and responsibility, not something BroadSite does.)
• broadsite.app (the app) uses a session cookie from Clerk so that you can stay signed in to your dashboard. This is a strictly necessary authentication cookie, not an advertising cookie. We do not use third-party advertising or cross-site tracking cookies.

We do not sell your personal information and we share it only as needed to run the Service, with the providers below and as required by law.

We may also disclose information where we reasonably believe it is necessary to comply with law or legal process, to enforce our Terms, or to protect the rights, safety, or property of BroadSite, our users, or the public — including preserving evidence and reporting to authorities as described in our Terms (for example, mandatory reporting of child sexual abuse material). If BroadSite is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction, subject to this Policy.

• Live account data is retained while your account is active.
• Form submissions are retained on a rolling basis — we keep up to the most recent 500 submissions per site, and older submissions are pruned automatically as new ones arrive.
• Aggregate daily counts — the published-page measurement described in Section 2 (page views, scroll/engagement/click counts, and campaign attribution) — are kept for the life of the site and deleted with it.
• Account deletion is an archive, handled honestly. When an account is deleted — whether you delete it yourself through Clerk or we delete it — we do not immediately and irreversibly destroy all record of it. Instead, your account's live records are removed from our operational database (your sites stop serving right away), while we retain a complete archived snapshot of the account — its sites, page versions, image metadata, and form submissions — in our systems for our legitimate business, legal, security, and abuse-prevention purposes. We keep this so we can, for example, investigate abuse, meet legal obligations, and maintain records. We may delete or further reduce archived data over time.
• Images stored for a specific site are purged from object storage when that site is deleted.

If you need the archived snapshot of your account handled in a particular way to meet a legal right you hold, contact us at support@broadsite.app and we will respond consistent with applicable law.

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it. Note that content and forms published by account holders are their responsibility; an account holder who directs a site at children takes on the corresponding obligations.

We take reasonable measures to protect information, including transport encryption (HTTPS), strict isolation between the app domain and the domain that serves untrusted published pages, sanitization of free-tier pages, one-way hashing of visitor IP addresses, storing secrets outside of source control, and access-controlled, audit-logged administrative tools. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

If we become aware of a data breach affecting your personal information, we will notify affected users and applicable authorities as required by law, without undue delay.

We may update this Privacy Policy from time to time. When we do, we will post the updated Policy here with a new effective date and, for material changes, provide reasonable notice. Your continued use of the Service after an update takes effect means you accept the revised Policy.

Questions about this Policy, or to exercise a privacy right: support@broadsite.app.