You are connecting a mailbox. Here is exactly what happens to it.
Magnetask asks for access to the places your team talks. That is a real thing to hand over, so this page states plainly what is read, what is stored, and what protects it - in specifics, not adjectives.
Reading your email, precisely scoped.
What it reads
Message content from the mailbox you connect, to detect which messages contain an actual request.
What it keeps
The task it creates and a link back to the source message - not a copy of your mailbox.
What it changes
Magnetask never asks for permission to modify your mail, so it cannot label, archive, move or delete anything. That is not a promise about our behaviour - it is a permission we do not hold.
Who can connect
A Workspace admin can connect the organisation, or an individual can connect only their own mailbox. Whichever is used, access can be revoked at any time from your Google account.
Magnetask's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Your message data is never sold, never used for advertising, and never used to train generalised AI models.
What protects it.
Integration tokens are encrypted at rest
The OAuth tokens that let Magnetask read your Slack or Gmail account are encrypted with AES-256-GCM before they touch the database. They are never stored in plain text.
Tenant isolation in the database, not just the app
Every workspace's data is separated by Postgres Row-Level Security, enforced by the database itself across the schema. A bug in application code cannot hand one team another team's rows, because the database refuses the read.
Every webhook is verified before it is trusted
Inbound webhooks - Slack, Stripe, email - have their signature checked before a single byte is acted on. An unsigned or mis-signed request is discarded.
Two-factor authentication
Available on any account, with the passwordless email-code path deliberately closed off so a second factor cannot be walked around by somebody holding an inbox.
A person approves every captured task
Nothing read from your Slack or Gmail becomes a task on its own. It becomes a draft that a person reviews. Auto-confirm is opt-in, and only for a message that names exactly one teammate.
Private by default, per person
What Magnetask captures for one person stays in their own review queue. Sharing a private task is a deliberate action by the person who owns it.
Leaving is as self-serve as arriving.
You can disconnect any integration without deleting your account, delete a workspace without deleting your account, or close the account entirely - each from inside the product, without emailing anybody to ask.