Privacy Policy

Last updated 14 June 2026

Reus is a meeting recorder that runs on your own machine. It was built local-first: your meetings are recorded, transcribed, and turned into notes on your device, and your audio never leaves it unless you deliberately turn on a cloud feature. This policy explains exactly what data Reus handles, where it lives, who (if anyone) it is shared with, and the controls you have.

Reus is operated by dME Network (“Reus”, “we”, “us”). It covers the Reus desktop app, the Reus web app, and this website, getreus.com. Questions about privacy? Email privacy@getreus.com.

The short version

• Recording, transcription, and note-writing run on your device by default. Your audio is never uploaded unless you choose a cloud transcription feature.
• We use no analytics, no telemetry, no advertising, and no crash reporting. We do not track you across the web and we do not build a profile of you.
• You sign in with Google to create a Reus account. We store only your basic Google profile (email, name, avatar) to run that account.
• If you connect read-only Google Calendar, it is used only on your device to show today’s meetings and remind you to record. Your calendar data is never sent to or stored on Reus servers.
• Optional cloud features (paid transcription, library sync, AI notes) send specific data to specific providers, listed below — and only when you actually use them.
• We never sell your data, and we never use it for advertising or to train AI models.

1. Data that stays on your device

By design, the heart of Reus runs locally. Unless you turn on a cloud feature, the following never leaves your computer:

• Recordings. Your microphone audio, and — if you enable it — the other side of the call (system / tab audio). On the desktop app these are saved as audio files in the app’s data folder; in the web app they are stored in your browser’s local database (IndexedDB).
• Transcripts and notes. The text of your meetings and the AI-generated summaries, key points, decisions, and action items. Stored in a local database on the desktop app, or in your browser on the web app.
• Settings and credentials. Your preferences, any API keys you add for your own AI/transcription providers, and your Google Calendar token live in local app storage on your device. Treat your app data folder as sensitive, as you would a browser profile.

Reus contains no analytics or telemetry SDKs of any kind. The only automatic outbound request the app makes on its own is an update check against our public release feed on GitHub, and a one-time download of the on-device transcription model from Hugging Face — neither carries any personal data.

2. Your Reus account

To use the app you sign in with Google. When you do, Google sends us your basic profile and we store it on our servers to run your account:

• your Google account identifier, email address, name, and avatar URL;
• your plan and transcription-credit balance;
• account timestamps (when you signed up and last signed in).

We use this only to identify you, sync your library to your other devices, and meter paid features. Your session is kept as a secure cookie or token on your device; on our side we store only a one-way hash of that token, never the token itself. We do not receive or store your Google password.

3. Cloud library sync (optional)

When you are signed in, Reus can sync your meeting library across your devices. Sync uploads your meeting text — titles, transcripts, and notes — to our database so you can reach it from another device. Your recorded audio is never uploaded by sync; it stays on the device that recorded it. When you delete a meeting, the deletion is propagated so the cloud copy is removed too.

4. Cloud transcription (optional, paid)

By default, transcription runs entirely on your device using a local Whisper model. If you choose Reus cloud transcription, your recording is uploaded to our server and immediately relayed to our speech-to-text provider (Groq) to produce the transcript. The audio is streamed through and not stored by Reus — we keep only the resulting transcript text (which then syncs with the rest of your library) and a record of how many seconds were transcribed, to meter your credits.

You may instead point Reus at your own transcription provider (any OpenAI-compatible endpoint) using your own API key. In that case the audio goes directly from your device to that provider; Reus is not in the loop.

5. AI notes

When you generate notes, Reus sends the meeting transcript text (plus, to help attribute action items, your name and email if known) to the AI provider you have chosen — for example Anthropic’s Claude or an OpenAI-compatible model — using your own API key or the Claude subscription you already have. This request goes directly from your device to that provider. Reus’s own servers never send your transcripts to any AI model. Your audio is never sent for notes; only the text is.

6. Google Calendar (optional, read-only)

Reus offers a lightweight calendar feature. If you connect it, Reus requests the read-only Google Calendar scope (https://www.googleapis.com/auth/calendar.readonly). This access is used for a single purpose: to show you your meetings for today and to fire a local reminder shortly before each one so the recorder is ready.

• Read-only. Reus can never create, edit, or delete anything on your calendar.
• Minimal. Reus reads only today’s events from your primary calendar, and from each event uses only the title, location, and start/end times. It does not read attendees, descriptions, attachments, video-conference links, or any other calendars.
• On-device only. The calendar request goes directly from your device to Google. Your calendar events are held in memory for your current session and are never transmitted to, or stored on, Reus servers, and are never written to disk.
• Revocable. You can disconnect the calendar at any time in Settings, which stops all calendar reads and clears the stored token from your device. You can also revoke Reus’s access from your Google Account permissions.

7. Google user data and the Limited Use policy

Reus’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained from Google APIs (your Google profile for sign-in, and read-only calendar events) is used only to provide and improve the user-facing features described above. We do not transfer or sell this data to third parties; we do not use it for advertising; and we do not use it to train generalized AI or machine-learning models.

8. Payments

If you buy transcription credits, payment is handled by Stripe on their own secure checkout page. Reus never sees or stores your card details. We store only the fact that a purchase happened (a Stripe event reference and the resulting credit grant) against your account.

9. Website & waitlist

If you enter your email on getreus.com to join a waitlist or hear about new builds, we store that email (and which list you joined) so we can contact you. Ask us any time and we’ll remove it. Our website and servers are hosted on Cloudflare; like any web service, Cloudflare processes your IP address and request metadata at the edge to serve and protect the site.

10. Who your data is shared with

We don’t sell your data or share it for advertising. We use a small set of service providers, and only for the features you use:

We may also disclose information if required by law, or to protect the rights, safety, and security of our users and our service.

11. Data retention

• On-device data (recordings, transcripts, notes, settings) stays until you delete the meeting or clear the app’s data. You are in control of it.
• Account and synced data is kept while your account is active. Deleting a meeting in the app removes its synced copy. To delete your whole account and all synced data, email us and we’ll remove it.
• Cloud-transcription audio is not retained — it is discarded once the transcript is returned.
• Calendar events are never stored by us; they live only in memory while the app is open.
• Waitlist emails are kept until you ask us to remove them.

12. Security

Reus is local-first, which keeps most of your data off the network entirely. Every network request the app makes uses encrypted HTTPS. On our servers we store only a hash of your session token, never card data, and never your audio. Your API keys and calendar token are stored locally on your device. No system is perfectly secure, but we minimise what we hold so there is little to expose.

13. Your choices and rights

You are always in control:

• Disconnect Google Calendar at any time, which stops all reads and clears the local token.
• Delete any meeting, which removes the local copy and any synced copy.
• Sign out to end your session.
• Request access to, correction of, or deletion of the account data we hold.
• Revoke Reus’s Google access from your Google Account.

Depending on where you live (for example under the GDPR or CCPA), you may have additional rights over your personal data. To exercise any of these, email privacy@getreus.com and we’ll help.

14. Children

Reus is not directed to children under 13 (or the minimum age in your country), and we do not knowingly collect their data.

15. International users

Reus is operated with infrastructure that may process data in countries other than your own. Where we transfer data, we rely on appropriate safeguards. By using Reus you understand that your account data may be processed in those locations.

16. Changes to this policy

We may update this policy as the product evolves. When we do, we’ll change the “last updated” date above, and for material changes we’ll do our best to let you know in the app.

17. Contact

dME Network — privacy@getreus.com. We read every message.