Privacy policy

Who we are

Rhea is run by Rhea. We are the controller of the personal data described here. For anything about privacy, write to privacy@sayhall.com.

When a company buys Rhea for its people, the company decides how Rhea is used at work. For meetings shared with a company's team we act on the company's instructions as its processor, under our data processing agreement.

What we collect

Your account

Your name, your email address and whether it is verified, and the identifier of the way you sign in: Apple, Google, Microsoft or a code sent to your email. If you belong to a team on Rhea, the team, your role in it and whether you hold a paid seat.

Your meetings

While you record, the app keeps the recording on your device and sends short audio clips over an encrypted connection, through our server, to be turned into text by OVHcloud in France. Neither our server nor OVHcloud keeps the clips. The grey preview you see while someone is still speaking is made on your device by Apple's dictation.

We store what the recording becomes: the transcript and its translations, the summary, decisions, open questions and actions, the questions you ask about your meetings and their answers, the Tabs you put meetings in, and how much you used Rhea this month, which your plan's limits are counted from.

Payments

If you buy Pro in the iPhone or Mac app, Apple takes the payment and RevenueCat tells us the subscription status. On this website, Lemon Squeezy sells the plan as our reseller, takes the payment and keeps the billing details; we receive the plan, its status and dates, and for Business the number of seats. We never see or store your card number.

This website

The marketing pages set no cookies and run no analytics. The account, checkout and team pages use Clerk's sign-in cookie to keep you signed in, and nothing else. Our hosting keeps standard server logs (IP address, page, time) to keep the site secure.

Why we use it, and on what basis

To provide Rhea to you: recording, transcribing, translating, summarising, Tabs, Ask, sharing and keeping your devices in step. Basis: our contract with you (GDPR article 6(1)(b)).
To run your plan: counting use against its limits, and billing. Basis: contract and, for tax records, legal obligation (6(1)(b) and (c)).
To keep Rhea secure and working: preventing abuse and fixing faults. Basis: our legitimate interest in a safe, reliable service (6(1)(f)).

We do not sell personal data, show ads, or use your meetings to train AI models, ours or anyone else's.

What happens to a meeting

Here is one meeting from the microphone to deletion: where each piece goes, and whether anyone keeps it.

1
You record
The recording is made and kept on your iPhone or Mac. It is never uploaded as a file. The grey preview you see while someone is still talking is made on the device by Apple's dictation.
Stays on your device
2
Short clips go to our server
As you talk, the app sends short clips, encrypted, to our server in the EU. The server passes them on and does not save them.
Passed on, not saved
3
It is turned into text in the EU
The clip goes to OVHcloud's speech-to-text in France, which does not keep it and sends the text straight back. It is the only service that hears your audio; if it can't take a clip, the clip goes nowhere else.
Kept by no one
4
The text is saved for you
The transcript is stored in your account on our server in the EU, with encrypted backups in the EU. This is the only place your meetings are kept.
Stored in the EU
5
AI writes the summary and answers
To translate, summarise or answer a question, our server sends the meeting text to an AI model, also with zero data retention, and saves the result next to the transcript.
Kept by no one
6
You delete it
Delete a meeting or your account in the app. It leaves our database at once and our backups within 35 days.
Gone

What zero data retention means

The AI services we use need your audio or text for a moment, to do their work. Zero data retention is the agreement that they use it for that moment and nothing else:

No copy is kept. The service answers the request and does not store the audio, the text or its answer, in its databases or its logs. The only thing it may keep is a record that a request happened, such as its time, size and cost, for billing. That record holds nothing from your meeting.
No training. Your meetings are never used to train or improve anyone's AI models.
No one reads it. With nothing stored, there is nothing for the service's staff to look at later.
It is not a setting we hope is on. Each service agrees to it in its terms. For text, our server also demands it on every single request, and a request that can't be handled that way isn't sent. Audio goes to one service only, OVHcloud's speech-to-text in France.

So a copy of your meeting exists in two places only: on your own devices, and on our server in the EU with its EU backups. When you delete a meeting, those are the copies that go.

Where it runs

Your meetings are stored only in the EU, and your audio is turned into text in the EU, at OVHcloud in France. The other AI work runs where the models are: Microsoft Azure in the EU first, and some text models at services in the United States. Sign-in, App Store purchases, payments and email also run from the United States; they see your name, email and plan, never your meetings.

For those text models, “United States” means where the work is done for the few seconds it takes, under zero data retention; nothing from your meetings is stored there. Every transfer is covered by the EU-US Data Privacy Framework where the provider is certified, and otherwise by the European Commission's standard contractual clauses, the EU's own contract terms for this.

Every service, what it does, what it sees and where it runs is on our subprocessors page. We give at least 30 days' notice there before adding a service that handles meeting content.

Recording other people

Meetings involve other people. Whoever records is responsible for telling the people in the meeting that Rhea is recording, and for having a lawful reason to do so, as with any recorder. People who appear in a recording can contact us about their rights; we will work with the person who recorded it.

Sharing

A meeting you share with your team, or file into a team's Tab, can be read by the people in that team. Meetings shared with a team stay with the team if you leave it.
Summaries you send by email go to the addresses you choose.
We disclose data to authorities only when the law requires it, and we tell you unless the law forbids it.

How long we keep it

Meetings, transcripts, summaries and Tabs: until you delete them or your account.
Deleted data leaves our live database at once and our backups within 35 days.
Billing records: as long as tax law requires, which is 7 years in the Netherlands.
Website server logs: 14 days.

Your rights

You can access, correct, export or delete your data, object to processing based on legitimate interest, and withdraw consent. Most of this you can do in the app, including deleting your account. For anything else, write to privacy@sayhall.com; we answer within one month. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, or the authority where you live.

Security

Everything between the app, our server and the AI services travels encrypted over TLS. Sign-in uses short-lived tokens, and a stolen refresh token stops working the moment it is reused. Backups are encrypted before they leave our server and are kept with a different provider. We report a personal data breach to the authority within 72 hours and to the people affected without delay.

Children

Rhea is for work and is not meant for anyone under 16.

Changes

When we change this policy we update the date at the top. If a change matters, we tell you in the app or by email before it takes effect.