AskSami privacy

1. What AskSami stores

• Your account. Your name, your email address, how you sign in and, if you use GitHub, Google or Apple, the profile details it passes on (such as your username and the link to your profile picture), the IP address and browser of each signed in session, your time zone and your settings. When you sign up, AskSami also records which page and link you arrived from, any campaign tags on that link, and the page you first landed on and when, or only that you came direct if nothing sent you to the front page, and, if that first page was a shared chat, which one, to know which channel brought you. The first page you load writes them into one cookie (sami_first, below), and they also travel in the page addresses; a later visit never changes them.
• What you told Sami while setting up. What you built, its address, who it is for, where you are stuck and what makes it different, Sami’s replies, and the files, links and Stripe, Paddle or Lemon Squeezy webhook secrets you added. It is kept with your product for as long as your account exists. If you start the setup again before Sami reads it, your new answers take the place of the old ones and Sami’s replies go, while the files, links and secrets stay. Any other setup you leave unfinished, such as one for another project on a paid plan, is kept as you left it for thirty days from the last time you touched it and then deleted, and sooner than that if you start setting up again.
• What Sami reads in your code. Facts, each with a short quote and the path of the file it came from, and the names and versions of the files it read. Not your whole code. The full text of a file, or of the changes in your folder, is kept only when Sami opens it from your repository or the terminal command sends it (which it does when you ask and whenever Sami asks), and then it is kept in that chat.
• Your live site. Facts from its pages, each with the page’s address. Web pages and search results Sami reads for you in a chat on the platform are kept in that chat.
• What you give Sami. The files you upload, as you sent them, and the figures read from screenshots and CSV files. The links you paste, with the title, author, text and counts read from them.
• Numbers from your product. What the eyes send (signups, clicks, drop offs and your own events, each with where the visitor came from, a random visitor id and any small details your code adds, and no IP address) and what your Stripe, Paddle or Lemon Squeezy webhook reports (amounts, currencies, that service’s customer, order and subscription ids, and any lead id your code stamps on them, not your customers’ names or emails).
• Every chat, in full. What you, the person you invite and Sami wrote, and the files, changes and web pages brought into it.
• The chat at /chat, before you have an account. What you and Sami wrote there, the names of any screenshots and table you sent with a message (the screenshots and the table themselves are not kept), a random visitor id that a cookie holds, how many messages you sent, which of Sami’s written questions you pressed, a keyed hash of your network address (never the address itself) with how many messages were sent, written questions pressed and shared chats carried on from it today, so the page’s limits hold (8 messages for you, 25 a day for your network, 120 written questions a day for your network and 20 shared chats carried on a day for your network), and a record of each answer Sami gave there (what it used and what it cost). The pages Sami opens and the searches it makes there are kept in the chat with what they gave back, as they are in every chat. When you sign up or log in in the same browser, the chat moves into your account and is kept like every other chat; the counts and the records of the answers stay against the visitor id. Until then the chat is kept against the visitor id. If you press Share under one of Sami’s answers, a copy of the chat from its first message up to that answer is kept with a link, and anyone who has the link can read it, with no account. The copy stays when the chat moves into your account. To have a shared chat taken down, write to support@asksami.app with its link. Someone who opens a shared chat and presses Continue this chat gets their own copy of it as their chat on /chat, kept like any other chat there and carried into their account if they sign up; the shared chat and its link stay as they were. A copy someone carried on is theirs, and it stays if the shared chat is taken down.
• The free plan’s chat. Kept like every other chat. It is the same chat as a paid account’s: the screenshots, the tables and the files you send with a message are kept with your product’s memory, and the web pages and search results Sami reads for you are kept in that chat, as they are on a paid plan.
• Your first honest read. A record of each try at it: the repository and the site address it was for, as GitHub’s number for the repository and the site’s address, with the day, and a one way hash of your email address, never the address itself. It stays after your account is deleted, no longer tied to your account, so the same repository, site or email address cannot have a second free read.
• What you and Sami work out. Your decisions, your honest read and plan, your channels, what Sami learns about your audience, your morning briefs, your Search & AI question and the questions Sami suggested, what the assistants answered each time it was asked (their words and the pages they cited), and the weekly check of your site. Answers you press on Sami’s marketing brain while signed in are saved with your product’s memory, and you can correct them on the Memory tab. Sami’s memory is never edited and never deleted by Sami: a correction is added and the old record kept, and the memory goes only when the account is deleted.
• The Founder review and your thread with the founder. On a paid plan, your Founder review, written by the founder of AskSami, every line you, the people in your account and the founder write in your thread, with its pastes and files (kept in Sami’s memory too), and a record of each letter that tells you or the founder of new lines.
• Your public page. What you write for it, the screenshots you pick and the figures you tick, as you write it, as you send it to the founder and as it is published. Once it is published, its words and copies of its screenshots are public at its address.
• Billing and use. Your plan, your Stripe customer and subscription once you have paid, a record of every AI call made for you, on the free plan and on a paid one, with what it used of your allowance (your free honest read uses none of it, and neither do the first words Sami fills in on your public page or the reading of files sent in your thread with the founder), and the credits you bought.
• The rest. The email addresses of people you invite, your terminal tokens and the name of the folder each was last opened in, your GitHub App installation and the repositories it lets AskSami reach (never a GitHub token), and a record of the emails AskSami sent.

2. Where it is kept, and who handles it

AskSami stores all of this in Supabase, in the EU (Ireland). These companies handle parts of it for AskSami, some of them outside the UK and the EU, including in the United States:

• Anthropic: the AI models behind Sami. What you write to Sami (what you tell Sami in the setup, the free plan’s chat, and the chat at /chat before you have an account, too), any screenshot and any table (a CSV or TSV file) you send Sami, what Sami reads, your name and email address, and the email address of anyone you invite go to Anthropic so Sami can answer. Sami’s web searches and page reads run through Anthropic as well, and so does your Search & AI question when the ask is on, answered there with a web search. The questions Sami suggests for Search & AI after each honest read are written by Anthropic’s model too, from your honest read, your product’s name and address, and the seo facts read from your site. On a paid plan the Founder review of your product reaches the model too. So do the lines and files of your thread with the founder, which Sami keeps in its memory like everything else. So does the record your public page is first filled in from.
• OpenAI: Search & AI’s ask, once the account owner turns it on (on Growth and Max): your Search & AI question, the one question a buyer would ask that you picked, goes to ChatGPT through OpenAI’s API with web search on, on the plan’s days (Monday, and Thursday on Max). It names your product only when you write it that way. Nothing else of yours is sent.
• Google (Gemini): the same ask: your Search & AI question goes to Gemini through Google’s API, which answers it with Google Search.
• Perplexity: the same ask: your Search & AI question goes to Perplexity through its API, which searches the web to answer it.
• Stripe: payments. AskSami sends Stripe your email address and your account id. Your card details go to Stripe and never reach AskSami.
• Resend: sending the emails AskSami writes to you, the invitations you send, the letters that tell you the founder wrote to you and, when you write in your thread with the founder, the letter that tells the founder, which quotes up to three of your lines.
• GitHub: the AskSami GitHub App that reads your repository, and sign in, if you choose GitHub.
• Trigger.dev: the background jobs that read your code and site, write your honest read and plan, write your morning brief, fill in the first words of your public page and send the Founder thread’s letters, and run Search & AI: the ask on the plan’s days (Monday, and Thursday on Max), the questions Sami suggests after each honest read, and the weekly check of your site.
• Vercel: hosting the website and the app.
• Supabase: the database, sign in and file storage.
• Kickbox: checking that an email address can receive mail when you sign up with one. It gets the address before the account is made.
• Google and Apple: sign in, if you choose them.

When Sami reads your site or a link you paste, and when the weekly check reads your site’s robots.txt, sitemap, llms.txt and pages, AskSami’s servers fetch them from that site.

3. Secrets

• Your Stripe, Paddle and Lemon Squeezy webhook secrets are stored encrypted, the Lemon Squeezy one whether you chose it or Sami made it for you. A Lemon Squeezy secret Sami makes is shown to you once, in the reply that hands it over, and the chat keeps a note in its place. A webhook secret you give in the setup is kept encrypted with your setup only until it is handed to its webhook, and then only the webhook keeps it.
• Eyes keys, terminal tokens and invitation links are stored as hashes, which cannot be read back. An eyes key Sami gives you in a chat is shown to you once, in the reply that hands it over, and the chat keeps a note in its place.
• Files that hold secrets by their nature, such as .env files and private keys, are never read from your repository or sent from your terminal.
• In other files Sami reads from your repository, and in the files and changes your terminal sends, anything that looks like a key or a password is blanked before it is kept or shown to Sami. Files you attach, on the platform or with /attach, are kept as you sent them. Blanking catches the usual shapes, not every one, so keep secrets out of your code.
• A key, a token or a password pasted into a chat, on the platform, in the terminal or at /chat, is taken out before the message is kept, and is kept nowhere: the keys of the services founders use most (Stripe, Paddle, OpenAI and the other AI models, GitHub, GitLab, AWS, Google, Supabase, Slack, SendGrid, Resend and more), a token in a pasted request, a password inside an address, a key in a link, and the secret lines of an environment file. A public key, such as a publishable key, and an example value are left as they are. A link you give Sami, in a chat, on your Channels tab or in the setup, is opened and kept without any password or token in it, and a link that does something when it is opened, such as a sign in, confirm or unsubscribe link, is kept and never opened. Taking them out catches the usual shapes, not every one, so do not paste passwords or other keys.

4. Your data stays yours

Nothing from your project is shown to or used for any other account, with one exception: no other account gets a free honest read of a repository, a site or an email address that has had one, and a free account that asks is told so. On a paid plan one person outside your account also sees your project: the founder of AskSami, as the next paragraph says. Sami’s own knowledge comes from AskSami’s playbook and notes, not from other people’s projects. AskSami does not train AI models on your data.

On a paid plan the founder of AskSami, a person, reads what you give, Sami’s honest reads of your product, your name, your email address, your plan and where you came from when you signed up, and never your chats with Sami. The founder writes a Founder review of your product that you see on your Verdict tab, and talks with you in a thread there. Either of you can send files in it, and only the people in your account and the founder can open them. You can write a public page for your product on asksami.app, starting from words Sami fills in. The founder reads it and publishes it, or sends it back with a note. It shows only the words you write, the screenshots you pick and the figures you tick. Its address is sent to search engines through IndexNow. Nothing else from your project is public.

The person you invite works in your account and sees your projects, as the Terms say.

5. Deleting your account

The account owner can delete the account from the Account page. It asks twice, and the second time you type DELETE. It cannot be undone.

Deleting cancels your plan at once, removes every file you gave Sami, and then deletes the account and all its projects with everything in them: your answers, facts, chats, numbers, decisions, memory, tokens, invitations and the record of emails sent. The person you invited loses access, and you are signed out. The record of your first honest read stays: which repository and which site address each try was for, and the one way hash of your email address, no longer tied to your account, so neither they nor your email address can have a second free one.

Deleting also removes your public page and the public copies of its screenshots, your Founder review, your thread with the founder with its files, and the records of its letters. Letters already sent to the founder stay in the founder’s mailbox, and a search engine may show a page that was public until it next visits it. To take your public page down without deleting your account, write to support@asksami.app.

Someone invited into another account can leave it from the Account page instead. What they wrote stays in that account’s chats. If you cannot reach the Account page, because you left someone’s account, write to support@asksami.app from your account’s email address and ask for your account to be deleted.

Some things live outside AskSami. Stripe keeps its own record of your payments. Emails already sent stay in your inbox. The AskSami GitHub App stays installed on your GitHub account until you uninstall it there. If you added the eyes to your product or pointed a Stripe, Paddle or Lemon Squeezy webhook at AskSami, they keep sending until you take them out, and AskSami refuses and keeps nothing they send. A chat you shared from /chat stays at its link after the account is deleted: write to support@asksami.app with the link to have it taken down. Our providers keep their own service logs for a limited time.

6. Cookies

AskSami’s cookies are for signing in, apart from one for the chat at /chat, one for where your first visit came from, and four for how the platform and the chat at /chat are laid out. One keeps you signed in. A few more connect a GitHub, Google or Apple sign in, or an email link, to the browser that started it. If you open an invitation while signed out, one more holds the invitation for up to an hour while you sign in. If you open the chat at /chat without an account, one more (sami_visitor, kept for a year) holds the random visitor id that keeps your chat and its limit of 8 messages, and lets the chat move into the account you make; it comes off once the chat has moved. One more (sami_first, kept for a year) holds where your first visit came from (the page that sent you, any campaign tags on the link, the page you landed on and when, and, if that first page was a shared chat, which one), written once on the first page you load and never changed, so that your account can record it if you sign up; it holds no name and nothing that identifies you. Scripts on the page cannot read any of those. The last four (sami_nav, sami_side_width, sami_wide and sami_chat_width) remember whether you keep the sidebar open, whether you expanded the chat across the page and how wide you dragged the chat, for a year, and how wide you dragged the sidebar, until you close the browser; they hold nothing about you, and they are the only ones a script on the page can read. There are no analytics or advertising cookies, and none from another company: sami_first is the one cookie that records anything about your visit, and what it records is where the visit came from, not who you are.

The website loads nothing from other companies. Paying, and signing in with GitHub, Google or Apple, take you to that company’s own page, where its own cookies apply.

If you add the eyes to your own product, the code your coding tool adds from Sami’s install prompt sets a cookie on your visitors (sami_attr, kept for a year) to tell where a signup came from. Telling your visitors about it is up to you.