Your account

Soloe uses your name, email address, account identifier and sign-in credentials to authenticate you, maintain your account and protect access to your projects. Session cookies keep you signed in. Passkey public keys are stored for authentication; Soloe does not receive your device's biometric data.

Google sign-in

If you choose Google sign-in, Soloe requests your basic profile and email address: your Google account identifier, name, profile image and verified email information. Soloe uses these to create or authenticate your account and display your identity. Google authorization tokens are stored encrypted by the authentication service.

Soloe does not request access to your Gmail messages, Google Drive files, calendar or contacts. Google sign-in data is not used for advertising, sold, or supplied to AI providers for model training. You can remove Soloe's access from your Google account connections.

Projects, notes and chats

The native application stores your local work on your device. Connecting an account enables cloud synchronization of eligible projects, their history and attachments, and your private notes and chat transcripts. Cloud synchronization makes this information available to your authenticated devices and the web dashboard.

Sharing grants the access you choose. Project viewers and commenters can access shared project content and comments. Private Inbox notes and Chats are account information. Publishing a page makes its publication accessible to anyone with its public link. Remove public sharing through the page's Share settings.

When you run a chat, your selected native application sends the prompt and relevant context to the AI provider you selected. That provider handles the information under its own terms and privacy policy. Provider credentials remain on the native device.

Service providers and security

Cloudflare hosts the web application and processes the account and cloud content required to operate Soloe. Google processes Google sign-in. Authentication and project access controls restrict private content; network connections use HTTPS. Cloudflare may process request metadata, including IP addresses, to deliver and secure the service.

Authentication messages use the configured email service. Those messages contain the information needed to sign in or recover access. Linking an MCP connector grants the account and project access shown in its authorization screen; you can revoke a connector from your account.

Retention and your choices

Account and synchronized content are retained while needed to operate your account. Project versions, conflict records and deletion markers can remain in synchronization history so offline devices reconcile correctly. Revoking a device or share removes its future access; it does not erase copies someone has already downloaded.

You can export your work, revoke devices and connectors, and change sharing settings. For account deletion, data access or other privacy requests, contact riconror@gmail.com. Include the email address associated with your account so the request can be verified.

Changes and contact

Updates to this policy will appear here with a new effective date. Privacy questions can be sent to riconror@gmail.com.