Your data, explained

Privacy policy

Who this policy covers

This policy describes the current Mailpico macOS development preview and this product website. Updated 25 October 2026.

Your data at a glance

Mailpico uses connected account data to run your email and calendar features. Mail is fetched from your provider to your Mac. AI assistance runs on your Mac. Sending a message sends its contents to your email provider and intended recipients.

What we use each type of data for

Data used by the current Mailpico app
DataWhat Mailpico does with itWhere it goes
Account address and sign-in tokensIdentify your connected account and keep it signed in. Tokens authorize connections to your provider.Account details are used on your Mac. Saved credentials are kept in macOS Keychain and used with the relevant provider.
Messages, senders, recipients, and labelsDisplay and search conversations, synchronize your inbox, and carry out mailbox actions you choose.Between your provider and your Mac. Cached account snapshots are encrypted locally.
Drafts, attachments, and scheduled messagesLet you compose, reopen drafts, view attachments, and prepare a reviewed message for delivery.Drafts autosave locally. “Save to Gmail” syncs a draft to Google. Sending transfers message contents and included attachments through your provider to recipients. Scheduling state remains local.
Calendar eventsDisplay your primary Google Calendar and register local reminders. Mailpico does not create or edit events.From Google to the app, with reminder information passed to macOS notifications.
AI prompts and selected mail contextGenerate summaries, answers, action items, reply suggestions, and rewrites when you request them.To the bundled local AI process on your Mac. No cloud AI fallback or mailbox-wide AI indexing is included. Suggestions you keep in a draft are stored with that draft.
Network request metadataRetrieve mail, remote email images, sender logos, selected AI model downloads, and website pages.The relevant mail provider, image or sender-logo host, Hugging Face, or website host may receive your IP address and ordinary connection metadata.
Information you send for supportUnderstand and resolve the issue you report.Only to the support channel you choose to contact. Do not send passwords, tokens, private mail, or unredacted screenshots.

Data Mailpico accesses

With your authorization, Mailpico accesses your email address and account information, message headers and bodies, recipients, labels, drafts, attachments, and mailbox synchronization information. It also accesses events from your primary Google Calendar, including event details needed to display them and set local reminders. Other connected mail accounts use their configured IMAP/SMTP provider.

How connected accounts work

When you connect an account, Mailpico uses your email data to display conversations, compose and send messages, manage drafts, and organize your mailbox. It uses your primary Google Calendar events to display your schedule and provide local reminders. Mailpico does not create or edit calendar events. Google sign-in takes place with Google; Mailpico does not receive your Google password.

How data is used

Account data is used to provide the email and calendar features you choose. Selected conversations, prompts, and drafts are processed by local AI only when you ask for assistance. AI does not authorize sending: sending requires a separate review, and scheduling requires date/time confirmation. Mailpico does not sell your personal data, use it for advertising or cross-service profiling, or use your mail, calendar data, prompts, or generated responses to train or improve AI models. Running an existing model locally to answer your request does not train that model.

AI Box catch-up

When you choose Catch me up or Refresh, AI Box retrieves unread Primary conversations in its catch-up period, including Updates where they are part of your Primary inbox. The period starts at the beginning of the day you last opened an incoming email in Mailpico; if no reading checkpoint exists, it uses the previous 24 hours. It may use downloaded mail when synchronization is unavailable. Message subjects and excerpts are processed by the local AI model to create a briefing. The report and source references remain in app memory; generating a report does not itself mark messages as read. Reports can be incomplete or inaccurate, so check the original messages before acting.

Where data is stored and protected

Persistent account snapshots, including mail, drafts, cached attachments, and scheduling state, are encrypted with AES-256-GCM on your Mac. Credentials and a separate encryption key are stored in macOS Keychain. Encryption does not protect decrypted content while the app is using it, attachments you export, temporary transport files, or unencrypted backups made by earlier app versions. Temporary IMAP/SMTP message files are placed in a private directory and removed after the operation. Deletion cannot guarantee physical erasure from device snapshots or backups. Network connections to mail providers use TLS. There is no Mailpico-operated mailbox or cloud AI server in this implementation.

Some metadata is outside the encrypted mailbox snapshot: connected account addresses and app preferences are stored in macOS preferences. AI Box stores a last-read timestamp under an account-derived hashed key. If notifications are enabled and authorized, sender names and message subjects, or calendar titles and reminder details, are passed to macOS Notification Center and may appear on the lock screen according to your system settings.

AI models and third parties

Built-in AI runs in a bundled local process on your Mac. Downloading a selected model contacts Hugging Face and shares ordinary request metadata such as IP address, but does not send email content. Google receives requests needed to operate Gmail and Calendar. Other providers receive requests for accounts you connect. Remote email images are off by default for new installations. If you enable them in Settings or for a message, HTTPS image hosts receive requests that may reveal your IP address or that a message was opened. Existing installations keep their previously chosen image setting. Spam images start blocked; insecure HTTP images are blocked. Sender logos are off by default and have a separate setting. If enabled, the message list retrieves logos from sender-derived HTTPS website domains before you open a message. Those hosts receive ordinary connection metadata. Logo downloads use a nonpersistent network session and decoded logos are held in app memory. Disabling the setting stops new logo requests from list views; it cannot undo earlier requests. Mailpico does not include app analytics or telemetry. The website includes no analytics scripts, advertising cookies, forms, or account system; the hosting provider may process request and security logs under its own policies.

Sharing and human access

The current app does not automatically transmit mailbox contents to Mailpico’s developer or provide the developer with remote access to your mailbox. Information goes to your connected providers as needed to deliver the features you request, and to recipients when you send email. If you voluntarily send support information, include only what is necessary and redact sensitive content. Such information is used to address your request; it is not used for advertising or AI training.

Retention, deletion, and revocation

Mailpico does not automatically delete its entire local account cache after a fixed number of days. Local account data remains until you disconnect the account or remove its stored data from your Mac. Uninstalling the app alone may leave application data or Keychain items behind. Disconnecting in Settings removes the account’s local cache, drafts, and saved account credentials after confirmation; it does not delete server mail. Model downloads remain until removed in Settings. Removing a model does not delete mail or drafts. Exported files and backups require separate deletion. Disconnecting also removes the account-specific AI Box reading timestamp and requests removal of its pending and delivered mail notifications from macOS. General app preferences, imported OAuth client configuration, the shared cache encryption key, downloaded models, and any license receipt remain because they may serve other accounts. Earlier network caches, exported files and backups require separate cleanup when fully removing Mailpico. You can revoke Google access at Google Account connections; revocation stops future authorized requests but does not itself erase local files. Mailpico has no central mailbox copy to delete. Deleting local data does not erase messages held by your email provider or recipients. Manage those copies through the relevant provider; recipients control their own copies. Revoking authorization and deleting local data are separate actions. Removing local drafts can make them unrecoverable; keep any drafts you need before disconnecting. Support correspondence, if supplied, is retained only as needed to resolve the request and satisfy applicable obligations; a specific retention period depends on the nature of the request and applicable legal obligations.

Google Limited Use

Mailpico’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace data is used only to deliver the disclosed, user-facing features. It is not transferred for advertising, sold, used for credit decisions, or used to create, train, or improve generalized AI models. Human access and any exceptional transfer must comply with the applicable Limited Use restrictions.

Your choices and rights

You may disconnect accounts, revoke authorization, remove local models, disable remote images, or stop using Mailpico. Depending on where you live, you may have rights to access, correct, delete, or restrict processing of personal information. For account data stored on your device, you can manage these choices directly in Mailpico Settings and your connected provider’s account settings.

Preview, licensing, and policy changes

No purchase or license-activation service is offered by this website. If paid activation becomes available, its data practices will be described before you activate a license. Material changes to data practices will be described in an updated policy and, where required, presented for consent. Mailpico is not intended for children under 13 or anyone below the applicable age of digital consent.