Rice for companies and regulated teams
Where Rice keeps each piece of data, what leaves the computer and when, and how that maps to the LGPD, the Brazilian data protection law. Every statement describes the current version of Rice and can be checked in the source code.
Updated
Where does Rice keep each piece of data?
| Data | Where it is kept | Leaves the computer |
|---|---|---|
| Audio | On the computer, in the meeting folder. You can turn off “Keep meeting audio”. | Never. |
| Transcript | On the computer, as a Markdown file. | As text, to the AI you chose, when notes or answers are generated. |
| Notes | Written by the AI you chose, or by a model on the computer, and saved on the computer. | The transcript goes in and the notes come back. Nothing, with a local model. |
| Memory across meetings | On the computer, in one file in the meetings folder. It can be edited, erased or turned off. | The notes of each meeting, once, to extract who asked, promised and decided what. |
| Chat and annotations | On the computer, in the meeting folder. | Your question and the relevant passages, when you ask. |
| Screenshots (off by default) | In the meeting folder. | Recent transcript text, to decide when to capture. The image only with an API key. |
| Voice separation (beta, off by default) | Runs on the computer. Voices are compared only in memory and never saved. | Never. |
| Keys and tokens | macOS Keychain, or Windows DPAPI. | Only to the provider they belong to. |
| Calendar (optional) | Read on the computer. Google Calendar access is read-only. | Only the title of a meeting you record, with its notes. |
What leaves the computer, and when?
These are all the connections Rice makes. None of them carries audio, and every send to the AI appears in the meeting’s receipt.
- The AI provider you configured, when notes, chat answers, memory, live ideas, follow-up emails or screenshot decisions are generated. Text only, except screenshot images with an API key. With a local model, this stays on the computer.
- GitHub, once a day, with an anonymous request to check for a new version. Turn it off in Settings › Updates.
- Model downloads, once: the transcription model and, if you use voice separation, the voice model. Both are checked by SHA-256.
- Google Calendar, only if you connect it, read-only. The macOS Calendar works without it.
- Optional tools you turn on: web search in the chat, War room internet sources and MCP servers. All are off by default.
How to block it
100% local mode, in Settings › Privacy, with the local model: web search, tools, War room internet sources, Google Calendar, update checks and model downloads are blocked, and the app’s network layer refuses any destination that is not the computer itself.
Without a local model: do not connect an AI provider and turn off the update check. Recording and transcription keep working; notes and chat do not.
Which privacy features does Rice have?
| Feature | What it does | Status |
|---|---|---|
| No servers, account or telemetry | Rice has no backend. Nothing about you or your meetings reaches the project. | Available |
| Private files | Everything Rice creates is readable only by your user (permissions 0700 and 0600). | Available |
| AI tools without file access | The AI command-line tools run without tools that touch your files; Antigravity runs inside a macOS sandbox. | Available |
| Delete to Trash | Deleting a meeting moves its folder to the Trash. No copy is kept elsewhere. | Available |
| Open code | MIT license. Anyone can audit what the app does. | Available |
| Receipt per meeting | “What left this computer” lists each send to the AI: kind, time and provider, never the content. It can be copied or saved as PDF. | Available |
| Consent notice | When recording starts, a notice suggests telling participants, with a ready sentence to copy. The receipt records when it was copied. | Available |
| Voice signature never saved | Participant identification compares voices only in memory during the recording; no voice signature is written to disk. | Available |
| Personal data redaction | CPF, CNPJ, card numbers, emails, phone numbers, RG and CEP are replaced by markers before text leaves the computer and restored locally in the answer. Always on in folders marked Sensitive. | Available |
| Retention per folder | Audio after 7, 30 or 90 days, or whole meetings after 6 months or 1 year, move to the Trash in a daily sweep. | Available |
| 100% local mode | Only the local model is accepted, and every connection that is not to the computer itself is refused. | Available |
How does Rice relate to the LGPD?
Your company remains the controller of the meeting data. Rice is a tool on your computer and the project receives none of that data.
| Topic | What Rice does | What stays with you |
|---|---|---|
| Transparency (art. 6, VI) | Open code, data in readable files, a receipt per meeting of what was sent, and this page listing every outgoing connection. | Tell participants that the meeting is recorded, why, and which AI processes the text. |
| Legal basis (art. 7) | Does not decide it. A consent notice with a ready sentence appears when recording starts. | Choose and document the basis, such as consent or legitimate interest. |
| Necessity and retention (art. 6, III; art. 15 and 16) | Retention per folder moves expired audio or meetings to the Trash, audio can be turned off, and the memory can be edited or erased. | Set how long meetings are kept and delete them when the purpose ends. |
| Security (art. 46) | Private files, keys in the system keychain, personal data hidden before sending, no copy on third-party servers. | Disk encryption (FileVault or BitLocker) and control of who uses the computer. |
| International transfer (art. 33) | Text goes only to the provider you choose, or nowhere with a local model and 100% local mode. | Check where that provider processes data and what its contract says. |
This page is a technical description to support your own assessment. It is not legal advice.