Magnetask

Security

Your data, and exactly what we do with it. Nothing on this page is a plan.

What we do, and what we never do

Nine things, each with the line we do not cross beside it.

01 / 09

What we ask for

Whatever you connect, Magnetask asks for the least it can work with - and for each of them, there is a matching thing it never asks to do at all.

We do
Reads the channels you connect
Reads the mailbox you connect, and sends from your own address
Reads the calendars you tick, and writes and changes the meetings you organise
Reads what was said after the call, and Gemini's notes on it
Reads the records you point it at
Never
Never posts a word in them
Never deletes, archives or labels a mail
Never touches an invitation somebody else sent you
Never joins or records a call, or opens anything else in your Drive
Never changes what a record says

02 / 09

What we keep

A captured request becomes four things: what was asked, who asked and when, a link back to where it was said, and when it is due.

We do
Becomes four things, and no more
Never
Never copies your mailbox or your channels

03 / 09

Where it lives

Four locks between you and your work: the browser reaches the site over HTTPS with a session cookie no script can read; every request to the application arrives signed in and carries its workspace; the database is reached over TLS and sits on disks encrypted at rest; and the tokens inside it are encrypted again, with a key the database never sees.

We do
A lock at each one
Never
Never a secret kept in the open

04 / 09

The key

Every integration token is encrypted with AES-256-GCM before it reaches the database, with a fresh iv each time and the key held outside it.

We do
Encrypted before they are written
Never
Never the key beside the lock

05 / 09

The wall

Two companies using Magnetask never meet. Every question the product asks on your behalf carries your workspace with it, so another company's work is not hidden from you - it is not in the answer at all. Follow a link to something in someone else's workspace and there is simply nothing there. The live updates your browser receives are held to the same line by the database itself.

We do
Each sees only its own
Never
Never one company's work in another's

06 / 09

A person decides

Nothing read from your mailbox becomes a task on its own: it becomes a draft in one person's review queue. In chat there are two exceptions you choose - a message you send the bot directly is taken as your own request, and an admin can opt in to the same for a message that @-mentions exactly one person. A discarded draft never reaches a board; it is kept, marked as discarded, and your answer is what teaches the reader. The message text behind a resolved draft is erased within 30 days.

We do
A draft, until a person says yes
Never
Never work on a board that nobody approved

07 / 09

A forged message

Every inbound webhook - Slack, Stripe, email - has its signature checked in constant time before a byte of it is acted on.

We do
Its signature checked before a byte is read
Never
Never a word acted on unchecked

08 / 09

Too many requests

Every door a stranger can push on - the support form, the newsletter box, the booking pages, sign-in, a tracked link - is rate limited: past a point the attempts are simply refused, and the cost of a flood lands on whoever is sending it. How many, how often and how it is counted are deliberately not published here.

We do
A real request goes straight through
Never
Never a flood let through

09 / 09

Leaving

Disconnect an integration, delete a workspace or close the account from inside the product. The tokens go; the work your team did stays yours.

We do
An off switch, where you made it
Never
Never read after you have gone

For each app

Every integration states its own four facts - what it reads, what it keeps, what it never does, and how to switch it off. They are on the integrations page, one app at a time.

See every integration

In the database

It is reached over TLS and never over anything else, and the disks it sits on are encrypted at rest. Row-level security is enabled on every table. Every table that holds your work carries the workspace it belongs to, and deleting that workspace deletes its rows. No card number is ever written to it: Stripe's own form takes payment. The database is hosted in the United States.

What the models see

A message is read by a model to find the request in it, and what is kept is the task. Meeting transcripts and notes are never stored, and nothing is sold. Under our providers' terms, nothing you send trains their general models. Magnetask's own reader learns from one thing: whether a person approved or discarded a draft.

In the browser

Sessions are httpOnly cookies. Two-factor authentication is available on any account, with the passwordless email path closed off so it cannot be walked around by somebody holding an inbox. The site refuses to be framed.

Found something?

Write to support@magnetask.app, or use the support page. We answer every report, and we tell you what we did about it.

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.

Privacy policyTermsAsk us something