CipherSEO takes privacy seriously. This policy explains what data we collect, why we collect it, and what we do with it. The short version: we collect the minimum needed to run scans and deliver reports, we don't sell anything to anyone, and we don't want your data any more than you want us to have it.
When you use the free scan, we process the URL you submit and the public content of that page. When you purchase the fix report, our payment provider collects your email address and payment details.
We do not collect names, phone numbers, addresses, or anything else we don't need. There are no accounts, so there are no passwords to leak.
We do not sell your data, share it with advertisers, or use your email for marketing you didn't ask for. If we ever launch a newsletter, it will be opt-in, with a working unsubscribe link.
CipherSEO uses the following third-party services to operate. Page content you submit is shared with them only to the extent needed to produce your report:
Each provider receives only what it needs: the AI sees page text, the screenshot service sees the URL, the payment provider sees the payment. Nobody gets the whole picture except us, and we barely want it.
Depending on where you live (GDPR in the EU/UK, CCPA in California, and similar laws elsewhere), you may have the right to access, correct, delete, or export the personal data we hold about you, and to object to or restrict certain processing.
In practice, since we hold almost nothing: email [email protected] and we'll show you what exists, delete it, or hand it over — usually within a few days, not the statutory thirty. We will never discriminate against you for exercising a privacy right.
CipherSEO sets exactly one cookie: an anonymous random ID (httpOnly, 1-year expiry) that tracks whether your free scan has been used and links your paid report to your browser. It contains no personal information and tracks you across exactly zero other websites.
There are no advertising cookies, no cross-site trackers, and no 47-toggle consent banner — because we didn't put anything in your browser worth a banner. Cloudflare's bot protection may set its own functional cookie during the security check; that one belongs to Cloudflare.
If we change this policy, we'll update the date at the top. If we ever change it in a way that matters — new data collected, new ways it's used — we'll say so plainly rather than burying it in clause 14(b)(iii).
Privacy questions, data requests, or anything else: [email protected] — or use the help page. A human (the only one here) reads everything.