Privacy Policy
Effective October 1, 2026
Silica Mail ("Silica") is an invite-only email application. This policy explains how Silica handles information when you use the app, connect a mailbox, or visit silica.app.
Information we access
- Account information: your invited email address or username, account identifiers, authentication and session records, preferences, and device notification tokens when you enable notifications.
- Mailbox information: connected email addresses, message and thread identifiers, senders and recipients, subjects, message text and HTML, attachments, labels, read status, drafts, and other information needed to display and manage your mail.
- Information you create: outgoing messages and attachments, saved contacts, sender rules, categories, classification results, and conversation organization.
- Connection and technical information: OAuth credentials needed to maintain Gmail access, connector credentials for imported Proton mail, and operational records used for security and troubleshooting. Hosting and service providers may process network information such as IP addresses.
How we use information
We use this information to authenticate you, connect and synchronize your mailboxes, display and search mail, organize messages, apply your rules, manage drafts and scheduled sends, send messages you request, deliver enabled notifications, and maintain the service.
Gmail access uses Google's authorization flow; Silica does not receive your Google password. The Gmail permissions allow Silica to read and manage email, including creating labels, marking messages read, archiving or moving messages to trash, and sending email. Some actions run automatically according to your configured rules and category settings.
AI processing and service providers
Silica sends a message's sender, subject, and up to 4,000 characters of its readable message text, together with relevant category criteria, to OpenRouter's Jev classification service. This processing determines categories, subtypes, importance, and related message facts. Attachments are excluded from these classification requests. Classification can run in the background for connected mailboxes.
Amazon Web Services hosts Silica's backend, authentication, and data storage. Google provides connected Gmail access. If you enable push notifications, Expo and Apple process notification delivery information. Proton mail imported through your local connector is processed and stored by Silica so it can remain accessible while the connector is offline. Email you send is delivered to its recipients through the selected mail provider.
These services process information under their applicable terms and privacy policies. See OpenRouter's privacy policy, AWS's privacy notice, Google's privacy policy, and Expo's privacy policy.
Google user data and limited use
Silica uses Google user data to provide its email features. Silica does not sell Google user data or use it for advertising, credit decisions, or training its own general-purpose AI models. Transfers of Google user data are limited to providing these features, security, compliance with applicable law, or a business transfer with your prior consent, as permitted by Google's policies.
Silica's use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to your affirmative permission for specific data, necessary security investigations, legal requirements, or other uses expressly permitted by that policy.
Storage, retention, and security
Silica stores account and mailbox records, credentials, organization settings, classification metadata, and imported Proton message content on AWS. Connections use HTTPS, and the configured AWS data stores use encryption at rest. No service can guarantee absolute security.
Disconnecting a mailbox in Silica disables access immediately and queues deletion of its stored message content, attachments, and mailbox metadata. Cleanup starts after a ten-minute wait for running requests and temporary upload links to expire, and retries if interrupted. Shared account settings, contacts, and sender rules remain until deletion is requested. Revoking Google access separately does not automatically delete Silica-held data. Temporary Gmail attachment caches and outgoing uploads also expire after one day, although provider cleanup can take longer. Operational backend logs have seven-day retention. Trashed imported Proton content is scheduled for deletion after 30 days while connected.
Your choices and deletion requests
You can revoke Gmail access through your Google Account connections, ask your Silica operator to disconnect a mailbox, disable notifications, or stop your Proton connector. Revoking Gmail access stops future authorized Gmail access but does not undo mailbox changes already made.
For access, correction, account closure, or deletion of data held by Silica, contact the operator who invited you. We may need to verify your identity before acting. Some records may need to be retained for security or legal obligations. Deleting Silica-held data does not itself delete your original mailbox at Google or Proton.
Changes and contact
We will update this page when the policy changes. Material changes to how Google user data is used will be disclosed, and additional consent obtained where required, before the new use begins. For privacy questions, contact the operator who invited you to Silica.