Consumer health data privacy policy

What we collect and why

While a session runs, what is said passes through our server in memory on its way to Deepgram or OpenAI, which turns it into text. Every AI service that receives it is independently audited for security, works for us under business terms and doesn't train its models on it. None of it is written down unless you keep the session in your account. If you keep a session in your account, its transcript and the notes made from it can include things said about someone's health: yours, or that of the people you talk with. We store them to show you your kept sessions, to write their reports, to search them and answer your questions about them, and to share them where you choose to, and use them for nothing else. Fact-checking against public sources is off until you turn it on, at Start or under Controls during a session. While it is on, SaysHere can check a fact about the world, such as a date, a number or who holds an office, when someone states it in the session. OpenAI's model makes a search phrase of at most six words from what was said, naming its topic, and our server sends that phrase to English Wikipedia. The phrase can name a condition, a treatment or a medication said in the session. It never includes your account, your email address or your notes. Our server holds it in memory for the check and never writes it down, apart from the checks a session you keep in your account keeps. 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. If you connect Gmail, the recent mail you include can mention someone's health. SaysHere keeps a sanitized copy of each message for at most 24 hours after the read it came from, to search it and answer your questions about it in your own Search and Ask. If you or your team connect GitHub, or you connect Google Drive, the files SaysHere reads from them can mention someone's health. SaysHere keeps their text in the workspace's library, reads them again while they stay connected, and uses them for search and questions in that library. If you connect Google Calendar, your meetings' titles can mention someone's health. SaysHere reads them from Google with your meetings, shows them in your list of upcoming meetings and keeps none of them. Notes you save to Notion can mention someone's health. SaysHere sends them to your Notion only when you press Save to Notion and keeps none of their text. A note you send to Slack can mention someone's health. It passes through our server on its way to Slack, and we keep nothing of it. A session kept on this device stays in your browser, and our server holds its text in memory only while it makes the session's report or answers a question you ask about it. Notes you write on a kept session's page, and a document you add to the Library, can mention someone's health too. We keep their text in your Library and use it the same way.

Where it comes from

From what is said near your microphone during a session you chose to keep, from the recent mail you include if you connect Gmail, from the documents you add to the Library, from the repositories you or your team connect from GitHub, from the files you add from Google Drive, and from the meetings on your Google Calendar if you connect it.

What we share

We don't sell consumer health data. While fact-checking against public sources is on, the search phrase described above goes to the Wikimedia Foundation, which runs Wikipedia. When you press Save to Notion, we send that note, or that session's notes, to Notion, into the workspace you connected. Notion holds it under your own agreement with Notion. When you press Send to Slack, we pass the note's title and text to the Slack channel your link names, after you have read the exact text and ticked that everyone in that channel may see it. We pass it at your request alone and keep no copy. When you share a kept session by a link, anyone with the link can read what you chose to share until the link ends: its report, and its transcript if you chose that too. Your browser encrypts the copy, and we store it without being able to read it. In a team, the people a project is shown to can read the sessions filed in it. We share nothing else.

Who we share it with

The Wikimedia Foundation, which runs English Wikipedia, receives the search phrases our server sends while fact-checking is on and handles them under its own privacy policy. A phrase can name a condition, a treatment or a medication said in the session, and it never includes your account, your email address or your notes. A note you save to Notion goes to Notion, which keeps it in the workspace you connected. A note you send to Slack goes to Slack, which holds it for the workspace your link belongs to, and to the people who can read that channel. A session you share by a link goes to the people who open the link, and a session filed in a project to the people in your team the project is shown to. No other third party and no affiliate receives consumer health data from us. OpenAI works on it only for us, to write what you asked for, to make the search phrases and to compare what was said with Wikipedia's sentences; the law counts that as our own processing, not as sharing. OpenAI processes the mail you connect from Gmail for us, to index it and to answer your questions about it, which the law counts as our own processing, not as sharing. OpenAI may also use that mail to check for abuse and to comply with the law. OpenAI processes the files connected from GitHub or Google Drive for us, to index them and to answer questions about them, which the law counts as our own processing, not as sharing. OpenAI may also use them to check for abuse and to comply with the law. OpenAI processes kept sessions and documents for us, to write their reports, to index them and to answer questions about them, which the law counts as our own processing, not as sharing.

Your rights and how to use them

You can ask whether we hold consumer health data about you and get a copy, withdraw your consent, and have it deleted. Turning fact-checking off withdraws your consent to the search phrases: nothing more goes to Wikipedia, apart from a check already under way. Disconnecting Gmail on the Integrations page withdraws your consent to its use and deletes the stored mail at once; 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, and our backups hold no Gmail data. Disconnecting a GitHub link or Google Drive on the Integrations page withdraws consent to the use of what SaysHere read through it and deletes that at once; in a team, only those who may connect sources can disconnect GitHub. 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. Disconnecting Google Calendar on the Integrations page stops SaysHere reading your calendar. Disconnecting Notion on the Integrations page stops anything more going to Notion. Pages you already saved stay in your Notion, where you can delete them. Remove link on the Integrations page stops anything more going to Slack. A note already sent stays in Slack until someone in that workspace deletes it there, and SaysHere can't delete it. Revoke, under a session's Share, ends a link at once. Deleting a kept session or a document deletes it with its passages and its links. Delete a kept session on its page, or write to team@sayshere.com from the address on your account; you don't need to make a new account. We answer within 45 days. Deleted data leaves our backups within 30 days. If we refuse a request, reply to that answer to appeal, and we'll answer the appeal in writing within 45 days.