What we collect
- Website signups: the waitlist form collects your email address and sends it through Resend so we can confirm your signup and manage beta invites.
- App and account data: beta sign-in details, app version, device name, and similar operational metadata.
- Assistant content: messages, reminders, memories, jobs, attachments, voice notes, and other material you choose to give Rosi.
- Connected service data: account identifiers, granted scopes, and task-related data for services you choose to link or use.
How we use it
- To run the beta, authenticate access, and keep your install associated with you.
- To carry out the tasks you ask for, including messaging, reminders, research, connector actions, and hosted phone-ready pages.
- To monitor reliability, diagnose bugs, secure the product, and understand beta usage at an operational level.
Where it goes
- On your Mac: core runtime state such as messages, jobs, memories, and attachments is stored locally.
- Rosi backend: sign-in, device heartbeat, connector auth flows, hosted-app publishing, managed search access, and operational telemetry.
- Third parties you invoke: Telegram for messaging, OpenRouter and model providers for AI processing and transcription, Resend for beta emails, and any connector or provider you choose to use.
Beta limits
- If you ask Rosi to publish a phone-ready page, that content is uploaded to Rosi hosting and accessible through the generated link.
- Operational telemetry is intended to be limited and filtered. It is not meant to be a raw copy of your messages.
- Because this is a beta, data handling and retention may change, and we may reset parts of the service while we iterate.
Practical advice: do not use the beta for highly sensitive, regulated, or irreplaceable information yet.