Privacy

When you visit a page that Spectare personalises, it reads the signals your browser already sends: the referring page, campaign parameters in the URL, and which page you are on. An AI model classifies those signals into an audience and a buying stage, and the page is assembled to match. The classification is kept against the signal pattern, shared by every visitor who arrives the same way. No account of who you are is created or kept.

What Spectare deliberately does not do for visitors:

• No tracking cookies. Visitors to spectare.ai receive no cookie from us at all.
• No visitor profiles, no fingerprinting, no cross-site tracking of any kind.
• No sale or sharing of visitor data with advertisers. There is no ad tech on this site.

Your browser does keep a small amount of first-party state on your own device, in localStorage and sessionStorage: the list of pages you have visited on this one site (so a return visit can be recognised as a pattern, not as a person), and short-lived tokens that let a later page attribute a signup or purchase to the content you actually saw. This state never leaves your device except as part of those requests, expires on its own, and contains no name, email, identifier, or anything from other websites.

Images on personalised pages are delivered from Cloudinary’s CDN. Like any image host, it receives the standard request your browser makes to fetch a file (IP address, browser type); it sets no tracking cookies for delivery and receives nothing about who you are, because we have nothing to send.

On WordPress sites using Spectare’s server-side zones, the site owner can opt in to one first-party cookie that mirrors that page list so their server can see it. It is off by default, set on the site owner’s own domain, and documented in the plugin settings.

spectare.ai uses Cloudflare Web Analytics, which is cookieless and does not fingerprint or track visitors across sites. We see aggregate page views, referrers, and performance timings, never individuals.

If you create a Spectare workspace, we process what running the service requires:

• Account: your email address and sign-in, handled by Clerk, our authentication provider. Signing in sets strictly necessary session cookies; these exist only for logged-in users and are exempt from consent requirements because the service you asked for cannot work without them.
• Billing: payment details are handled by Stripe. We never see or store card numbers.
• Content: the atoms, images and settings you put into your workspace, stored so we can serve them. They are yours: edit or delete individual pieces at any time in the admin, and ask us to export or remove everything.
• Aggregate performance data: impression and conversion counts per piece of content and arrangement, kept as counters against signal patterns, not against people.
• Email: account email only, sign-in codes from Clerk and billing receipts from Stripe. We run no email platform of our own and no marketing lists you did not join.

Processing happens on infrastructure provided by Google Cloud, Neon (database), Upstash (cache), Cloudinary (images), Cloudflare (network), and Anthropic (AI models). Visitor signal summaries are sent to the AI model for classification; they contain the page, referrer and campaign context described above, and no visitor identity, because none exists.

Like every web service, our infrastructure keeps short-lived request logs, which include IP addresses, for security, rate limiting and abuse prevention. Rate limits key on the connecting IP and forget it; logs rotate out on the providers’ standard schedules.

For workspace data: ask and we will export or delete it. For visitor data: there is nothing to look up, because visitor records do not exist; the state on your device is yours to clear like any site data. If you believe we hold personal data about you, or have any question about this page, write to [email protected] and a human will answer. You also have the right to complain to your data protection authority.

If what we store changes, this page changes first, with the date above updated. We will not quietly widen what is collected.