Plain words, no fine print.

Basic, cookie-free page-view analytics: which page you visited, the referring site (if any), and a timestamp. No cookies, no tracking ID follows you between pages, and nothing here is linked to your account or identity - even we can't read it back through the public API, only via direct database access. Nothing is sold or shared with advertisers.

On supported chat sites (like claude.ai and chatgpt.com), Alide reads the prompt box you're typing in, the visible conversation, and files you attach there - that's the material it reviews. It reads nothing on any other site, and it never reads your browsing history, your browser's saved passwords, or anything outside the chat page. (One narrow exception: the extension also runs on alide.ai itself, only so your account dashboard can display your extension settings. It reads nothing from that page.)

When AI review runs, your draft (plus relevant conversation and attachment excerpts) is sent to Alide's servers, which pass it to our model provider to generate suggestions. We keep a count of tokens used - for fair-use limits and our own costs - but we don't keep the draft.

One qualifier, because "not kept" should mean what it sounds like: our model provider is OpenAI, and OpenAI may hold what we send in its own abuse-monitoring logs for up to 30 days before deleting it. It is not used to train their models, and nobody at Alide can read it back. Section 14 of the full policy sets out exactly what OpenAI retains and for how long.

Four things, plus the bookkeeping every account needs: usage counts that enforce plan limits, and subscription status if you subscribe. The four: your account email, for sign-in. Your sign-in credential: if you create a password, we collect it when you set it and when you sign in, it travels only over encrypted connections, and it is stored solely as a salted cryptographic hash by Supabase, our sign-in provider - the password itself is never written to our database and nobody at Alide can read it. (Sign in with Google instead and we receive your email and basic profile from Google; we never see any Google password.) Your settings (suggestion density, theme, and so on), so they follow you across devices. And your suggestion history: when you pick, ignore, or undo a suggestion, we store that choice - the style of option that was offered, like "go deeper" or "critique this" - and use it to tailor future suggestions to how you actually work. Not the suggestion itself, and not anything you wrote.

Your prompts themselves are never stored on our servers - not in your suggestion history, not anywhere in our database. Your draft is sent to our model provider to produce a suggestion and is not written to our database at any point. What your history keeps is the shape of what happened: which kind of suggestion was offered, which one you took, and when. Not the words.

Two things do stay on your own device, in your browser's storage for the extension, and neither is ever uploaded to us. While you work through a prompt, Alide keeps a copy of that draft and the answers you have given in that tab, so a reload or a crash doesn't lose the work you have put in; it is erased when you finish or clear the prompt, and a copy older than 30 minutes is thrown away rather than restored. Separately, any prompt you deliberately save to the prompt library is kept the same way. Both live only in that browser on that machine - we cannot read either one - and uninstalling Alide or clearing the browser's data removes them.

Alide used to keep a numeric fingerprint of each draft so it could recognize a similar moment later. That is gone. The fingerprints were deleted and the feature was removed, because keeping a derivative of your writing sat badly next to the sentence above. Alide now personalizes only from what you give it during a session, and keeps none of it afterwards.

We never sell your data. We never share it with advertisers. We don't run ads. Your prompts and history aren't used to train foundation models - they tune your own suggestions, for you.

Both live in the extension itself: open the Alide popup, and under Data & privacy you can delete your suggestion history, or delete your whole account - email, settings, history, usage records, everything. Two clicks, effective immediately, no email required. (Though if you'd rather ask a person, alideteam@gmail.com still works; a founder answers directly.)

What deletion cannot reach, so the promise means something: copies already held by a processor may take their own course to clear, unexpired backups keep a copy until they expire, aggregate figures that no longer point at you stay, and we keep the limited billing, tax, security, fraud-prevention and dispute records the law requires us to keep. Deleting your account is also not the same as uninstalling: uninstalling stops Alide on that device and leaves the account alone. Section 18.2 of the full policy states all of this precisely and is the version that governs.

One carve-out is worth naming on its own, because it is deliberate. A problem report you send from the popup is anonymous: it carries no user ID, which is exactly what lets us read what went wrong without learning who it came from. That cuts both ways - we can't delete your reports along with your account, because nothing in our system records that they are yours. Instead every report is erased 90 days after it was sent, whether or not the account behind it still exists. Sections 13.5 and 18.2 of the full policy state this precisely.

Deletion also happens on its own: suggestion history is automatically erased after 90 days - it only ever informs your suggestions for that long - and raw usage records after 90 days, keeping only daily counts.

Five, named: OpenAI receives the draft you are writing and returns the suggestion. Supabase hosts our database and sign-in. Stripe handles payment if you ever subscribe - we never see or store your card. Resend delivers our email, so it sees the address every sign-in code is sent to; and if you report a problem, the full text of what you wrote passes through Resend on its way to our inbox, along with the reply address you chose to leave and any answer we send back. Netlify hosts this website, so it sees the IP address and browser your visit arrives with - it receives nothing from the extension, which never talks to it. Each receives only what it needs to do its job, and none is permitted to use your data to train models or for anything else.

One more, only if you ask for it: if you connect a GitHub repository, we store the access token you granted and a small cache of repository facts - the default branch, and open pull requests and issues, including ones assigned to you - so Alide can ground its suggestions in what you are actually working on. We never store file contents, and we do not keep a list of your files. Disconnecting removes the token and the cache.

This summary is short because the product is simple. If anything here is unclear, ask: alideteam@gmail.com.