Privacy
SayAlign reads the message you are writing so it can rewrite it. It does not keep it.
Last updated: 16 November 2026
Your messages are not stored
When you ask for a rewrite, a reply or a check before sending, the text involved is sent to our server and on to our AI provider, which returns the result. For a rewrite that is your selection; for a reply, the message you are answering — the part you selected, or the latest message in the conversation when you start from the reply box — and any notes you add. For a check before sending, it is the whole message you are writing, not just a selection. Most results are sent a second time, together with your original, for a meaning review that warns if the result changed what your message commits you to. That is the whole journey. The text is not written to our database, not written to logs, not sent to analytics, and not saved in your browser.
| When you use | What is sent |
|---|---|
| Rewrite, or a situation such as Push back | The text you selected. |
| Reply | The message you are answering — the part you selected, or the latest message in the conversation when you start from the reply box — and your notes, if you wrote any. |
| Meaning review (after most results) | The text that action started from and the result it produced. |
| Check what this commits me to (only when you press it) | The whole draft you are writing. |
| Fact Guard and the instant checks | Nothing. They run in your browser. |
Our database has no column that could hold message content, and an automated test fails the build if one is ever added. We also instruct our AI provider not to retain the request: every call is made with OpenAI’s response storage turned off. Under OpenAI’s own API policy it may still keep request data for a limited period to detect abuse, and it does not use API data to train its models unless a customer opts in, which we have not.
For that second check, we store a one-way fingerprint of the text — a keyed hash that cannot be turned back into the words and is useless without a key only our server holds. It lets us confirm a check is about the message it claims to be about. It is not your message.
This applies to what you write, what the tool generates, email subjects, recipients and thread contents alike.
What we do store
- Your email address and password hash, for signing in
- Your plan and how many actions you have used this period
- For each request: which action you chose, which model ran, how many tokens it used and what it cost us — never the text itself
- Product events such as “a rewrite was generated” or “a result was inserted”, with no content attached
- If you arrived through a creator link or entered a referral code when you signed up, which creator referred you (the code is stored with your account)
We keep usage counts because they are what your plan is billed against, and cost figures because they are how we know the product is sustainable.
When you sign up we check the domain of your address against a public list of temporary-inbox services, so that a free allowance cannot be collected endlessly from throwaway addresses. The check happens in memory against a fixed list; nothing is looked up externally and nothing about it is stored.
Who else is involved
- OpenAI processes the text to produce a result and to run the checks. We send every request with response storage turned off; OpenAI’s abuse-monitoring retention, described above, is set by OpenAI.
- Supabase hosts our database and handles sign-in.
- Stripe processes payments. We never see or store your card details. Purchases go through Stripe Managed Payments, under which Stripe is the merchant of record for your purchase: it calculates, collects and remits sales tax or VAT.
- Google (Google Analytics) measures visits to the public website, only if you accept it — never the extension or your account.
There is no advertising network and no tracking pixel, and no third-party analytics in the extension or in your account pages. On the public website we use Google Analytics, only if you accept it — see below.
What the extension can access
The extension asks for local storage, to keep you signed in; access to the sites it works on — Gmail, Outlook on the web (outlook.office.com, outlook.office365.com, outlook.live.com and outlook.cloud.microsoft), LinkedIn, and the mail pages of common webmail services such as Yahoo Mail, Proton Mail, iCloud Mail, Yandex Mail, Zoho Mail, GMX, WEB.DE, Mail.ru, Fastmail and Tuta — and our own backend (sayalign.com and our Supabase project). On any other site it runs only after you turn it on there from the extension’s toolbar button: your browser then asks you to allow that one site, and you can turn it off again the same way. Opening the toolbar button lets the extension see the address of the tab you are on, so it can offer this; it does not keep it. It cannot read your other tabs, your browsing history, your cookies or your bookmarks, because it never asks for those permissions.
On a supported site, when you select text, the extension looks at the selection in your browser to decide whether to show its button. When you open SayAlign it reads the message you are working on, still in your browser. Some checks — a leftover placeholder like [AMOUNT], a date that does not exist — run entirely inside your browser and are never sent anywhere. Nothing is sent to our server until you choose an action or a check. Email subjects, recipients and the rest of the thread are not read or sent.
Website analytics
If you choose “Accept all” in the cookie banner, the public pages of this website — the home page, pricing, download, guides and similar — load Google Analytics, so we can see which pages and links bring people to SayAlign. It records the page address (with only campaign tags such as utm_source kept from the query), the page you came from, your browser and device type, an approximate location derived from your IP address, and clicks on links that leave the site. Google processes this for us. Advertising features — Google signals and ad personalisation — are turned off, and data is kept for 14 months.
It never runs in the extension, on sign-in and sign-up, on your dashboard or account pages, or on a creator’s private stats page, and it never sees anything you write. If you choose “Necessary only”, or have not answered, nothing from Google is loaded. You can change your answer at any time with “Cookie settings” at the bottom of every page; withdrawing removes Google’s cookies.
Cookies
Two of ours, both first-party. One keeps you signed in on the website. The other records which creator referred you, if you arrived through a creator link; it lasts 30 days, contains only a short reference, and is cleared once your account is created.
Only if you accept website analytics: Google Analytics sets its own cookies (_ga and _ga_…), which last up to two years. Your answer itself is kept in your browser’s local storage, not in a cookie.
Two separate sign-ins
The extension keeps its own session, independent of the website. Signing out on one does not sign you out of the other. This is deliberate — it means closing your browser tabs does not sign you out of the tool you are working in — but it is worth knowing.
Your data
You can export or delete your account data by writing to privacy@sayalign.com. Deleting your account removes your profile, usage records and subscription link. Because we never stored your messages, there are none to delete.
We keep billing records for as long as tax law requires, which is separate from your account data.
Changes
If this policy changes in a way that affects what we do with your data, we will tell you by email before the change takes effect.
Contact
Areonex · privacy@sayalign.com
