This policy explains what riru collects and why, across the riru website (riru.app), the riru Chrome extension, and the servers behind them ("riru", "we", "us"). The rule we build to: collect only what the job you asked for needs, keep as little of it as possible, and never sell any of it. Questions or requests: hello@riru.app.
1. Information we collect
Account information. You sign in with a Google account through Clerk, our sign-in provider. We store the email address, name, and profile image Google shares, keyed to your account id. We never see your Google password.
Chats. Your prompts, the agent's replies, and files you attach are stored so you can reopen a chat. Pages the agent reads or acts on become part of the transcript: excerpts of their content, and their titles and addresses. Long page snapshots are compacted to summaries when saved. When a chat grows long, the agent writes notes on its older part (the goal, the constraints and decisions you stated in your own words, where things stand, what it learned, and open questions) and stores them with the chat; the full transcript stays as it was.
The tab you were on. When you send a prompt, the title and address of the tab you were viewing ride along, so "summarise this page" means the page you were looking at.
Screenshots. During a run the agent may take a screenshot of the tab it is working in. The image is shown to you in the panel and sent to the AI model that runs the agent; only the latest two stay in the live conversation. Screenshot images are never written to storage, so a saved chat contains no screenshot pixels. Older extension versions instead send each screenshot with a question to a separate vision model and keep only its written answer.
Voice input. If you dictate a prompt, microphone audio streams from your browser straight to Deepgram, our transcription provider, and the words come back to the composer for you to review before sending. The audio never passes through our servers and is never stored; only the text you send becomes part of the chat.
Usage and billing records. We meter what each run costs (token counts and cost per turn) in an append-only ledger to enforce your monthly allowance, and store your subscription state (plan, status, billing period) as our payment provider reports it.
Payment information. Payments are handled by Polar, our merchant of record. Card details go to Polar and its payment processors, never to us. We give Polar your account id and email so it can link the subscription to your account.
Preferences. Settings you choose in the product, such as whether sounds are on.
Technical logs. Server logs and error reports (timestamps, request metadata, the extension version, error messages) used to keep the service running. They contain no chat content or screenshots, and error reports are deleted after 30 days.
2. What we do not collect
- Your browsing history. The extension has no content scripts and no access to sites in the background. It touches a tab only during a run you started, in the tabs the agent opens or you point it at.
- Your open tabs, by default. A list of your tabs is sent only when the agent asks for it during a run. The only tab that rides with a prompt is the one you sent it from.
- Analytics and tracking. The website counts visits with Vercel Web Analytics, which uses no cookies and keeps no personal profile: just the page, the referring site, and your rough country and device type. There are no advertising or tracking scripts, and none at all in the extension.
3. How we use your information
- To run the agent: your instruction and the context above are what the AI model needs to decide the next click, keystroke, or answer.
- To keep chats so you can reopen and continue them.
- To meter usage against your monthly allowance and bill subscriptions.
- To provide support when you contact us.
- To secure the service: detecting abuse, debugging failures.
- To improve riru using aggregate, non-identifying usage patterns.
We do not use your content to train AI models. We do not sell your personal data, and we do not show ads.
Where the law asks us to name a legal basis: we process account, chat, and billing data to perform our contract with you; microphone audio on your consent, given when you switch dictation on and withdrawn by switching it off; and logs and abuse detection for our legitimate interest in running a secure, working service.
4. Who processes your data
riru is built on a small set of providers, each seeing only what its job requires:
- Clerk (authentication) and Google (sign-in): your sign-in session and the profile Google shares. Google's own privacy policy governs the sign-in step.
- Vercel (hosting and analytics): serves this website and the service the extension talks to, so every request passes through its servers, and counts website visits as described above.
- Supabase (database and file storage): chats, attached files in a private bucket, account and billing records.
- OpenRouter (AI model routing): each turn of a run, the conversation (your messages, page content the agent has read, page and tab titles and addresses, attached files, and the latest two screenshots), along with your name, time zone, language, and operating system, goes through OpenRouter to the model that decides the agent's next action, and again when the agent writes its notes on a long chat. Each chat's first message also goes to a small model that writes its title. OpenRouter forwards each request to a provider that hosts the model, and we instruct it to use only providers that neither store your content nor train on it.
- Exa (web search): when the agent searches the web, only the search query is sent to Exa.
- Deepgram (speech to text): microphone audio while you dictate, streamed from your browser under a short-lived token, with Deepgram's model-improvement programme opted out.
- Polar (payments, merchant of record): checkout, card processing, invoices, and tax.
These providers process data to provide their service to us and are bound by their own privacy commitments. We may also disclose information if the law requires it, or to protect the rights and safety of riru or its users.
5. Where your data lives
riru and the providers above may store and process your data outside your country, including in the United States. We choose providers that commit to protecting it, and by using riru you agree to this transfer.
6. Cookies
The website uses only the cookies our sign-in provider needs to keep you signed in, set on riru.app and clerk.riru.app. The extension reads that sign-in cookie, and nothing else, through its cookies permission. There are no analytics, advertising, or tracking cookies.
7. The Chrome extension's permissions
The extension asks for the minimum Chrome permissions the agent needs, and nothing runs invisibly: the tabs riru works in sit in a labelled tab group and carry a visible glow, and Chrome shows its own banner while the agent drives a tab. A run keeps going after you close the panel; Stop ends it.
- debugger: how the agent clicks, types, and takes screenshots in the tab it is working in.
- tabs and tabGroups: listing tabs when the agent asks for them, and grouping the tabs riru works in under a visible label.
- sidePanel and storage: hosting the chat panel and keeping local extension state.
- cookies: reading your riru sign-in session, scoped to our own domain only.
- notifications: optional, off until you turn it on in riru's settings. It lets riru tell you when it needs a confirmation or has finished while you are on another tab. The notification shows the chat's title and the line riru would have shown in the panel; nothing is sent anywhere.
- microphone: not an extension permission. Chrome asks you directly the first time you dictate, and you can revoke it in Chrome's site settings.
8. Data retention and deletion
- Chats and attached files are kept while your account exists. To have specific chats removed, email us.
- Screenshots are never retained, and voice audio never reaches us.
- Error reports are deleted after 30 days.
- Billing records are retained as required for accounting, tax, audit, and dispute resolution, and survive chat and account deletion.
- To delete your account, email hello@riru.app from the address you signed up with. We deactivate the account immediately, and within 30 days delete your profile, chats, and attached files from our systems and ask our providers to do the same, except records we must keep by law.
9. Your rights
You can ask what personal data we hold about you, have it corrected or deleted, withdraw consent you have given, or object to how we use it, by emailing hello@riru.app. We aim to respond within 30 days.
India. We honour the rights of Data Principals under the Digital Personal Data Protection Act, 2023, including access, correction, erasure, withdrawal of consent, grievance redressal, and nominating someone to exercise these rights on your behalf. That address is our grievance contact. If we do not resolve your grievance, you may complain to the Data Protection Board of India.
EEA and UK. If the GDPR or UK GDPR applies to you, you also have the rights to data portability and to restrict processing, and you may lodge a complaint with your local data protection authority.
10. Security
Data moves over encrypted connections. Attached files live in a private storage bucket with ownership checked on every read, and all chat access is authenticated and scoped to your account on the server. No system is perfectly secure; we design so that what is on your screen is held for the shortest time possible.
11. Children
riru is not directed at children and requires you to be at least 18 years old. We do not knowingly collect data from anyone under 18.
12. Changes to this policy
When we change this policy we will update the date at the top, and for material changes we will tell you in the product or by email. Continued use after a change means you accept the updated policy.
13. Contact
For any questions or requests about your data, write to hello@riru.app.