Last updated October 18, 2026

Privacy policy

Sei is an early-access tool that checks articles for search, readability and AI-answer quality. This page explains what we collect when you use it, why, and what you can do about it.

What we collect

  • Your Google account basics. When you sign in with Google we receive your name, email address and profile picture. We do not receive your password, and we do not ask for access to your Gmail, Drive or other Google data.
  • Google Search Console data, if you connect it. A workspace owner can connect a Google account to Sei with read-only access to Search Console. We then read, for the properties you choose: clicks, impressions, click-through rate and average position by day, page and search query, and the index status of your published articles (URL Inspection). We also receive that Google account's email address, to show which account is connected.
  • AI requests, if you use the AI features. When you ask for Fix with AI, title and description suggestions, alt text or an AI image, Sei records that a request was made: who asked, which feature, which provider and model, how many tokens it used, its estimated cost and whether it worked. These records never contain your article's text.
  • Site health scans. Our scanner, SeiBot, reads the public pages of the sites you add: the home page, your published articles and some sitemap pages. Sei keeps what it found on each page (status codes, redirects, indexing tags, canonical links, structured data types and word counts) for your last 10 scans, never the pages' HTML.
  • AI visibility. The prompts you add for a site (questions your customers ask) and its other brand names. Each run sends the prompts to the AI engines that are on for the site, and Sei keeps their answers (up to 4,000 characters each) and the sources they cited for the last 12 runs plus the newest completed run.
  • What you create in Sei. Workspace and site names, site domains, and the articles you write or edit, including their titles, meta descriptions and the scores Sei computes for them.
  • Sign-in sessions. A session cookie keeps you signed in, and a cookie remembers which site you last opened.

The public demo stores its edits only in your own browser. Nothing you type in the demo is sent to our database.

How we use it

  • To sign you in and keep your workspace separate from everyone else's.
  • To save your articles and show their scores.
  • To contact you about your account if we need to.

We do not sell your data, use it for advertising, or use your articles to train AI models.

Search Console data is used only to show your sites' search performance and index status inside your Sei workspace. It is never sold, never used for advertising, never used to train AI models, and never shown to anyone outside your workspace.

Where it is stored

Sei runs on Vercel, and its database is hosted by Neon in the United States. Background jobs (importing and refreshing Search Console data, and checking index status) run on Inngest, which stores each job's inputs and results in its run history: a site's Search Console property name (for example sc-domain:example.com) and Sei's internal ids for the site and its articles. Inngest never receives Google access. Vercel, Neon and Inngest act as our processors. Connections are encrypted in transit.

AI writing assistance

Sei's AI features send only what a request needs to an AI provider: for Fix with AI, the sentences to rewrite, the paragraphs around them, and the article's title and keyphrase; for title and description suggestions, the title, SEO title, meta description, keyphrase, first paragraph and headings; for alt text, the article's title and keyphrase, the heading and paragraph near the image, and the image's web address. Sei never downloads or sends the image itself: the provider fetches it from that address, so the image's host sees a request from the provider. Nothing is sent until you click an AI button.

For an AI image (the image dialog's AI image tab), Sei sends only the description in the box, which starts from your article's title and keyphrase and which you can change before you click Generate, plus Sei's own rules (no text, logos, brands or real people). Nothing else from the article is sent. On Sei's own, the image is made by Pollinations (pollinations.ai), a free public image service, or by Google Gemini (Pollinations when Sei's Gemini key can't make it); with your workspace's own key, by OpenAI or Google Gemini. Pollinations gets only the prompt, in the address of the request, never your name, workspace or article; it is a public service that logs requests and may cache the image it made, so don't put anything private in the description. The images come back to your browser only; Sei stores just the one you pick, in its image storage like an upload, and keeps the others nowhere.

Depending on how your workspace is set up, these excerpts are processed by Groq, OpenRouter, Google Gemini, OpenAI or Anthropic. OpenRouter passes each request on to the provider that serves the chosen model, under that provider's terms and your OpenRouter privacy settings. Sei's default provider may be a provider's free tier, whose terms can let the provider use requests to improve its models (Settings shows which provider is in use and its note). A workspace owner can add the workspace's own API key for a provider instead, so its requests run under that key's own terms, including paid tiers that don't use requests for training. Keys are stored encrypted and are sent only to their provider.

Sei does not train AI models on your articles, and for AI writing it doesn't keep the AI's answers beyond showing them to you. (AI Visibility keeps its answers, as the next section says.)

AI visibility

AI Visibility sends a site's prompts, exactly as you wrote them, to the engines that are on for the site, each with web search on: Google Gemini and Groq on Sei's keys, and OpenAI, Anthropic, Perplexity and OpenRouter only on your workspace's own keys. Nothing else about you or your articles is sent with them. Each provider handles the prompts under its own terms; on Sei's keys that can be a provider's free or standard tier. Sei stores each answer's text, the sources it listed and the provider's usage figures, for the last 12 runs plus the newest completed run, so you can compare runs. Answers are shown as text only and are never sent to another provider. You can delete prompts at any time; a deleted prompt's past answers stay with their run until it is deleted.

Google user data

Sei's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Search Console access is read-only: Sei never changes anything in Search Console. The access Google grants is stored encrypted, and the short-lived tokens it is exchanged for are never stored.

Revoking Search Console access

A workspace owner can disconnect Search Console at any time in Integrations: Sei asks Google to revoke Sei's access and deletes the stored access straight away. Disconnecting revokes all the access that Google account granted to Sei, not only Search Console: if you also sign in to Sei with that Google account, you stay signed in, and Google may ask you to approve Sei again the next time you sign in. You can also remove Sei from the Google account itself, under Security → Third-party apps and services (myaccount.google.com/connections). Search data Sei already synced stays in the workspace, marked as stale, until the site is deleted or mapped to another property; choosing “No property” for a site deletes it straight away.

Keeping and deleting data

We keep your data while your account exists. To delete your account and everything in it, email us from the address you sign in with and we will remove it within 30 days. Deleting a site (on its page in Sites) removes its articles straight away.

Contact

Questions about this policy: petruswst@gmail.com