riru is an AI agent that lives in your browser: a Chrome side panel where you describe a job and the agent clicks, types, and reads pages to get it done. Because riru works inside your browsing, we hold ourselves to a simple rule: collect only what the service needs to do the job you asked for, keep as little of it as possible, and never sell any of it.
This policy covers the riru website (riru.app), the riru web app, and the riru Chrome extension, operated from India ("riru", "we", "us"). Questions or requests: hello@riru.app.
1. Information we collect
Account information. We use Clerk for sign-in. When you create an account we receive and store your email address, name, and profile image, keyed to your account id.
Chats. Your prompts, the agent's replies, and files you attach are stored so you can reopen a chat and continue it. Pages the agent reads or acts on during a run become part of that chat's transcript: page excerpts, and the titles and addresses of pages it worked on. Long page snapshots are compacted to summaries when a chat is saved.
The tab you were on. When you send a prompt, the title and address of the tab you were viewing ride along as context, 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. Screenshots are shown to you live in the panel and seen by the AI model during that run, and that is all: they are never written to storage. When a chat is saved, the image is stripped and only the fact that a screenshot was taken remains. A reopened chat contains no screenshot pixels, by design.
Usage and billing records. We meter what each run costs (token counts and cost per turn) to enforce your monthly allowance, and we keep an append-only billing ledger of those costs. Your subscription status reaches us from our payment provider's webhooks.
Payment information. Payments are handled by Polar, our merchant of record. Your card details go to Polar and its payment processors, never to us. We store only your subscription state (plan, status, billing period).
Technical logs. Standard server logs (timestamps, request metadata, errors) that we use to keep the service running and debug problems.
2. What we deliberately do not collect
- Your browsing history. The extension has no content scripts and no access to sites in the background. riru touches a tab only during a run you started, in the one tab the agent has explicitly bound as its working tab.
- Your open tabs, by default. A list of your tabs is sent to our servers only when the agent explicitly asks for it during a run, never pushed automatically. The only tab context that rides with a prompt is the tab you were on when you sent it.
- Screenshots at rest. As above: screenshot images are never stored.
- Card details. Polar handles checkout end to end.
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 persist chats so you can reopen and continue them.
- To meter usage against your plan's monthly allowance and to 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.
4. Who processes your data
riru is built on a small set of service providers, each seeing only what its job requires:
- Clerk (authentication): your sign-in credentials and profile.
- 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, the latest screenshot, attached files) is sent through OpenRouter to the AI model that generates the agent's next action.
- Exa (web search): when the agent searches the web, only the search query text is sent to Exa.
- Polar (payments, merchant of record): checkout, card processing, invoices, and tax handling.
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.
5. The Chrome extension's permissions
The extension asks for the minimum set of Chrome permissions that make the agent work, and nothing runs invisibly: the open side panel is the signal that riru is working, closing it stops the run, and the tab the agent is working in carries a visible glow while it does.
- debugger: how the agent clicks, types, and takes screenshots in the working tab. Chrome shows its own banner whenever this is active.
- 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.
6. Data retention
- Chats and attached files are kept until you delete them or your account.
- Screenshots are never retained.
- Billing records are retained as required for accounting, audit, and dispute resolution, and survive chat deletion.
- When you delete your account, your profile is deactivated immediately and your personal data is removed, except records we must keep by law.
7. Your rights
You can access, correct, or delete your personal data, withdraw consent, or ask what we hold about you by emailing hello@riru.app. We honour the rights granted by India's Digital Personal Data Protection Act, 2023, and equivalent rights under other laws that apply to you, such as the GDPR. That address also serves as our grievance contact; we aim to respond within 30 days.
8. Security
Data moves over encrypted connections. Attached files live in a private storage bucket with ownership checked on every read. All chat access is authenticated and scoped to your account on the server. No system is perfectly secure, but we design so that the sensitive thing (what is on your screen) is held for the shortest time possible.
9. 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.
10. 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.
11. Contact
hello@riru.app. riru is operated from India.