Privacy Policy
How Robin processes and stores information across your local Windows computer, AI models, and connected services.
1. About Robin
Robin is a desktop personal assistant application for Windows designed to help you organize daily information—including email, calendar events, tasks, contacts, files, and notes—through a unified conversational interface.
Robin operates with a local-first design: the application runtime, configuration, local database, and session records run on your physical Windows PC rather than on remote centralized servers operated by Robin. When you choose to connect third-party services or cloud AI models, information flows directly between your computer and those authorized providers according to your settings.
2. Information Robin Processes
Depending on which features you enable and use, Robin processes:
- User Requests: Text messages, spoken instructions, and commands you submit in conversation.
- Connected Account Data: Email headers, message content, calendar events, task items, and contact information retrieved via services you authorize (such as Google Workspace).
- Workspace Files: Content and metadata of documents located strictly within your configured local Robin workspace directory.
- Local Memory & Preferences: Saved context, project names, confirmed contact identities, and assistant preferences stored on your device.
- Microphone Audio: Live audio captured in memory by your microphone during voice interaction and wake-word listening.
3. Local Processing and Storage
Robin stores application data on your local hard drive in your Windows user profile under ~/.robin. This local storage consists of:
- Application Database (
robin.db): A local SQLite database storing confirmed contacts, action history, and configuration preferences. - Session Database (
adk-sessions.db): A local SQLite database storing conversation logs and turn history on your machine. - Embedded Vector Store (
qdrant/): A local embedded vector index used for contextual memory search on your device.
4. AI Model Providers
Robin allows you to choose how assistant reasoning is handled:
A. Local AI via Ollama
When configured to use local AI through Ollama (connecting to http://localhost:11434), model reasoning executes on your computer's hardware. Prompts and request context are not sent to cloud AI providers.
B. Cloud AI (Google Gemini)
When configured to use a cloud model such as Google Gemini, relevant user instructions, conversation context, and tool inputs are transmitted directly from your desktop to Google's Gemini API using your configured API key. That data is handled under Google's applicable terms and policies.
5. Google User Data
Robin offers optional integrations with Google Workspace. Robin accesses Google user data only after you explicitly initiate connection and authorize permissions through Google's standard OAuth sign-in flow.
A. Scopes & Access
Robin requests permissions limited to the assistant features you choose to use:
- Gmail: Used to inspect message headers and recent emails when you ask about your inbox, retrieve specific email context you request, and prepare email drafts.
- Calendar: Used to check your schedule, identify conflicts, and draft calendar events based on your instructions.
- Tasks: Used to view and manage your Google Tasks lists.
- Contacts: Used to read saved contact names and email addresses so Robin can resolve who you mean when asking to contact a person.
B. How Google Data Is Handled
- Robin uses authorized Google data solely to deliver the specific assistant functionality you request.
- Robin does not use Google user data to display, target, or serve advertisements.
- Robin does not sell, rent, or transfer Google user data to data brokers, advertising networks, or commercial third parties.
- Robin does not use Google user data to train or fine-tune generalized machine learning or artificial intelligence models.
- Mutating actions—such as sending an email or changing a calendar event—require your explicit approval in Robin before anything is changed.
C. Disconnecting Access
You can disconnect Google at any time in Robin Settings. Disconnecting removes your stored credentials from your local Windows Credential Manager. You can also revoke access at any time through your Google Account permissions page.
6. Files and Workspace Access
Robin can read and summarize local documents you place in its designated workspace directory (defaulting to C:\RobinWorkspace or your customized folder).
Robin's file tools are scoped to this directory. Robin does not perform background scans of your entire hard drive, personal folders, or system files.
7. Voice Features
Robin includes voice capabilities using on-device speech processing:
- Wake Word & Speech-to-Text: Microphone audio is processed locally on your computer's CPU using on-device speech models (Sherpa-ONNX for wake-word detection and Moonshine for speech transcription).
- Audio Buffers: Audio frames are processed in-memory during active voice interaction. Robin does not write permanent audio recording files to disk and does not stream raw audio to external audio servers.
- Cloud AI Distinction: When you speak to Robin while using a cloud AI model (such as Gemini), your spoken audio is converted to text locally on your PC, and the resulting request text is sent to the cloud model to generate the response.
8. Memory and Personal Context
To maintain conversational continuity, Robin can remember relevant details you share (such as preferred meeting times, ongoing project names, or confirmed contact identities).
- Memory records and semantic embeddings are stored locally on your device in
robin.dband the local vector index. - Robin does not claim to remember everything; it retains specific context relevant to your daily tasks.
- Memory is not hidden surveillance—it is stored in your local application data folder.
9. Credentials and Connected Accounts
Robin does not store your Google or third-party account passwords. When you connect an account via OAuth, access and refresh tokens are stored locally in the standard Windows Credential Manager under the service name Robin using the operating system's built-in credential locker.
When you provide a Gemini API key in Robin Settings, Robin stores the key using Windows Credential Manager rather than in Robin's plaintext configuration files. Non-sensitive AI configuration, including the selected provider and model, is stored locally in ~/.robin/ai-settings.json.
Tokens and credentials are not stored in reviewable action plans, unencrypted application logs, or transmitted to Robin servers.
10. Human-in-the-Loop & Action Approvals
Robin distinguishes between reading information and modifying external state. Actions that change something—such as sending an email, creating or editing a calendar event, or updating a task—are prepared in a pending state and require your explicit review and approval before execution.
Pending actions that are not approved automatically expire after 24 hours in the local database.
11. Telemetry and Analytics
Robin does not currently include third-party product analytics or advertising tracking SDKs in the desktop application or on this website (robinpa.in).
Robin does not monitor your general background computer activity, browser history, or keystrokes outside the assistant interface.
12. Data Sharing and Selling
Robin does not currently sell personal information to advertisers.
Information is shared only with third-party services that you explicitly configure or authorize (such as your chosen cloud AI provider or connected Google Workspace account) to carry out assistant requests.
13. Data Retention and Removal
Because Robin stores its application data locally on your computer, you can manage and remove your data directly:
- Robin Application Data: Deleting the local directory
~/.robinremoves Robin-managed files, including your local SQLite databases (robin.dbandadk-sessions.db), the local Qdrant vector index, local AI settings, and Robin-cached voice models (such as Moonshine and wake-word models). - Credentials and API Keys: Stored credentials—including Google OAuth tokens and your Gemini API key—are managed in the Windows Credential Manager. Disconnecting your account or clearing keys in Robin Settings removes those credentials from Windows Credential Manager.
- Ollama Models: If you use Ollama for local AI, models you download are managed and stored independently by Ollama on your system. Deleting the
~/.robindirectory does not delete your Ollama installation or downloaded Ollama models; these can be managed or deleted directly through Ollama.
14. Security
Robin uses standard security practices suitable for Windows desktop software:
- Storing account tokens in the Windows Credential Manager rather than plaintext files.
- Using standard OAuth 2.0 PKCE authentication flows.
- Restricting file operations to designated workspace paths.
- Requiring human approval before consequential actions execute.
No software system is entirely immune to security risks. You are responsible for maintaining the physical and operating-system security of your Windows PC.
15. Children's Privacy
Robin is intended for general productivity use by adults. It is not directed to children under 13, and we do not knowingly collect personal information from children.
16. Changes to This Policy & Contact
We may update this Privacy Policy as Robin develops. Any updates will be posted to this page with an updated revision date.
Contact
Official public contact mailboxes will be provided on this website prior to public distribution.