Insay privacy policy
Last updated November 12, 2026 · Insay by Indraft
Insay is a browser extension that drafts replies on Gmail, X, Reddit and LinkedIn. It is built to read as little as possible, keep nothing, and never act without you.
What Insay reads
Only when you tap the Insay button (or press Alt+I) in a reply box, Insay reads the message you are replying to, up to two earlier messages in the same thread, the post title or email subject, and anything you already typed in that box. On Reddit it also reads the subreddit's name and up to five other comments in the same thread (shortened), so the reply fits the thread and does not repeat what others said. On LinkedIn it also compares your name, as shown on the page, with the post's author, only to tell whether the post is yours; your name itself is never sent. When you write the note on a LinkedIn connection request, it reads the name and headline of the person you are inviting, as shown on that page. It never reads other people's profiles in the background, post history or other pages. The one exception is your own profile, and only when you ask: see "Fill from my profile" below. With those messages it reads what the page shows about them: who wrote each one (so your own earlier replies and the post's author are recognised), when it was posted, and the author's headline or verified badge. Nothing is read before you tap, with one exception that you switch on yourself. If you choose "With a draft as I click in" for a site in Insay's settings (off by default, and offered on X, LinkedIn and Reddit, never in Gmail), Insay reads the same things when you click into an empty reply box on that site and stay in it for a moment, and sends them the same way, to write a draft that it shows in the box. While that draft is being written, the post is lit briefly on the page so you can see what was read; that is drawn by Insay and changes nothing on the site. That draft is not put into the site's box unless you press Tab, and typing puts it away. Insay does not do this on posts about a loss, an illness or a layoff, in direct messages, or in email. On a site you switch off in Insay's settings, Insay does nothing at all: no button, and nothing on the page is read.
On other sites
On any site other than the four above, Insay is not on the page and reads nothing. It has no permission for those sites. If you press Insay's shortcut, or choose "Polish with Insay" from the right-click menu of a text box you are typing in, your browser lets Insay into that one tab for that one time. Insay then reads only what you typed in that box (the part you selected, or all of it), sends it the same way as a draft to be tidied up, and puts the result back in the box, with Undo. Nothing else on the page is read, and never a password field, an email-address field or a number field. This works in Chrome and other Chromium browsers.
You can also turn Insay on for one such site, from Insay's popup while you are on it ("Turn on for this site"). Your browser then asks you to let Insay work on that site, and only that site. From then on Insay's button shows in the text areas and editors there. It still reads nothing by itself: when you click the button, press the shortcut, or pick Fix, Shorter, Clearer or Rephrase on text you selected, it reads what you typed in that box (or the part you selected), sends it the same way as a draft to be tidied up, and puts the result back, with Undo. It never reads the rest of the page there. The list of sites you turned on is kept on your device only. Turning a site off in the popup removes Insay from it and gives the permission back to your browser.
On such a site the popup also has "Request this site". It opens an email in your own mail app, addressed to Insay, with the site's name in it. Insay sends nothing itself: the email is yours to send, change or discard, and if you send it, it is handled like any email you write to us.
Fill from my profile
If you choose "Fill from my LinkedIn" or "Fill from my X" in Insay's settings, Insay first asks for your permission, every time. Only after you agree, it opens your own profile in a background tab, reads it once, and closes the tab. On LinkedIn it reads your name, headline, About, current company and location; on X, your name, bio, website and location. It never opens anyone else's profile. This happens in your browser: the page is read by the extension and nothing is sent to Insay's server or to any AI provider. You then choose which details to keep in your profile, and the rest is discarded. If you also choose "Tidy it up with AI" on that screen, the text Insay read is sent once to write cleaner suggestions, the same way as a draft (to Insay's server and Anthropic, or straight to your own AI provider), and is not stored.
Where it goes
Insay writes in one of two ways, chosen in its settings. Each draft request includes what it is replying to (above) and what you told Insay about yourself for that site: your profile, your "about me" note, your About me facts and My rules. If you turn on "Use my posted replies as examples", 2 or 3 of your recent posted replies on that site go with it too (links, emails and @handles removed; never on Gmail), and it can include the names of the reply types you pick most there. They are used to write that draft and are not stored by Insay.
With an Insay account (the default when you have not added an API key): the text is sent to Insay's server, run by Alpstack on Amazon Web Services in the United States, which passes it to Anthropic's Claude to write the draft and streams the draft back. The server does not store the text or the draft, and its logs record only your account or device id, the site, how long the request took and how many words the model used, never the content. Anthropic does not train its models on API data; see Anthropic's privacy policy for how long it keeps API requests.
With your own API key: the text is sent directly from your browser to the AI provider you chose (Anthropic Claude, Google Gemini, DeepSeek, OpenAI or your own OpenAI-compatible endpoint), using your key. Alpstack's server is not involved and never receives your messages, drafts or key. If the first provider fails before writing anything, and backup models are on, the same text is sent to the next provider in your list that has a key.
The provider's own privacy policy applies to what you send them. Please read it, especially for email. For example, DeepSeek states that it processes and stores data in the People's Republic of China and may use it to train its models unless you opt out in your DeepSeek account.
Gmail and InboxSDK
On Gmail, Insay uses InboxSDK (by Streak) to attach to compose and reply windows. Insay turns off InboxSDK's usage analytics. If InboxSDK itself hits an internal error, it sends an error report to InboxSDK's servers containing the error message, the extension ID and a one-way hash of your Gmail address. It is not sent your emails, the replies you draft, or your API keys. See the InboxSDK terms.
What Insay stores
On this device:
- Your API key, if you use one: stored only on this device (
chrome.storage.local), never synced, readable only by the extension's background worker. - Your Insay sign-in: short-lived tokens and a random device id, stored the same way, never synced.
- Your preferences (provider, model, default tone, reply language, your "about me" note, X length limit, which sites are on), and your About me facts, My rules and snippets: stored on this device (
chrome.storage.local). If you turn on "Sync settings across my devices", they and your saved actions are kept inchrome.storage.sync, your browser's own sync, so they follow your browser profile. Insay's servers are not involved, and API keys, edit history and recent takes are never synced. - Your profile (your kind of work, what you do in one line, your work, your goals and who you want to reach): stored on this device only (
chrome.storage.local). It is synced through your browser's own sync only if you choose "Sync with my browser account" for it in Insay's settings, or kept with your Insay account if you choose "Sync with my Insay account" (see below). Otherwise it is lost if you uninstall Insay or move to another browser profile or computer, so settings has an export to back it up. - A small settings file (
heyinsay.com/config.json) with page selectors and links, downloaded every few hours. It contains no user data and the request carries none.
On Insay's server, for the Insay account only:
- Your account: when you sign in with Google, your email address, your Google account id, what you have bought (Plus, BYOK), when your Plus trial started and ends, and when you joined. Insay asks Google only for your basic profile and does not store your name or photo.
- Your profile, synced, only if you choose "Sync with my Insay account" in Insay's settings (off until you do, and Insay asks every time you turn it on): your profile, your About me facts, your name and your "about me" note, as one copy, so your phone and your other browsers can use them. It is kept on Insay's server in the US (AWS), encrypted at rest, with when it was last saved and on which device ("Chrome on Windows", "iPhone"). Insay's logs record only its size, never what it says. Each device keeps its own copy too. Turning sync off offers to keep the copy or delete it; signing out stops syncing and keeps this browser's copy. It is also deleted with your account.
- Your browsers: each browser you sign in on gets a random id, kept with a label such as "Chrome on macOS" and when it was last used, so the BYOK plan can be used on up to 2 browsers. You can see and deactivate them in settings.
- Usage counts: how many drafts you used today and this month, to apply the plan's limits. They hold numbers only and delete themselves after the period ends.
- The Plus trial: the random id of the browser that started it, so each browser gets one trial, deleted after a year; and a count of trials started from your network, kept under a one-way keyed hash of your IP address (never the address itself) and deleted when the month ends.
- Before you sign in: the random device id and, to stop abuse of the free tries, a one-way keyed hash of your IP address. The IP address itself is never stored, and the hash is deleted after two days.
On this device, unless you turn it off:
- Your edits: when you insert a draft, Insay keeps it, and when you post, what you actually posted (the last 200). This is how Insay will learn how you write. It stays in
chrome.storage.local, is never synced and never sent. Settings, Privacy, "Remember my edits on this device" turns it off, and "Clear my edit history" deletes it. - Your voices: if you create a custom voice, the writing you paste is sent once to write its style rules (to Insay's server with Plus, or straight to your AI provider with your own key) and is not stored anywhere, by Insay or on your device. Only the resulting rules and a few short examples, with names, emails and links removed, are kept on this device, and synced only if you turn on settings sync. They are sent with each draft you write in that voice.
- What you typed into Insay: your last 10 takes and refinements, so the up arrow can bring one back. Never kept on Gmail. It stays in
chrome.storage.local, is never synced and never sent. Settings, Privacy, "Remember what I type, for the up arrow" turns it off and deletes them. - Your recent drafts (History): the last 50 drafts, with a short preview of what they replied to, for 30 days. Gmail is left out unless you turn it on. It stays in
chrome.storage.local, is never synced and never sent. Settings turns History off and clears it.
Apart from these, page text, drafts and generated replies are never stored, on your device or on the server. They live in memory while the panel is open and are gone when you close it.
Payments
Plus and BYOK are sold through Polar, which handles checkout, tax and receipts as the merchant of record. You pay on Polar's checkout page; Insay never sees your card. Polar tells Insay's server what you bought, linked to your Insay account id, so your plan works wherever you sign in. Insay keeps only what you own, when you bought it and the price paid, never payment details.
With BYOK, your API key stays in this browser and is never sent to Insay. A signed note from Insay's server, valid for 7 days, lets BYOK keep working if Insay's server is briefly unreachable.
Usage statistics
To learn what to improve, Insay sends anonymous usage events to PostHog (US), which stores them for us. An event says what happened, never what was written: for example that a draft was written or inserted, which action it was (Answer, Push back...), on which site, how long it took, whether you changed it before posting (as yes or no and a number), whether you use an Insay account or your own key, and the extension version. When you mark a draft as not good, the reason you picked (such as "Too generic") is sent with the names of the writing rules the draft broke, never the draft. Each install gets a random id that is not linked to your account, your email or your trial.
Never sent: page text, drafts, your edits, your take, your API key, your email. PostHog is told not to look up your location from your IP address. Turn usage statistics off in Settings, Privacy, "Share anonymous usage data"; anything not yet sent is dropped.
What Insay never does
- It never clicks Post or Send. You always post yourself.
- It has no ads, no session recording and no tracking across sites, and it does not sell or share your data. Its only usage statistics are the anonymous ones above, which you can turn off.
- It only runs on mail.google.com, x.com, www.reddit.com and www.linkedin.com.
Removing your data
Uninstalling Insay deletes your key, sign-in, preferences and edit history from this browser. To revoke a key, delete it in your provider's dashboard. To delete only your synced profile, turn off "Sync with my Insay account" and choose "Stop and delete it from my account". To delete your Insay account, its browsers, usage counts and synced profile from the server, use Delete my Insay account in settings, or email insay@alpstack.com from the address you signed in with. Deleting the account ends any Plus subscription first. Polar keeps its own records of past payments, as the law requires for tax.
Contact
Questions: insay@alpstack.com