Privacy Policy
1. Who we are
Magpie is a personal executive-assistant service operated by xVentures Global Ltd, a company registered in England and Wales under number 12298947, registered office 124 City Road, London, England, EC1V 2NX ("Magpie", "we", "us").
For the purposes of the UK GDPR and EU GDPR, we are the data controller for the personal data described in this policy. Our contact point for privacy matters is hello@meetmagpie.ai.
2. What we collect
| Category | Examples | Source |
|---|---|---|
| Account data | Name, email address, messaging identifier, subscription and billing status | You, and our payment processor |
| Messages you send us | Text and voice messages you send to your assistant, and files you share with it | You |
| Google account data | Your Google account email address; email messages and metadata; calendar events and calendar list. See section 3. | Google, with your consent |
| Other connected accounts | Notes, documents and meeting notes from services you choose to connect | Those services, with your consent |
| Assistant-generated content | Summaries, briefings, drafts, notes and task records your assistant creates for you | Generated by the service |
| Approximate location | A town or city you set, used for weather and scheduling context | You |
| Technical and usage data | Timestamps, job outcomes, error diagnostics, usage volumes | Automatically |
3. Google user data
If you choose to connect a Google account, Magpie requests only the narrowest permissions that allow the service to function. We request the following scopes:
| Scope | What it allows | Why Magpie needs it |
|---|---|---|
openid | Confirm your identity when you sign in with Google | To sign you in without a separate password |
email | See your Google account email address | To know which account is connected and to show it to you |
gmail.readonly | Read messages and metadata | To triage your inbox, summarise what matters, and surface what needs your attention |
gmail.compose | Create, read, update and delete drafts | To write reply drafts into your Drafts folder for you to review |
calendar.readonly | See your calendars and their events | To brief you on your day and reason about your availability across every calendar you keep |
calendar.events | View and edit events on your calendars | To brief you on your day, reason about your availability, and place confirmed meetings, bookings and reminders into your calendar when you ask |
Magpie cannot send email. The service has no capability to send mail on your behalf. It writes drafts into your own Drafts folder, and you send them yourself from your own email client. This is enforced in our software architecture rather than by policy alone: no mail-sending capability exists anywhere in our codebase, and an automated check asserts this on every release.
We request gmail.compose because Google provides no draft-only permission.
Although that scope would technically permit sending, our service is built so that it cannot.
We do not request permission to permanently delete your mail, and we do not request the broad
https://mail.google.com/ permission. For calendars we request only the events
permission, not the wider calendar permission that would also allow us to create,
share or delete whole calendars.
What Magpie writes, and what it only proposes. Magpie can create and update calendar events; that is how it puts a confirmed booking or meeting in your diary. It can create email drafts. It cannot send email, and it cannot delete your mail. Anything it arranges outside Google (a restaurant table, for instance) happens through that provider, not through your Google account.
4. Limited Use commitment
Magpie'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.
The use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
Specifically, we confirm that we do not:
- use Google user data to train, improve or develop generalised artificial-intelligence or machine-learning models;
- transfer or sell Google user data to advertising platforms, data brokers or information resellers;
- use Google user data for advertising, including retargeting or personalised advertising;
- allow any person to read your Google user data, except in the narrow circumstances set out in section 10.
5. How we use your data
We process your data only to provide the assistant service you have asked for: reading and triaging your inbox, briefing you on your day, drafting replies for your review, placing confirmed events in your calendar, capturing notes and tasks into your personal knowledge vault, and answering your questions about your own information. We also use technical and usage data to operate, secure and debug the service, and account data to bill you.
Our lawful bases are performance of a contract with you for the core service; your consent for each account you choose to connect, which you may withdraw at any time; and our legitimate interests in securing and improving the service, in a manner consistent with the restrictions in section 4.
6. AI processing
Magpie is built on large language models. To answer your requests and produce your briefings and drafts, the content necessary for a given task is transmitted to our AI providers for processing. This is inference only: your content is used to produce your result and is not used to train any model.
We use every AI provider on a paid tier whose terms prohibit training on submitted content and prohibit human review of it. We do not use free or consumer tiers of any AI service for customer data, because those tiers generally permit both. We do not send Google user data to any service whose terms would allow it to be used for model training or read by a person.
Automated systems process your content in order to deliver the service. Magpie's output, particularly email drafts and factual summaries, may be inaccurate and is presented for your review. Nothing is sent, booked or committed on your behalf without your action.
7. Website and app analytics
We use PostHog, hosted in the European Union, to understand how the website and the app are used, so we can improve them. We do not use analytics for advertising, and we do not share analytics data with advertisers or data brokers.
On this website we record page views and a small number of named interactions (for example, that a demo was started or a waitlist form was submitted), together with your browser type, screen size and country, derived from your IP address and not stored. We do not set analytics cookies or store an identifier on your device: a fresh anonymous identifier is created for each visit and discarded when you leave. We do not record your screen or your typing, and the demo brief and chat you create are not sent to analytics. Because nothing is stored on your device, you will not see a cookie banner.
In the app, analytics are tied to your account so we can see which features you use and where things go wrong. We record which screens you open and which actions you take, not the content of your email, calendar, notes or messages, and we do not record your screen. You can ask us to exclude your account from analytics at any time by emailing hello@meetmagpie.ai.
Browser settings and extensions that block analytics are respected: if PostHog is blocked, nothing is sent and the site and app work exactly the same.
8. Subprocessors
We share data with the following processors, each bound by a data-processing agreement:
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Anthropic | Language-model inference: the assistant itself | Task-relevant content, including email and calendar content | US |
| Groq | Voice-note transcription | Audio you record | US |
| PostHog (EU) | Product analytics for the website and app | Page views and named interactions; browser and device type; country. No content, no recordings. | EU |
| Google (Gemini API) | Spoken audio briefings | The text of your briefing, which may include summaries of your email and calendar | US |
| Telegram | Message delivery, if you use the Telegram interface | Messages exchanged with your assistant | Varies |
| Hetzner Online GmbH | Hosting and storage | All service data at rest | Germany (EU) |
| Cloudflare | Website delivery and security | Website request data | Global edge |
Paid subscriptions are not yet operating. Before we charge any customer we will name our payment processor in this table; we will never hold full card numbers ourselves.
Where a provider is outside the UK or EEA, transfers are made under UK International Data Transfer Agreements or EU Standard Contractual Clauses with supplementary measures as required. Services you choose to connect, such as note-taking or code-hosting tools, receive data only at your direction, and their own privacy policies govern their handling of it.
9. Storage and location
Each customer's data is held in a separate, isolated environment with its own storage. Your data is not commingled with another customer's, and no part of the service reads across customer boundaries. Primary storage is in Germany (EU).
10. Human access
Our staff do not read your email, calendar entries, notes or messages. Access to systems holding customer content is restricted, logged, and permitted only where:
- you have given specific, affirmative agreement for us to view particular items, for example when you ask for help with a problem and authorise us to look;
- it is necessary to investigate a security incident or abuse; or
- we are compelled by law.
Our operational logs are designed to exclude the content of your messages, email and documents.
11. Retention and deletion
| Data | Retention |
|---|---|
| Your knowledge vault and assistant-generated content | For the life of your account |
| Cached email and calendar content | 30 days, then deleted |
| Operational logs | 30 days |
| Billing records | As required by law, typically 6 to 7 years |
You may disconnect a Google account at any time, from within Magpie or via your Google account permissions page. On disconnection we stop accessing that account and delete data derived from it within 30 days, except where retention is legally required.
On account closure, your environment and all content in it are destroyed within 30 days. You may request an export of your vault beforehand.
12. Security
We encrypt data in transit using TLS and at rest. Credentials and access tokens are stored encrypted and are never written to logs. Each customer's environment is isolated. Our application undergoes an annual independent security assessment under the App Defense Alliance's Cloud Application Security Assessment (CASA) framework, as required for applications handling restricted Google Workspace data. We operate least-privilege access control with audit logging, and maintain an incident-response process under which we will notify affected users and regulators of a personal data breach within the timeframes required by law.
13. Your rights
Subject to applicable law, you have the right to access, correct, delete, restrict and object to our processing of your personal data, to data portability, and to withdraw any consent you have given. To exercise a right, contact hello@meetmagpie.ai; we respond within one month. You may complain to the UK Information Commissioner's Office at ico.org.uk, or to your local supervisory authority.
14. Children
Magpie is not directed at children and is not intended for anyone under 18. We do not knowingly collect personal data from children.
15. Changes
We will post any change here and update the date above. Where a change materially affects how we handle your data, we will notify you in advance and, where the law requires it, seek your consent.
16. Contact
xVentures Global Ltd
124 City Road, London, England, EC1V 2NX
hello@meetmagpie.ai
See also our Terms of Service.