Privacy

The short version

SaysHere never records audio. When you listen, your audio passes through our server on its way to Deepgram or OpenAI, which turns it into text. Our server holds it in memory and never writes it down. The notes on your Notes page stay on your device. Our server keeps a transcript only for a session you chose to keep in your account before you started it. If you or your team connect GitHub, or you connect Google Drive, our server keeps the text of the files it reads from them for a workspace's library. Our server also keeps the notes you write on a kept session's page, the text of the documents you add to your Library, and a copy of each session you share by a link, encrypted so that we can't read it. Your audio, transcripts and notes reach an AI service only if it is independently audited for security, works for us under business terms and doesn't train its models on them. This page names each one we use. We keep your email address, the ways you sign in, your plan, your billing records, how much listening time you've used, and records of page visits that hold nothing linking them to your name or to another day.

What we keep

• Your email address, and the ways you sign in: for an outside account its ID and the address it gave us.
• Your plan, its billing period and its status, as Stripe reports them, and the dates and amounts of your invoices.
• For each time you listen, when it started and ended, how long it ran and how it ended, so your plan's limits can apply and you can see your own history. These records hold no words.
• The sessions you chose to keep in your account, described below.
• The documents you add to your Library and the encrypted copies of the sessions you share by a link, described below.
• Sign-in records: for a sign-in by code, the code and its link, kept in a form we can check but not read, for ten minutes, and when a Google or GitHub sign-in waits for that code, the outside account's ID and the address it gave us, held with the code until it is used or expires; a record of each session and the way it was made; a count of sign-in tries, kept two hours; and for thirty days a scrambled form of each address a browser signed in to, so a stranger's requests can't use up your codes.
• A record of each way to sign in added or removed and each password set, changed or removed, with its time, kept while your account exists.
• Records of visits to the pages: which page and when, from which country, in which browser, operating system and kind of device, from which site the link came, how long the page was in front of you and how far it was scrolled. They carry no cookie and no number that ties your visits on different days together (see Cookies and tracking below), and they are kept without a time limit for now; this page will say when we set one.
• A record that you agreed to a plan's renewal terms, with the time, the price and the network address you agreed from. California law has us keep it for three years, or for one year after the plan ends if that's longer, so it stays after you delete your account.
• If you or your team connect GitHub, the text and path of each file SaysHere reads from the repositories chosen for a workspace's library, the names of the repositories the link can reach and of the GitHub account the app is installed on, and the numbers of the installation and of the GitHub user who linked it, until the link is removed.
• If you connect Google Drive, the name and text of the files you add to a workspace's library, the token Google gives SaysHere, encrypted, and your Google account's address, until you disconnect Google Drive or delete your account.
• If you connect Gmail, a sanitized copy of the recent mail you include, with each attachment's name, size and type, each copy for at most 24 hours after the read it came from, and the connected mailbox's address, encrypted, until you disconnect Gmail or delete your account.
• For each meeting bot you send, a record of its notice and of its run, and its transcript if you keep it in your account, described below.
• Your Zoom connection, if you connect Zoom: your Zoom user ID, your Zoom account ID and Zoom's two tokens, sealed.
• If you connect Google Calendar, the token Google gives SaysHere, encrypted, and your Google account's address, until you disconnect Google Calendar or delete your account, and a record of each meeting it lists, without its title or guests' addresses, for the time "Meetings from your Google Calendar" names.
• If you connect Notion, the token Notion gives SaysHere, encrypted, your Notion workspace's name and ID, and the ID Notion gives the connection, until you disconnect Notion or delete your account.
• If you save a Slack link, the link, encrypted, with its kind, its last four characters and when you saved it and last sent with it, until you remove it or delete your account.
• SaysHere keeps each notice in your notifications for 90 days, then deletes it.

When you delete your account, we also keep a one-way hash of your email address and your Stripe customer number, so a late message from Stripe can be matched and set aside.

We copy our database every night and keep each copy up to 30 days, so something you delete is gone from every copy within 30 days.

We also keep a list of what was deleted and when, without its content, for 30 days, so that if we ever restore a copy, anything deleted after that copy was made is deleted again.

A session you don't keep

Every account starts here. Our server never writes any of these to disk or to a log: the audio, the transcript, the text of your notes, the suggested lines and the summary. While you listen, the transcript is on your device and in the memory of the program that listens for you on our server, and that memory is gone when the session ends. Our server keeps only the record that you listened and for how long. We don't use what you say or write to train or improve anything.

A session you keep in your account

If you choose In my account before you press Start, our server stores the session as it runs and keeps it when it ends: its transcript, the notes SaysHere makes from it (a summary, decisions and action items, each with the words it rests on), the suggested lines and fact-checks your screen showed with their sources and licence notices, and a record of the notice you gave the room: which sentence your screen showed, and whether and when it was said. It stays until you delete it or your account, or until 30, 90 or 365 days after it ends if you set the sessions you keep in a workspace to be deleted then. In a team, leaving the team deletes the sessions there that only you can open. A session you started as not kept can't be moved into your account afterwards, and the notes on your Notes page are not stored with it.

We never sell it, and never use it to train or improve any AI model, ours or anyone's. Others can read it only through a link you share or a project you file it in, as "Your Library" says. We read it only at your request, to keep the service secure, or where the law requires.

Your Library

If you choose On this device before you press Start, the session stays in this browser's storage on this device, under your account, with its transcript and its report. To make the report, your browser sends the transcript's text to our server, which passes it to OpenAI. Our server holds the text and the report in memory alone and writes neither down. Your browser can fetch the report for ten minutes after it is made.

For a session you keep in your account, our server sends OpenAI the transcript's text, with the time of each line, to write the session's report. On the session's page you can give it a title, tags, a folder and notes of your own, and we keep them with the session.

To search what you kept and answer your questions, our server sends OpenAI the text of your kept sessions and documents in short passages, to build the index they are searched by. When you ask a question in the Library, your question goes to OpenAI as you wrote it, with up to 8 short passages of what you kept and their titles. Those passages can come from the sessions kept on this device and, while "Use these notes in the Library" is on, from the notes on this device, and we don't store them on our server. Before a transcript or a passage goes to OpenAI, we replace the email addresses, phone numbers, and payment and ID numbers in it. What we keep stays as it was said. OpenAI may keep what it receives and the answers it returns for up to 30 days to provide the service and check for abuse, longer only where the law requires it or to protect its services or others from harm, and it doesn't train its models on it unless SaysHere opts in, which SaysHere hasn't.

When you add a document to the Library, our server reads it and keeps its text in the workspace you add it to, so that search and Ask can find it. We don't keep the file. Only you can open its text until you file it in a project, which shows it to the same people as the sessions filed there. In a team, leaving the team deletes the documents there that only you can open.

Share on a session's page makes a link to a session you kept in your account. Your browser encrypts the copy before it leaves, and the key is part of the link, so we store a copy we can't read and give it to anyone who opens the link. We delete the copy when the link is revoked, when the session is deleted, when you leave the team it was made in or the team switches links off, and within an hour after its last day. We keep the link's record, without the copy, for 30 days after it ends, so you can see that it ended.

In a team, no one else in the team can open a session you keep until you file it in a project. A project shows the sessions filed in it to the member who made it, the people it names and the team's Owner and Admins, or to everyone in the team.

Delete on a session's page deletes the session at once, with its report, its passages and its links. For 90 days we keep a record of the deletion, with the session's ID, its workspace, who could open it and when it was deleted, and none of what it held, so your other devices remove their copies.

This browser keeps a copy of each session in your account that it lists or opens, so you can read it without a connection. When it next lists your sessions, it removes the copy of a session that was deleted, and once a day it removes the copies of sessions you can no longer open, unless a change you made there is still waiting to be sent. "Remove my sessions from this device", on your account page, removes every copy.

We count the questions you ask each month, and for a session kept on a device, how many characters of its transcript went to make its report and how many times the report was made, under your account and workspace and without any words. A count of questions is deleted 35 days after its last use, and a session's report counts when the record of that listening is.

Where your audio goes

When you press Start, your device sends the microphone's audio to our server, which passes it on as it arrives to Deepgram, to be turned into text, or to OpenAI when Deepgram fails and when you've asked for your language to be detected. In the demo, it goes to OpenAI. When OpenAI fails, Deepgram takes over, unless you've asked for your language to be detected. It travels encrypted, and our server holds it in memory only. When you pick a browser tab to hear the other side of a call, the tab's sound is mixed with the microphone's audio and goes the same way. A session sends none of your notes to our server. With each request we send OpenAI a scrambled form of your account's number, so it can act on abuse without learning who you are.

OpenAI's terms say it doesn't train its models on this data unless SaysHere opts in, and SaysHere hasn't. Under the same terms, OpenAI may keep the audio and the text of each request for up to 30 days to check for abuse. With every request, SaysHere tells Deepgram to leave the audio out of its programme for improving its models. Deepgram then stores neither the audio nor its text after it sends the text back. Both work for us under their business terms. Independent auditors have examined the security of each: Deepgram holds SOC 2 Type 1 and Type 2 reports, and OpenAI's API holds a SOC 2 Type 2 report and ISO/IEC 27001 certification.

Meeting bots

When you send a meeting bot, it joins the Google Meet or Microsoft Teams call as a participant and posts a notice in the meeting's chat before it listens. In Microsoft Teams it asks to join under the name its settings give it, which always holds "SaysHere". In Google Meet it shows the name of the SaysHere account it signs in with. Its notice names the person who sent it.

A workspace can hold several named bots, and every one of them posts the same notice.

The bot runs on our own servers, which Linode hosts, and records no audio. Our servers pass the call's sound to Deepgram as it arrives, to be turned into text, and hold it in memory only. With every request, SaysHere tells Deepgram to leave the sound out of its programme for improving its models. Deepgram then stores neither the audio nor its text after it sends the text back.

If you keep the transcript, our server stores it with the messages the bot read in the meeting's chat and who sent them, and OpenAI may write notes from it after the call. The transcript of your own bot or of a team bot stays in your account until you delete it or your account. In a team, it is deleted when you leave unless you shared it, like your other sessions there, and if you leave before a team bot's transcript reaches the team's Library, it goes to the team's Owner instead. A project bot's transcript is filed into that project, where the project's people can read it, and it stays there if you leave. A team's Owner and Admins can see the settings of a bot a member made for themselves, never its transcripts. If you keep nothing, the transcript is in our server's memory only while the bot listens, and nothing the bot heard or read is kept after it leaves.

For each bot we keep a record of its notice: when you sent it and when it was to join, the meeting platform, which bot you sent and its name in SaysHere, whether it was your own, your team's or a project's and which project, what it was set to write and how, whether you kept the transcript, the notice's version, the company that turned its sound into text, when the bot was admitted and posted its notice, how many times it posted the short notice for people who joined later, how and when it was stopped, and when what it took was deleted. The record also holds the first name you gave in the send form, encrypted, until a day after the bot leaves at the latest, and never any words of the meeting. It is deleted with the workspace that sent the bot, as your own workspace is when you delete your account.

We also keep a record of each bot's run: its platform, its times, how long it listened and why it ended. While the bot runs, the record also holds the meeting's link, the bot's name and its notice, and if you keep the transcript, it keeps the name and the notice until you delete the transcript or your account. Without them, it holds no words of the meeting and no names, and it stays after your account is deleted.

Anyone in the call can type SaysHere stop in the chat, or open the bot's notice link and press Stop it now. The bot then leaves, and everything it took is deleted.

In a Zoom meeting nothing joins the call. You connect your own Zoom account. When you press Start taking notes, Zoom sends our server the meeting's mixed sound and the name of whoever is speaking, and shows everyone in the meeting that its content is being sent to an app. Our servers pass the sound to Deepgram as they do for a bot and hold it in memory only. Our server drops the speaker's name with the sound, so the transcript carries no names. Zoom's own handling of the meeting is under your agreement with Zoom.

For your Zoom connection we keep your Zoom user ID, your Zoom account ID and the two tokens Zoom issues, sealed, until you disconnect Zoom in SaysHere, remove SaysHere from your Zoom account, or delete your SaysHere account. Disconnecting Zoom stops notes under way and deletes what they took, and transcripts you kept earlier stay. Removing SaysHere in Zoom also deletes the transcripts and Library copies made from your earlier Zoom meetings. To check that you host the meeting or are on its invitation, we read the meeting's details and your Zoom user's details from Zoom and keep neither. We keep each notice Zoom sends about a stream's start, stop or interruption sealed until our server has acted on it, and then only its ID.

Before notes start, you paste a notice with a stop link in the meeting's chat, and the notice's record keeps when you confirmed it and, where notes could not start, a code word for why. Anyone in the meeting can open the link and press Stop it now, and the host can stop the app from Zoom's own controls. Either one ends the notes and deletes everything they took.

Meetings from your Google Calendar

Google Calendar is off until you connect it on the Integrations page. SaysHere then asks Google, separately from signing in, for one permission, to see the events on the calendars you own, and for your Google account's email address. That permission can't change your calendar, and SaysHere never changes it.

While you stay connected, SaysHere reads the events on your primary calendar to find the meetings in the next seven days that have a Google Meet or Microsoft Teams link. It reads the next seven days each time you open the list of upcoming meetings in the Bot view, and it checks Google for changes while you stay connected. It shows you those meetings there and sends SaysHere's meeting bot to the ones you turn on.

For each of those meetings SaysHere keeps the event's identifiers, its start and end, its platform, its meeting link and its bot's notice link, both encrypted, whether you organise it, your answer to the invitation and how many guests it has, with your choice for it and what its bot did. It keeps none of a meeting's title, description or guests' addresses. The list reads the titles from Google each time it opens and holds them in memory alone.

For the connection SaysHere keeps the token Google gives it, encrypted with a key kept apart from the database and its backups, and your Google account's address, to show you which account is connected. It also keeps your settings for the list and a marker from Google that lets it read only what changed since its last read.

A bot sent from your calendar works as a bot you send by its link does. It uses your bot time, posts its notice in the meeting's chat and keeps the transcript in your account, as "Meeting bots" above describes. Its record of its notice also keeps a scrambled form of the meeting's identifier and whether you turned the meeting on yourself. SaysHere makes that form with a key of your account's own, which it keeps until you delete your account.

Within an hour after a meeting and the half hour that follows it have ended, SaysHere deletes the meeting's link and its bot's notice link from its record. It deletes the record itself 90 days after the meeting ended. A record whose bot is still being cancelled then goes once the cancellation is done.

Disconnect cancels the bots your calendar booked that haven't joined their meetings, asks Google to end SaysHere's access, and deletes the connection and SaysHere's records of your meetings, whatever Google answers. A bot already in its meeting stays until it leaves, and the transcripts you kept stay in your account. If Google doesn't confirm, the Integrations page says so, and you can remove SaysHere Calendar on your Google Account's linked apps page. Deleting your account disconnects Google Calendar the same way. Our nightly backups lose what was deleted within 30 days.

SaysHere never uses your Google Calendar data for advertising, to sell, to build profiles across people or to train any AI model, and it sends none of it to an AI service. The meeting bot, which runs on SaysHere's own servers, receives a meeting's link and times to join it. No one at SaysHere reads your calendar data, except with your written agreement for support or where security or the law requires it.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Fact-checking against public sources

Fact-checking against public sources is off until you turn it on, at Start or under Controls during a session. When you turn it off again, nothing more goes to Wikipedia. A check already under way still finishes, usually within seconds and always within about half a minute.

When a sentence said in a session states a fact about the world, such as a date, a number or who holds an office, OpenAI's model makes a search phrase of at most six words from what was said, naming its topic. Our server sends that phrase to English Wikipedia, run by the Wikimedia Foundation, and requests at most two of its articles. The phrase can include a name said in the conversation.

We never send Wikipedia your notes, documents, audio or transcript, who said what, your account, your email address or anything else that identifies you. The requests come from our server, so the address Wikipedia sees is SaysHere's.

To pick out the statement and compare it, up to five lines of the transcript (the three before it, its own line and the one after) and the Wikipedia sentences go to OpenAI, under the same terms as the text for lines and summaries. A line in which we find an email address, a phone number, a payment or bank account number or a similar identifier is never checked, and the lines around a checked line reach OpenAI with those parts replaced.

The Wikimedia Foundation receives these requests as an independent organisation, under its own privacy policy, which says personal information is in most instances deleted, aggregated or de-identified after 90 days.

We hold the lines, the statement, the search phrase, the articles and the sentences in memory for the check and never write them down or log them, apart from the checks a session you keep in your account keeps. Our server keeps the time of each search, with your account, for an hour, to hold the limit of 20 searches an hour, and the time of your account's last check for an hour, to space checks ten seconds apart. A check's cost is added to the day's spending total, which holds no content.

A check stays on screen until you press Done at the end of the session, and it isn't saved in the transcript you download. The sentences shown are Wikipedia's text under the CC BY-SA 4.0 licence, each with its article's address. A session you keep in your account keeps the checks it showed, with their licence notices.

Your browser keeps the fact-checking setting for your account. Removing your notes from this device does not change it.

We emailed everyone with an account before fact-checking began. We keep no record of who was emailed, only counts and times that show how far the sending got.

What stays on your device

Your notes are saved in your browser's storage on your device, under your account. They aren't stored on our server or copied to your other devices. The transcript of a session you don't keep is on your screen while you listen and is stored nowhere, unless you save it as a text file.

Signing out leaves them on the device, and another account signed in on the same browser can't see them. You can save a transcript as a text file; otherwise it's discarded when the session ends. Remove my notes from this device, on your account page, deletes all of it.

Notes you import

Your browser reads a file, a folder or text you import into your notes from your device. The import sends nothing of it to our server, and the notes it makes are kept with your other notes.

Our server fetches a web page you import from the address you give, so the page's site sees a request from SaysHere and never from your device. The page's title, text and address become a note kept with your other notes. Our server keeps nothing of the page beyond the counts that limit how many pages a workspace reads each hour and each day.

Our server reads a file you import from GitHub through a GitHub link you made, in the workspace you import into or in your own workspace, and never through a link another member made. It can read any repository that link reaches, including ones not chosen for the workspace's library. It reads the branch, tag or commit your address names, or the repository's default branch when the address names none. GitHub sends the file to our server, which passes its text to your browser. The file's text and path, and where on GitHub it came from, become a note kept with your other notes. With Keep importing on, which Import offers for a link in your own workspace, the link also chooses the repository for the workspace's library, as "Repositories you connect from GitHub" says. With it off, our server keeps nothing of the file beyond the counts that limit how many links and files a workspace reads each hour.

Our server reads a Google Drive file you import through your own Google Drive connection, and only a file you own. Google's file picker opens inside a folder your link names, or on a file your connection does not reach yet, and you pick what to import. From "A connected source", the picker opens on your Drive. Google sends each file to our server, which passes its text to your browser. Each file's name and text, and where on Drive it came from, become a note kept with your other notes. With Keep importing on, SaysHere also adds the file to the workspace's library, as "Files you add from Google Drive" says. With it off, our server keeps nothing of the file beyond the counts that limit how many links and files a workspace reads each hour.

"Read again" on an imported note reads its source again when you press it. Files kept in the workspace's library are read again as the library reads them.

Who else handles your data

• Deepgram turns audio into text.
• OpenAI turns audio into text.
• OpenAI writes the reports of the sessions you keep, indexes what you keep in your Library and writes the answers to the questions you ask there.
• GitHub sends us the files of the repositories you or your team connect. OpenAI indexes the text of those a workspace's library keeps and writes the answers you ask about them.
• Google sends us the files you pick from Google Drive when you import them into your notes, and when you add them to a workspace's library and once a day after. Its file picker loads in your browser only when you open it. OpenAI indexes the text of those a workspace's library keeps and writes the answers you ask about them.
• Google sends us the mail you connect from Gmail. OpenAI indexes its sanitized text and writes the answers you ask about it.
• Zoom sends us a Zoom meeting's sound and the name of whoever is speaking while notes you started in it run.
• Google sends us the events on your primary calendar while you stay connected to Google Calendar.
• Notion (Notion Labs, Inc.) receives what you save to Notion, a note's title and text or a session's notes, when you press Save to Notion, and keeps the page in your own Notion workspace.
• Slack receives the notes you send to your Slack link and handles them for the workspace the link belongs to, under that workspace's agreement with Slack.
• The Wikimedia Foundation receives the search phrases and the article requests, as an independent organisation under its own privacy policy.
• Stripe takes payments and holds your card details. We never see your full card number.
• Resend sends our emails to you: sign-in codes, mail about your account, your plan, payments and your team, and our notices of changes to this page.
• Google (Google Analytics) and PostHog receive the visit records described under "Cookies and tracking" once you turn on measurement, on the public pages alone, and act for us as processors; Microsoft (Clarity) receives them once you turn on recordings, on the public pages alone, as an independent controller under its own terms.
• Linode hosts our server and its database.
• Cloudflare carries the pages and the text between your device and our server, and stores our nightly backups. Your audio goes to our server directly.
• Google and GitHub (and each provider you sign in with) confirm who you are when you use them to sign in.
• Backblaze stores a second copy of our nightly backups.

If you sign in with Google, Google sends us a signed statement of your Google account's ID, your email address and whether Google has checked it. We keep the ID and the address to recognise you and use them for nothing else. Signing in asks Google for nothing more and keeps no token from Google, and we never receive your Google password. Connecting Gmail asks Google for a separate permission, which "Mail you connect from Gmail" below describes. Adding files from Google Drive asks Google for a separate permission too, which "Files you add from Google Drive" below describes. Connecting Google Calendar asks Google for a separate permission too, which "Meetings from your Google Calendar" below describes.

If you sign in with GitHub, GitHub gives us a token that lets us read your GitHub account's ID and the email addresses on your account. We read them once, keep the ID and the main address GitHub has checked, and discard the token; we never receive your GitHub password.

Repositories you connect from GitHub

GitHub is off until someone who may connect sources links it on the Integrations page. In your own workspace that is you, and you can also link it from Import on the Notes page. In a team it is the Owner and Admins, and Members where the team allows it. That person installs SaysHere's GitHub App on GitHub and can choose up to 20 repositories for the workspace's library. The app can read the contents of the repositories it is installed on and cannot change them.

SaysHere reads the documentation on each chosen repository's default branch, such as Markdown, PDF and Word files. If someone who may connect sources turns on Include code, for the link or for one repository, SaysHere also reads the source files of the repositories it covers, in common programming languages. It leaves out code a tool wrote, such as minified scripts. It never reads issues or pull requests. Each file's text becomes a document in the workspace's library, under the file's path, with its address on GitHub. When GitHub tells SaysHere of a push, it reads the files that changed, and once a day it checks for changes it was not told of.

To make the link, GitHub gives SaysHere a token that shows which installations and repositories the linking person can reach. SaysHere reads that once, asks GitHub to revoke the token, and stores no GitHub token. It keeps the name of the GitHub account the app is installed on, the installation's number, the names of the repositories the link can reach and the GitHub user number of the person who linked it. For each chosen repository it keeps the commit it last read and the paths of the files it read or left out. It keeps the identifiers of GitHub's notices for seven days.

In your own workspace only you can open the documents. In a team, the person who links GitHub chooses whether its documents go to the whole team or to one project, and the people who can see that place can open them. That choice also covers each later version SaysHere reads. OpenAI receives their text in passages to index it for the library. For a question asked in the library, it also receives the question, the passages found for it and the titles of their documents. OpenAI may keep what it receives and the answers it returns for up to 30 days to provide the service and check for abuse, longer only where the law requires it or to protect its services or others from harm, and it doesn't train its models on it unless SaysHere opts in, which SaysHere hasn't. SaysHere never uses them to train or improve any AI model, ours or anyone's.

Taking a repository off the link deletes its documents at once. Turning Include code off deletes the documents read from source files it no longer covers. Disconnect deletes everything the link read, and SaysHere uninstalls the app from the GitHub account once no SaysHere workspace links it. Uninstalling the app on GitHub, or removing a repository from it there, deletes what SaysHere read from it. Our nightly backups lose what was deleted within 30 days. A team's record keeps who connected or disconnected GitHub, and when.

Deleting a team removes its links the same way, and deleting your account removes the links of your own workspace. If SaysHere cannot reach GitHub to uninstall the app before such a deletion finishes, the app stays installed on that GitHub account. SaysHere reads nothing more through it, and you can uninstall it there. A link you made in a team stays with the team when you delete your account. It no longer names you or your GitHub user, and it keeps the name of the GitHub account the app is installed on, which is your login if you installed the app on your own GitHub account. The team keeps reading the chosen repositories until someone who may connect sources disconnects the link or the app is uninstalled on GitHub.

Files you add from Google Drive

Google Drive is off until you connect it on the Integrations page or from Import on the Notes page. SaysHere then asks Google only for the files you pick (Google's drive.file permission), separately from signing in. That permission also covers changing those files, and SaysHere only reads them. It reads only files you own.

Google's file picker is Google's own. Your browser loads its script from apis.google.com only when you press to open the picker, on the Integrations page or in Import on the Notes page, and that script loads the picker's code from apis.google.com too. The picker then opens inside SaysHere's page, as a frame of Google's page at docs.google.com. Like any request to a site, these requests carry your network address and your browser's identification string. Opening the picker tells Google SaysHere's address, SaysHere's browser key and project number for Google, a short-lived access token our server got from Google for your connection, the kinds of file offered and how many you may pick. On the Notes page it also tells Google the picker's title, and the folder or file a link names. You choose in Google's frame, signed in to Google. The frame then hands the page details of each file you pick, and the page uses its id and name. For a folder a link names, the page also uses the folder's name. What the frame keeps is Google's, on Google's own sites. SaysHere sets no cookie for the picker. The page holds the access token in its memory while the picker is open and stores it nowhere on your device.

SaysHere keeps each file's name and text as a document in the workspace you add it to, with the file's id and address on Drive, and reads the file again once a day while you stay connected. It keeps the token Google gives it for your connection until you disconnect, encrypted with a key kept apart from the database and its backups. It also keeps your Google account's address with the connection, to show you which account is connected.

The people who can see where you add a file can open its text. Your choice of where to add it also covers each later version SaysHere reads. Leaving a team, or being removed from one, deletes the files you added there, including those you shared with the team. They come from your own Google account, so they leave with you. OpenAI receives their text in passages to index it for the library. For a question asked in the library, it also receives the question, the passages found for it and the titles of their documents. OpenAI may keep what it receives and the answers it returns for up to 30 days to provide the service and check for abuse, longer only where the law requires it or to protect its services or others from harm, and it doesn't train its models on it unless SaysHere opts in, which SaysHere hasn't. SaysHere never uses them to train or improve any AI model, ours or anyone's.

A file you delete on Drive, or can no longer read, is deleted here at the next day's read. If Google stops honouring the connection, its files are deleted 14 days later unless you connect again. Disconnect deletes every copy made from your Drive, in every workspace, and asks Google to end SaysHere's permission. That also ends the permission you gave SaysHere to sign you in with that Google account, so Google asks for it again the next time you sign in. Deleting your account does the same. Our nightly backups lose what was deleted within 30 days.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Mail you connect from Gmail

Gmail is off until you connect it on the Integrations page. Before Google asks for your permission, you choose how much recent mail to include, the last 7, 30 or 90 days as your plan allows, and a maximum number of threads. SaysHere asks Google only for permission to read your mail, separately from signing in, and cannot send, change or delete mail.

SaysHere reads a limited set of recent threads. For each message it includes, it keeps the names of the sender and the recipients, the date, the subject, the labels, each attachment's name, size and type, and the message text. Email addresses and detected credentials are removed from each message before it is kept; that can remove useful text, and it can miss something. We never download attachments and keep no Bcc line. Each copy is deleted at most 24 hours after the read it came from, and sooner when Google's rules or the window you chose end it. SaysHere also keeps the address of the mailbox you connect until you disconnect Gmail or delete your account, so a reconnect can check that it reads the same mailbox. That address and your Google permission are encrypted with a key kept apart from the database and its backups.

Your own Search and Ask are where your mail is used. It stays personal to your account, with every answer made from it: no team, administrator, guest, share, export or message sent out includes it. OpenAI receives the sanitized text to index it for search, the words you search or ask with, and the passages an answer needs, each with its thread's title. OpenAI may keep what it receives and the answers it returns for up to 30 days to provide the service and check for abuse, longer only where the law requires it or to protect its services or others from harm, and it doesn't train its models on it unless SaysHere opts in, which SaysHere hasn't. Opening a page sends nothing anywhere.

We never use your mail, or anything made from it, for advertising, to sell, to build profiles across people or to train general models. No one at SaysHere reads it, except with your written agreement for support or where security or the law requires it.

Pausing stops reading and using your mail at once, and stored copies still expire. Remove from sources deletes one thread and keeps it out until you reset exclusions, disconnect, or reconnect after Google's permission ends. Disconnect deletes all stored mail and every answer made from it, then asks Google to end SaysHere's permission; if Google does not confirm, the Integrations page says so, and you can remove SaysHere in your Google Account's permissions. Losing the permission and deleting your account delete the stored mail too. OpenAI keeps what it received for up to 30 days to provide the service and check for abuse, longer only where the law requires it or to protect its services or others from harm. Our nightly backups hold no Gmail data, and restoring one ends every Gmail connection.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Notes you save to Notion

Notion is off until you connect it on the Integrations page. SaysHere then asks Notion for one permission, Insert content, which lets it add pages to the workspace you choose. That permission cannot read or change the pages already there. SaysHere asks Notion for no information about you, so Notion sends it no name, picture or email address.

Nothing goes to Notion until you press Save to Notion on a note. SaysHere then sends Notion the note's title and its text, and Notion makes a new page of them at the top of your workspace. Only you can open that page until you share it or move it in Notion. On Notion's Enterprise Plan, the workspace's owners can find any page in the workspace by its title or text, and that includes these pages.

If you save a session to Notion from its page, SaysHere sends the session's title and its notes: the summary, the decisions, the action items with the name each is assigned to, the open questions, the quotes from the meeting they rest on, and your own notes. It never sends the transcript.

Our server passes each page to Notion and keeps none of its text and no record of it. For the connection it keeps the token Notion gives it, encrypted with a key kept apart from the database and its backups. It also keeps your Notion workspace's name and ID, to show you which workspace is connected, and the ID Notion gives the connection.

Disconnect asks Notion to end SaysHere's access and deletes the token, the workspace's name and both IDs, whatever Notion answers. Deleting your account does the same. If you remove SaysHere in Notion instead, Notion ends its access there, and SaysHere keeps the connection's details until you disconnect it on the Integrations page or delete your account. The pages you saved stay in your Notion, under Notion's own privacy policy, until you delete them there. Our nightly backups lose what was deleted within 30 days.

Notes you send to Slack

Sending to Slack is off until you save a Slack link on the Integrations page. You make the link in your own Slack workspace, as an incoming webhook of an app you make there or a workflow that starts from a webhook. SaysHere has no app in your Slack workspace and reads nothing there.

When you press Send to Slack on a note, after you have read the exact text and ticked that everyone in the channel may see it, your browser sends the note's title and text to our server, which posts them to your link once and keeps no copy. The test message on Slack's row posts only SaysHere's own sentence.

SaysHere keeps your link encrypted with a key kept apart from the database and its backups, with its kind, its last four characters, when you saved it and when it last posted. Our logs record when a link was saved, removed or posted to and what Slack answered. They hold no link, workspace name or note text.

What you send then lives in that Slack workspace. The workspace's own settings decide how long Slack keeps it and who can read it, and SaysHere can't change or delete it.

Remove link deletes your link from SaysHere at once, and deleting your account does the same. The link keeps working in Slack until you delete it there. Our nightly backups lose what was deleted within 30 days.

Trying it without an account

The demo you start from the home page works the same way, and nothing you say in it is kept when it ends. We keep a record that a demo ran and for how long, and a scrambled form of your network address for two days, so the daily limit can apply.

Our staff, free periods and company domains

SaysHere's staff can see an account's email address, plan, listening time and payments. For a team, they can see its members and their roles, and its plan, seats, listening time and payments. Staff use this information to support the account and to give a team a free period. They also use it to see what those payments and that listening time cost us, so we can run the service and keep its books. They cannot see sessions, notes, transcripts or documents. We rely on our contract with you and on our legitimate interest in running the service. We keep this information for as long as the account exists.

A company that asks us to give its team a free period may give us the email address of the person who will run the team before that person has an account. We use the address to send them one email offering the free period, and to give them the team when they sign in with it. We rely on our legitimate interest in the company's request. The email says who we are, where we got the address, why we hold it, and how to decline or object. If the person has not signed in by the time the free period ends, or if we withdraw it, we delete the address.

When you sign in with an address at a mail domain that a company has confirmed to us as its own, we compare your address's domain with the company's. We do this to offer you the company's team. Where the company has chosen to have its people added to a team in a free period, we add you to that team as a member instead. We rely on our legitimate interest and the company's. You can hide the offer, and you can leave a team you were added to at any time.

If you are in a session someone else kept

If you are in a session someone kept with SaysHere, ask that person first; we help them answer. If you cannot reach them, or your request is about what SaysHere itself holds, write to team@sayshere.com and we will answer for what we hold.

Cookies and tracking

SaysHere sets one cookie to keep you signed in and, once you've signed in here with a code, one that remembers this browser for thirty days, so that someone else asking for codes to your address can't lock you out. While a sign-in is in progress it also sets short-lived cookies that protect it; each is gone within thirty minutes. While you connect GitHub, Google Drive, Gmail or Google Calendar, SaysHere also sets a cookie for that step alone; it is gone within fifteen minutes. Your browser also stores your notes, your colour choice for the page, your fact-checking setting and your analytics choice, if you made one.

We count visits with Plausible, open-source analytics software that runs on our own server. It sets no cookie and keeps nothing that names you or follows you from day to day: a visit is counted under a number made from a secret that changes every day, your network address and the identification string your browser sends. The secret is deleted after two days; the extra day only lets a visit that runs past midnight count once, so visits on days further apart can't be linked. Your network address and that identification string are not stored; what is kept from them is the browser's name and version, the operating system and the kind of device. The count goes from your browser to sayshere.com and no further.

Three other analytics services, Google Analytics, PostHog and Microsoft Clarity, receive a record of your visit only after you turn on their purpose, and only on the public pages while you are signed out: nothing of the app, your notes or your sessions reaches them. Neither Plausible nor any of the three ever receives what is said in a meeting, what you write in notes or documents, or anything you connect, such as your mail, calendar or files. Google Analytics and PostHog measure how people use the public pages and set cookies, and run only after you turn on measurement; they act for SaysHere as processors. Microsoft Clarity sets cookies and shows us how a page is used, with every piece of text on it masked, and runs only after you turn on recordings; it handles what it receives as an independent controller under Microsoft's own terms. Until you turn a purpose on, none of its services loads, sets a cookie or receives anything, and until you answer, Plausible alone counts. A page whose address carries a sign-in or invitation link is never recorded and is counted by its path only. None of the three is used to follow you from site to site through SaysHere.

The choices above give one switch for each purpose: counting visits without cookies, which is on until you turn it off, and measurement and recordings, which stay off until you turn them on and whose cookies recognise this browser on your next visit; Save choices keeps them for this browser, and the storage that signing in, your settings and this choice need is always on. A browser that sends the Global Privacy Control signal or Do Not Track turns every count off whatever you chose.

The first time a browser opens SaysHere we ask once, at the foot of the page, with Reject all, Choose and Accept all as keys of equal weight; Choose shows one switch for each purpose. Google Analytics, PostHog and Microsoft Clarity run only after you turn their purpose on; until you answer, Plausible alone counts.

When you are signed in, your answer is also kept on your account. A purpose you turn off stays off in every browser where you are signed in; one you turn on runs only in a browser where you turned it on, and a browser that holds no answer of yours asks you. That record holds the purposes you turned on, the version of the words you answered, when you answered, whether your browser sent a privacy signal, and an identifier of the signed-in device that answered; it never holds your network address. Where a browser and your account hold different answers, a purpose runs only if both have it on, and you can change yours at any time under Analytics choices at the foot of any public page or with the choices above.

If you are in a team

The organisation that buys a Team plan is the controller of what its members put in the team, and SaysHere processes that information for the organisation to provide the service.

Everyone in the team can see your name and role. If you have set no name, Members see the first letter of your email address and its domain instead. People you invite to the team see your name, or the first letter of your email address and its domain if you have set no name, in their invitation and on the join page, before they join. The team's Owner and Admins can also see your email address, how much listening time you've used in the team and the sessions you share in it. This includes people who join the team later and anyone made an Admin or its Owner later, and they can also see what you shared before then. No one else in the team can open a session you have not shared. Your personal workspace stays separate from the team.

When you leave or are removed from a team, you can no longer open anything in it, and a session you are running in it stops. What you shared with the team stays with it under your name. Sessions, documents and folders you did not share are deleted, and the share links you made in it stop working.

Files you added from Google Drive are deleted when you leave the team or are removed from it, including those you shared. They come from your own Google account.

We show the team's Owner and Admins your email address and the listening time you use in the team because the Team rules you agree to when you join are part of our contract with you, and because the organisation has a legitimate interest in running its own seats and listening time. We do not ask for your consent to this. Nothing from your own plan or your personal workspace is shown to them.

Your Notion connection is your own. In a team, Save to Notion sends what you save to the Notion workspace you connected, and no one else in the team can save through your connection.

Your Google Calendar connection is your own. The bots it sends keep their transcripts in your own workspace, and no one else in the team sees your calendar or its meetings.

Selling your data

We don't sell or rent your personal information, and we don't share it for advertising. Nevada residents may still send a request not to sell to team@sayshere.com, and we'll answer within 60 days.

Your choices

• To see or correct what we hold about you, write to team@sayshere.com from the address on your account.
• To delete a session you kept, use Delete on its page.
• To delete your account, use Delete account on your account page. Any plan is cancelled at Stripe first, then your account is removed, apart from the records described above. Your account's rows and your kept sessions are removed at once, or as soon as Stripe confirms a paid plan's cancellation, and from our backups within 30 days. What stays is the record that the account was deleted, beside the records described above.
• To clear a device, use Remove my notes from this device on your account page.
• To disconnect GitHub or Google Drive, use Disconnect on the Integrations page. In a team, only those who may connect sources can disconnect GitHub. What a workspace's library read from it is deleted, and our backups lose it within 30 days. Notes you imported from it stay in your notes until you delete them.
• To disconnect Google Calendar, use Disconnect on the Integrations page. SaysHere's records of your meetings are deleted, and our backups lose them within 30 days.
• To cancel a plan, use Manage or cancel on your account page. If you can't sign in, write to team@sayshere.com from your billing address.
• What we do with anything said about health is in our consumer health data privacy policy.

Telling the people you talk with

SaysHere records no audio, but what people say is sent to Deepgram or OpenAI to be turned into text, and a transcript is stored when you choose to keep a session. Some places, and some schools, require everyone's agreement first. Tell the people you're talking with before you start, and get their agreement where the law or your school requires it. The Start screen gives you the sentence to say for what you chose.

Who may use it

SaysHere is for people 18 or older, and an account found to belong to someone younger is deleted.

If your information is exposed

If someone gets access to information we hold about you without our permission, we'll email the address on your account within 30 days of finding out, and sooner if we can. We'll say what happened, what was involved and what we've done about it, and we'll put a notice on this page.

Changes to this page

When we change what we collect or who handles it, we'll update this page and its date, and email everyone with an account before the change takes effect.

Contact

Manic Agency LLC, 2831 St Rose Parkway, Suite 200, Henderson, NV 89052, United States.

team@sayshere.com