Legal

Privacy Policy

Effective October 10, 2026

Wingman Mail is local-first. Your mailbox, calendar, and contacts sync directly between your device and Google, and our servers never store message content. We never sell personal data, never use it for advertising, and never use it to train generalized AI models. AI processing requires a separate choice for each mailbox. When enabled, it sends relevant thread content or bounded batches through our AI proxy, in memory, and discards them after processing. Connecting an external AI app through MCP is a separate permission.

1. Who controls your data

Grand Ventures SIA (Riga, Latvia) operates Wingman Mail and is the controller of the personal data described in this policy. Questions and privacy requests can be sent to [email protected].

2. Google user data

Wingman Mail asks for the Google permissions below only when you connect an account, and uses each only for the feature described.

Gmail

gmail.modify lets the app read, search, compose, send, label, and archive your mail. gmail.settings.basic reads your send-as addresses and signatures and manages the filters created when you block a sender. The grant cannot bypass Gmail's trash to permanently delete messages. Mail, attachments, drafts, and the search index are stored only on your device, in an application-encrypted database whose key is protected by your operating system's credential service.

Contacts

contacts.readonly, contacts.other.readonly, and directory.readonly let the composer suggest recipients the way Gmail does: your saved contacts, people you have emailed, and colleagues in your Google Workspace directory. Names, addresses, and photo links are stored only on your device. If you separately allow contextual voice drafting, up to 12 relevant contact names and email addresses may pass transiently through our AI proxy to help resolve spoken recipients. Your full directory and contact photos are not sent.

Calendar

A separate, independently revocable grant (calendar.events, calendar.calendarlist.readonly, calendar.freebusy) syncs your calendars directly to your device so you can view, create, edit, and respond to events. When you look for a meeting time, your device asks Google when the people you added are busy; it sees only busy and free time, never their events, and none of it reaches our servers. Text you type into an event's location field is sent through our server to Google Places for address suggestions and is not stored or logged.

Identity

OpenID Connect scopes (openid, email, profile) identify your Google account so we can sign you in and confirm which mailboxes belong to you. In the web app, Google returns a short-lived access token through our server to your browser; it is not stored on our servers.

3. How Wingman Mail uses Google user data

AI features

Before AI processing starts for a mailbox, the app explains which content it sends, who receives it, and what derived information it stores, and asks you to enable it. Connecting Gmail alone does not enable AI. You can withdraw this permission for each mailbox in Settings. When enabled, AI drafting, summaries, translation, reminder suggestions, follow-up reminders, automations, and "Tell Wingman" use the relevant content. Drafting and thread actions use the relevant thread; Auto Reminders' follow-up check uses only the message you just sent; automatic summaries use up to eight threads per request, travel extraction up to four likely booking emails, memory learning up to 60 sent messages initially and 25 on later passes, and scheduled reports up to 60 inbox snippets. With your additional permission, contextual voice drafting searches locally for up to 12 matching contacts, four relevant email excerpts, and six calendar events from the selected mailbox (at most 24,000 characters total). To answer faster, drafting may start from what you have said so far when you pause, before you tap Stop; drafts are shown only after Stop. Audio remains on your device. These references help propose recipients and draft text; they do not authorize sending mail or changing events. That content is sent through our AI proxy to OpenRouter and the model provider it routes to. Every request requires no data collection and zero data retention from the provider. Content is processed in memory and discarded after the response; it is never written to our databases, queues, logs, or crash reports.

For Trips, the desktop app first picks likely booking and visa-approval emails on your device (promotions never leave it), then sends those through the same proxy to read flights, stays, rental cars, and visa or travel-authorization details such as the holder, authorization number, and validity dates. Passport numbers are never extracted. The results are stored only in the app's encrypted database on your device.

Memories

Memory learning runs only for mailboxes where you have enabled AI processing, and can also be turned off in Settings. While it is on, the app periodically sends a bounded sample of your sent mail through the AI proxy to extract short facts and writing-style preferences (for example "prefers morning meetings") so drafts sound like you. These memories are the one kind of email-derived data we store: encrypted at rest, scoped to your account, and viewable, editable, and deletable at any time in Settings. Turning off learning stops new extraction; delete existing memories separately if you no longer want them retained.

Optional cloud features

When you explicitly enable cloud automations, auto drafts, or reminders for a mailbox, a separate Google grant (gmail.modify) is held by an isolated grant broker. Its refresh token is envelope-encrypted with a key held in Google Cloud KMS and is never returned to our application server or worker. The worker fetches new mail for that mailbox, processes it in memory, performs only the actions you authorized, and discards the content. AI processing still requires your separate per-mailbox permission. Scheduling links extend that grant with calendar.events and calendar.freebusy so people can book time while your devices are offline; we store the link settings and booking times, not invitee details or event text.

AI apps you connect through MCP

You can connect an external AI app to Wingman through our cloud-only MCP endpoint. You choose which verified, cloud-enabled mailboxes it may read and whether it may create reply drafts. Each app has its own permission grant, which you can revoke on the Connected AI apps page. Cloud access alone does not authorize an external app. The initial tools cannot send mail, download attachments, or read existing drafts.

We fetch requested mail transiently through the grant broker and never persist its content or tool responses. Reply drafts are stored in Gmail. We retain hashed connection credentials, mailbox permissions, operation metadata for up to 30 days, and identifiers needed to prevent duplicate drafts. The external app you select receives the authorized mail content and may retain it under its own privacy policy; our AI provider retention settings do not apply to that app.

A connected app may use this data only for the email features you authorized and must honor the Google API Services User Data Policy, including Limited Use. It must not use or transfer your mail for advertising, resale, or training generalized AI models. Your consent does not waive those restrictions. Review the app's privacy and retention terms before connecting it; disconnecting stops future access but does not itself erase copies already held by that app.

What we store on our servers

  • account data: Google account identifier, email address, name, plan, trial, and team membership;
  • session and security metadata;
  • memories (above), snippets, trip notes you write in Trips (encrypted, and linked to trips by hashed booking identifiers rather than booking references), which flights you marked checked in and which nights you marked as having a place to stay (encrypted; hashed identifiers only), for each email thread your desktop app read for Trips, the thread's identifier, a hashed message identifier, and a fingerprint of what it found, so your phone reads the same emails directly from Gmail and checks it reaches the same result (encrypted; identifiers and one-way fingerprints only, never the email or the booking), tasks you add beside the calendar (encrypted), automation instructions and schedules, reminders, scheduling-link settings and bookings, and synced preferences such as your mailbox list and split names;
  • automation activity: time, outcome, and a short action description such as "archived" or "forwarded to an address you chose", kept up to 30 days; and
  • account-scoped message identifiers needed to retry work and prevent duplicates, never message content.

Other processing

  • Remote images in email are blocked until you allow them; allowed images load through our image proxy so senders do not see your IP address. Image addresses are not logged or stored.
  • Sender pictures and logos also load through the image proxy, so the services below see our server, never you: Gravatar receives a one-way SHA-256 hash of a sender's email address, Google's favicon service receives the domain of a sender's organization, and Google's static image host receives airline codes for logos on flight cards.
  • To show a verified brand logo, your device looks up the domain of a received email's sender in DNS through Cloudflare's DNS-over-HTTPS resolver; on desktop it then fetches the brand certificate that domain publishes. Cloudflare sees your device's IP address and the sender's domain, nothing else from the message.
  • When you ask Wingman to preview where an email link goes, our server follows the link's redirects for you, so tracking services see our server rather than you. The link is not logged or stored.
  • GIF searches you type in the composer are sent through our server to KLIPY with an opaque identifier; they are not logged or stored.
  • Weather on a trip's place card is fetched by our server from MET Norway using the place's coordinates rounded to about a kilometre; MET Norway sees our server, not you, and the coordinates are not logged or stored.
  • For instant sync, Google notifies our server when a mailbox changes (its address and a change number, never content). We relay that notification to your signed-in devices and do not log or store it.
  • Feedback you choose to send, with your name and email, is delivered to our team's Slack workspace.

4. Google API Services User Data Policy

Wingman Mail's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • we use Google user data only to provide and improve the user-facing features described in this policy;
  • we transfer it to others only as needed to provide those features (the service providers in section 6), to comply with law, for security, or as part of a merger or acquisition only after obtaining your explicit prior consent;
  • we never use or transfer it for advertising, and never sell it;
  • we do not use Google user data, including data obtained through Google Workspace APIs, to develop, improve, or train generalized or non-personalized AI or machine-learning models; and
  • no Wingman Mail personnel read your Google user data unless you give explicit consent for specific messages (for example in a support request), it is necessary for security purposes such as investigating abuse, it is required to comply with law, or it has been aggregated and anonymized for internal operations.

5. Why we process data

  • to provide, synchronize, secure, and support the service;
  • to run features you explicitly enable;
  • to administer subscriptions and organizations;
  • to prevent abuse, enforce limits, and investigate failures; and
  • to comply with legal obligations.

Where European data-protection law applies, processing is based on performance of our contract (including AI features and memory learning), your consent for optional cloud access, our legitimate interests in security and reliability, and compliance with law. You may withdraw consent or turn off memory learning at any time.

6. Service providers

  • Google: sign-in, Gmail, Calendar, Contacts, Places address suggestions, sender favicons and airline logos (through our image proxy), Cloud KMS key custody, and encrypted backups;
  • Gravatar (Automattic): sender avatars, looked up by a hash of the sender's email address through our image proxy;
  • OpenRouter and the model provider it routes each request to: AI requests, transient, with no data collection and zero retention;
  • Stripe: billing and invoices (we never receive full card details);
  • KLIPY: GIF search;
  • MET Norway (Norwegian Meteorological Institute): weather forecasts for trip destinations;
  • Slack: feedback you send;
  • Cloudflare and our hosting provider: network delivery and infrastructure, and Cloudflare DNS-over-HTTPS lookups of sender domains for brand verification, made directly from your device.

They process data under their terms and our instructions where applicable. We may also disclose information when required by law or to protect users and the service.

7. Retention

Message content is never retained on our servers. Automation activity is kept up to 30 days and grant-broker access metadata up to 90 days. Other stored data lasts until you delete it or your account. Encrypted database backups expire after 90 days, so deleted data leaves backups within that window; backups are used only for disaster recovery.

8. Revoking access and deleting your data

  • Remove a mailbox in Settings to disconnect it. The desktop app revokes its Google grants and deletes its local copy; the web app forgets its access and local data. Either way its cloud access, if enabled, is revoked. Nothing in your Gmail, Calendar, or Contacts is deleted.
  • You can also revoke Wingman Mail at any time at myaccount.google.com/permissions.
  • Settings → Transparency → Opt-out from the cloud revokes every cloud grant and deletes all optional cloud data while keeping your account.
  • Settings → Transparency → Delete account revokes every grant, cancels your subscription, and permanently deletes your account and all data we hold about it. We keep only an opaque account identifier linked to the billing provider's records, because invoices and payment records must be retained for accounting and tax law. You can also request deletion by email; we complete it within 30 days.

9. Security

We use encryption in transit and at rest, restricted service identities, tenant-scoped storage, an isolated token broker with KMS-wrapped keys, capability allowlists, send limits, audit metadata, and revocation controls. No system is completely secure; please report suspected issues to [email protected].

10. International transfers

Providers may process data outside your country. Where required, we use recognized transfer mechanisms and contractual safeguards.

11. Your rights

You can review cloud activity, pause automations, revoke each mailbox, edit or delete memories, and delete cloud data or your whole account in Settings. Depending on where you live, you may also request access, correction, portability, restriction, objection, or deletion, and may complain to your local data-protection authority.

12. Children

Wingman Mail is intended for business and personal productivity use by people old enough to enter a binding contract. It is not directed to children under 16.

13. Changes

We may update this policy as the service changes. Material changes will be communicated through the service or the contact information associated with your account.