Privacy Policy

Eggomi ("we", "us") brings your connected services, conversations and personal tools into one place. This policy covers the Eggomi service, including its web app and supported companion clients. It explains what stays on your device, what our services process, and what you choose to share with other providers. Contact us at hello@eggomi.com.

Eggomi is moving to local-first storage. The current production version still stores readable connected-service data and activity on our servers, including mail summaries, calendar details, follows, watch history, and AI questions and replies.

The encrypted device-vault and cloud-recovery sections below describe the new local-first version and apply when you use that version. Updating the app does not itself erase older server copies. The retention and deletion choices below also apply to those copies.

Private features use an encrypted vault on your device. Depending on the features you enable, this includes:

• Mail and calendar content, contacts, connected Work content, drafts and saved items.
• Platform follows, feed preferences, searches, activity, watch progress and listening history.
• Tasks, trackers, personal notes and memories, personalization, saved Ask answers and AI conversation history.
• Listen scripts and downloaded or generated audio kept in the private vault.

The app decrypts data while your vault is unlocked so you can read, search and use it. Encryption protects stored copies; it does not hide content from someone who can use your unlocked device. Some account settings, public or shared content, and service metadata are handled separately as described below.

Cloud sync stores encrypted changes and recovery snapshots so your other authorized devices can catch up. Eligible app data and recent provider content can be included. Media backed up through the private vault is encrypted on your device before upload to our storage. Provider credentials are handled separately from content recovery; restoring content does not automatically reconnect every account.

Our sync services receive encrypted data and the metadata needed to deliver it, such as your account and device identifiers, encrypted object identifiers, sizes, versions and timing. The vault content key is protected by your configured unlock and recovery methods rather than stored as a plaintext sync key on the server. This does not make network activity anonymous.

Keep an available unlock or recovery method and any exports you need. Clearing browser storage, losing every usable key or losing an unsynced device can make data unavailable. Encrypted backup cannot recover a lost decryption key by itself.

We process account information such as your sign-in identity, email address, profile and authentication records; service settings and entitlements; and operational data needed for security, reliability, rate limits and support. Requests can expose IP addresses, browser or device information, request times and diagnostic information to our infrastructure and hosting providers.

Content you deliberately publish or share, including public profiles and shared spaces, is available to its intended audience. Public feed items and channel information may be stored on our servers. Your private follows and personal history belong in your device vault, but a request for public content can still reveal which resource you requested.

We use hosting, network and storage services to run Eggomi. They process the information necessary to provide those services. We may also disclose information when required by law, to address abuse or security incidents, or to protect users' rights. These disclosures do not give us an ability to decrypt vault content we cannot otherwise access.

You choose which accounts to connect and authorize the permissions needed for each feature. Where supported, your browser contacts the provider directly. Some services require an Eggomi broker to exchange authorization codes or forward requests. That broker processes the relevant tokens, request content and responses during the request; local storage does not mean those requests are invisible to our server. Sign-in credentials and optional hosted connection flows can follow different storage rules from browser-only provider access.

In the local-first provider flows, private content is kept in the encrypted device vault. Tokens may be held in memory or encrypted device storage, depending on the provider. Operational request metadata can still be processed. Browser RSS fetching may use our proxy, which can see the requested feed address and return its content.

If you enable Google token continuity, Eggomi stores an encrypted refresh token on its server and can decrypt it to renew access for your browser. That option gives our server access to the granted scopes; it does not by itself move your mail or calendar content to server storage. You can turn off continuity separately from deleting local content.

Messaging has its own encryption boundaries. Matrix and connected networks process account, room and delivery information. End-to-end encryption applies where the conversation and connection support it; public rooms, recipients, bridges and the original network have their own access and retention rules. Sending a message necessarily shares it with its recipients. The private vault is not a promise that every connected network is end-to-end encrypted.

Google sign-in identifies your account. Connecting Gmail separately lets you read and organize mail and, when authorized, manage drafts or send messages. Calendar access lets you view events and, when authorized, create, change or delete them. YouTube access supports subscriptions, playlists, liked videos and search, with account changes only when authorized. Enabling an API in our developer project does not itself grant access to your account.

We use Google account data to provide the features you select. Eggomi's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data or use it for advertising or credit decisions. Human access is limited to your specific permission or the security, legal and other narrow exceptions allowed by that policy.

When you use an AI feature on Google data, such as summarizing a message or drafting a reply, the relevant content is sent to the AI model service handling that request, such as OpenAI, Anthropic, Google Gemini, Cloudflare Workers AI, Venice or NEAR AI, directly or through Cloudflare. We send it only to provide the feature you asked for. We do not use Google user data to develop, improve or train generalized AI or machine-learning models, and we send it only to AI services whose terms do not allow them to train on it.

In the local-first version, your Gmail messages and Google Calendar events are kept in your encrypted device vault, not on our servers. Our servers keep account metadata for each Google connection: the connected email address, the granted scopes and sync status, plus an encrypted refresh token if you turn on Google token continuity. Content passes through our servers only while a request you make is being handled, such as an AI request about a message, except for the suggestion cards described below.

Until the local-first version reaches your account, the current production version keeps the Gmail inbox list on our servers (each message's ID, thread, sender, subject, snippet, received time and read and inbox state) and Google Calendar events (title, time, location, meeting link, status, your response, the organizer's email and the number of attendees). Message bodies are fetched from Google when you open them and are not stored. Shipment tracking keeps the order and delivery details it finds in your mail (merchant, items, order and tracking numbers, carrier and status) and sends the carrier and tracking number to a parcel-tracking provider (Ship24 or EasyPost) to follow the parcel. Your Yolk digest is stored as generated text and can mention senders, subjects and events. Suggestion cards omi makes from your mail and calendar (a reply to send, a deadline, prep for a meeting) are stored on our servers so they reach each of your devices, along with what omi learns from how you respond to them (for example, that you usually reply to someone within a day). Answers to tracker questions that drew on your mail or calendar are not kept in your question history. Google tokens are stored encrypted. Disconnecting Gmail or Calendar deletes from our servers its synced mail list or events, every Yolk digest and suggestion card built from that source, your voiced Yolk recordings, and what omi learned from those cards; shipment details are deleted when you disconnect your last Gmail account.

You can revoke Google access through your Google Account connections or the Google security settings page. Revoking access stops future authorized requests; it does not automatically delete copies already stored on your devices or in backups. YouTube features use YouTube API Services and are also subject to the Google Privacy Policy.

Local models process their model input on your device. Hosted models, speech services and external model endpoints receive the prompts, selected context or audio needed for the feature you use. For example, asking for a mail summary can send the relevant message content to the selected model service. Hosted requests may pass through Eggomi's servers even when their saved history is encrypted on your device.

Private AI request paths are designed to process their content without saving a plaintext prompt-and-response history on Eggomi's server. Operational usage and error metadata can remain. The selected external provider has its own processing and retention terms; encrypted storage is not a guarantee of zero retention by that provider. Review your model choice before including sensitive information.

AI-proposed account changes use the approval controls shown in the app. Check the recipient, content and intended action before approving a send, publication, deletion or other external change.

Eggomi uses cookies and browser storage for sign-in, security, preferences, offline operation and encrypted local data. We do not sell private account data or use it for targeted advertising. Blocking storage can prevent sign-in, persistence or recovery.

Embedded media, provider sign-in screens, externally hosted fonts and links can make requests to other services. Those services may receive your IP address and browser information and apply their own cookies and policies. A local copy of your watch history does not prevent the original video service from observing playback.

You can disconnect providers, change history preferences, delete saved items and conversations, and use the available vault sync, recovery and export controls. Turning off history recording does not by itself erase existing history or separately saved AI conversations. Disconnecting an account does not delete the original data at that provider.

Deletion and encrypted sync are distinct from clearing this browser's storage. Synced deletions reach other devices when they reconnect. Recovery snapshots, offline devices and exports you saved may retain earlier copies until those copies are removed or expire. Request account or server-data deletion by contacting us; we may need to verify the request. We cannot remotely erase independent exports or copies held by message recipients and other providers.

We retain account and operational records while needed to provide the service, secure it, resolve disputes or meet legal obligations. Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, or receive a copy of your data. Contact us to exercise those rights; you may also contact your local data protection authority. Processing by our service providers may take place outside your country.

Eggomi is not intended for children under 13 or below the minimum age required to use the service in their country. If you believe a child has supplied personal information, contact us.

We will update the date on this page when this policy changes and provide notice of material changes. If a new use of connected data requires permission, we will request it before that use. For privacy questions or requests, email hello@eggomi.com.