Raava Privacy Policy

Last updated: October 14, 2026

Raava is a personal automation tool: a Chrome extension and a desktop application that observe how you work, find repetitive workflows, and build agents to automate them. This policy explains exactly what is recorded, where it goes, and how you stay in control. It is written to be read, not skimmed past.

The short version

Everything Raava records stays on your own computer. The Chrome extension sends data to exactly one place: the Raava application listening at 127.0.0.1:8765 on your machine. We — the developers — never receive, see, or have access to your data. There are no tracking pixels and no third-party services in the extension. The desktop application sends us one thing on its own: a daily health report made of numbers and version strings (described below), which you can switch off.

What the extension records

To reconstruct your workflows faithfully, the extension captures, on the pages you use while recording is on:

• Clicks and the labels of the buttons/links you click
• Text you type into forms and spreadsheet cells
• Copy and paste events, including the copied/pasted text
• Navigation: the domain and path of pages you visit (query strings are dropped and long IDs in paths are replaced with a placeholder) and page titles (email addresses are stripped before storage)
• Occasional screenshots of the visible tab, used to give workflow summaries visual context
• Google Drive file moves (which file moved to which folder), detected at the network layer because Drive performs moves in a way page scripts cannot see

What is never recorded

• Passwords. Anything typed into a password field (input type="password") is never captured — only the fact that a value was entered and its length.
• Anything while paused. One click on the Raava toolbar icon pauses all recording; nothing is captured or retroactively recovered from pause windows.
• The Raava dashboard itself. Activity on 127.0.0.1/localhost is excluded.

Where your data goes

1. Your machine, and by default nowhere else. All captured events go to the Raava application on your computer and are stored in a local SQLite database in Raava's data folder. The extension has no other network destination.
2. Your own Anthropic API key (AI analysis). The Raava desktop application — not the extension — sends summaries of recorded sessions to Anthropic's Claude API to detect patterns and learn skills, using an API key you provide, under your Anthropic account. Before anything is sent, an anonymizer scrubs credentials/API keys and personal-data patterns (email addresses, phone numbers, card numbers, IDs, IP addresses, file paths). Anthropic's handling of API data is governed by their policies: anthropic.com/legal/privacy
3. Your own accounts (agent actions). When you explicitly run an agent that Raava built for you, it acts through your own logged-in accounts (for example your Google account) to perform the workflow — the same way you would by hand. Nothing about this is shared with the developers.
4. A daily health report to us (numbers only, switchable). Once a day the desktop application sends a short report to a server we run: Raava's version, your operating system name and version, how long it has been running, counts (sessions, patterns, agents, runs by outcome, suggestions, captured events), what your AI calls cost, and the locations in Raava's own code where errors occurred (file, function, line and error type — never the error message, which could quote your data). The report carries no names of patterns or agents, no URLs, page titles, typed text, file paths, email addresses, keys, or IP addresses; the server rejects any report containing a field outside that fixed list. It is tied to your invite code, not to an account. Settings shows the exact next report and has a switch to turn it off. The server also records when your copy last checked for updates.
5. Troubleshooting files, only when you send one. Settings has a "Report a problem" button. It writes a redacted troubleshooting file to your Desktop (version numbers, settings, and error excerpts with recorded content and secrets stripped out structurally) and offers to send it to us; nothing is sent until you press Send. If Raava crashed, it offers the same on its next start. Sent files are deleted after 30 days.

There is no other path by which anything about your use of Raava reaches the developers, and no path at all by which your recorded data does. We could not sell your data even if we wanted to — we never have it.

Your controls

• Pause / resume any time from the extension popup or the desktop app tray.
• Review what was recorded and what any AI call would receive in the Raava dashboard's per-session Privacy panel.
• Delete everything by deleting Raava's local data folder (this removes the database, screenshots, and generated agents) and uninstalling the extension and application. There is no server-side copy to chase.

Data retention

Data is retained on your machine until you delete it. Raava sets no expiry and performs no off-device backup. On our side, health reports are kept for 90 days and troubleshooting files for 30 days, then deleted.

Changes to this policy

If the extension's data practices ever change (for example, a new capture type), this policy will be updated and the "Last updated" date bumped before that version ships to the Web Store.

Contact

Questions or concerns: rypuri0@gmail.com