Privacy policy · updated 17 November 2026
your data, in plain words.
SEOAnything is run by the SEOAnything team at www.seoanything.dev. This page says exactly what we store and why. No legalese padding.
what we store
- Account: your email address, display name and avatar URL, as given by you or by GitHub/Google when you sign in. Passwords are stored as salted, peppered hashes.
- Your work: chat conversations, blog posts, keyword lists, audit reports and settings you create in the app. They exist so you can come back to them.
- What you post in public: blog posts you publish, and comments and likes you leave on the blog. Your display name is shown next to your posts and comments. You can delete your own at any time.
- Usage counters: how many chats, posts and audits you ran today, to enforce the free daily limits. Anonymous visitors are counted by a daily-salted hash of their IP address, never the raw address.
- Connections you add: API keys you create (stored hashed), and, if you choose, your own Cloudflare Workers AI credentials or a GitHub, GitLab, DEV Community or Notion key for publishing. Those tokens are encrypted at rest and never shown again. A post is only sent to those services when you choose to publish it there.
what we never do
- No ads and no selling of personal data. We only pass data to the service providers listed below, to run the product.
- We do not train models on your content.
- We do not log prompts by default. Our error logs keep request ids, not message text.
analytics
We use PostHog (US cloud) and Google Analytics 4 to see which pages and features are used and where things break. Both receive page views, clicks and, after you sign in, your account id and email so we can tell new users from returning ones. IP addresses are anonymised in Google Analytics. Neither is used for advertising. Block analytics with your browser's tracking protection and the app keeps working.
who processes it
The app and database run on Cloudflare (Workers, D1) in their global network.
When you use chat, blog writing, keyword tools or meta tag generation, your prompt and the text needed to answer it, such as recent conversation history or page content, are sent to Infinity Router (infinityrouter.dev), which passes it to an AI model. If that service is unavailable, the request goes to Cloudflare Workers AI instead. Infinity Router's own terms and privacy policy cover how it handles that text, so please avoid including sensitive information. Deleting your data here removes what we store, but cannot reach anything Infinity Router keeps under its own policy. If you link your own AI tool in settings and choose it, those requests go to your computer and that tool instead.
Trend data comes from Google Trends, GitHub and GitLab public endpoints; your identity is never sent to them. If you sign in with GitHub or Google, their privacy policies cover that sign-in step.
your controls
- Delete any conversation, post, list or key from the app at any time.
- Delete your whole account from Settings › Account. Everything tied to it is removed immediately.
- Questions or requests: chandra2khadka4@gmail.com.
cookies
- Signing in:
better-auth.session_token(HttpOnly, Secure, SameSite=Lax) keeps you signed in. A session lasts 12 hours and is renewed while you use the app.better-auth.session_datakeeps a 5-minute copy of the session so pages load faster, andbetter-auth.two_factorlasts only for the code step when two-factor sign-in is on. On the live site these names start with__Secure-. - Analytics: Google Analytics sets
_gaand_ga_<id>(up to 2 years), and PostHog setsph_<project key>_posthog(1 year) with a copy in local storage. Each holds a random visitor id; see analytics above. Blocking them does not stop the app working. - Your browser's own storage, never sent to us as a cookie: your theme, sidebar, market and organization view choices; an invite code from a
?ref=link until you sign up; and, only in that tab, a password-reset or device sign-in code so the page still works after a reload. A reset or sign-in code is taken out of the page address before any analytics run.
See also the terms of service.