Each activity is listed with its data, its purpose, its legal basis under the GDPR, and how long the data is kept.
Your account
To give you an account and sign you in. Your email address is stored encrypted, with a keyed hash so we can find your account without decrypting every address. Your password is stored only as an Argon2id hash. When you turn on two-factor sign-in, its secret is stored encrypted and its recovery codes only as hashes. Verification and reset links are stored only as hashes.
DataEmail address, password hash, display name, initials, language, account tier and status, two-factor sign-in secret, recovery code hashes, the time of sign-in failures.
Legal basisContract, Art. 6(1)(b) GDPR: the account is the service you sign up for.
Signing in
Strictly necessary
To keep you signed in between pages. After sign-in the browser holds one cookie. The server keeps a hash of it, the time it was created and last used, and whether two-factor sign-in was completed. The server stores no IP address and no browser details with a session. After 10 failed sign-ins in a row, the account is locked for 15 minutes.
Cookie__Host-synteum_session HttpOnly, Secure, SameSite=Lax
Legal basisContract, Art. 6(1)(b) GDPR. The cookie is strictly necessary for the service you ask for, so it needs no consent. The lockout serves our legitimate interest in protecting accounts, Art. 6(1)(f).
KeptThe session ends after 7 days without use, after 30 days at most, or when you sign out. Ended sessions are deleted within a minute.
Workspaces and what you put in them
To run the boards you and your team work on. This covers projects, boards, tasks, comments, checklists, logged time, tags, attachments, notifications, and the members of a workspace with their roles. Names and free text are encrypted on the server with a key for each workspace. Files you attach and images you paste into a description go to your own Google Drive (see Google Drive storage). The icons of workspaces, projects and boards are the only images Synteum stores itself: checked, re-encoded and encrypted, at most 0.5 MB each. Members of a workspace see each other's names and the content of the projects they may open. When a member invites you, we store the email address they typed, encrypted, to send the invitation.
Legal basisContract, Art. 6(1)(b) GDPR. For an invitation to a person without an account: our legitimate interest, and that of the inviting team, in letting a team invite a colleague, Art. 6(1)(f).
KeptWhile the workspace exists. A deleted workspace is kept 30 days so it can be restored. Then its keys are destroyed, and nothing in it can be read again. A read notification is deleted after 90 days. An invitation link expires after 7 days.
Mail we send
To send what your account and your workspaces need: address verification, password reset, invitations, task alerts and digests, notifications, export and deletion notices, and security notices (a new two-factor device, a used recovery code, a locked account, a vault unlock from a new device, a hardware key added or removed, an unlock refused without the hardware key, a recovery that waits). Each mail is queued in our database with its recipient, subject and body encrypted. After sending, the content is removed from the queue, and the queue entry is deleted 30 days later.
Legal basisContract, Art. 6(1)(b) GDPR. Security notices: our legitimate interest in protecting your account, Art. 6(1)(f).
KeptQueue content until sent, the queue entry 30 days.
Your vaults
To keep the tables you store in the vault (Account, Vault). Your browser creates the vault key and every token, and encrypts each table before it is uploaded. The server stores only that ciphertext, the vault key in wrapped form, and hashes it uses to check a token or a recovery code. It cannot open your vault, and nothing from the vault is ever written to Google Drive. To warn you about an unlock you did not make, the server records, for each token and trusted device, the graphics card your browser reports (vendor and model) and the IP address it sees. Both are stored encrypted, shown only to you, and never used as a key. When a token or device is used from a graphics card or network it has not used before, we mail you.
If you add a hardware key to your vault (for example the U2F app of a Flipper Zero), the server stores for each key the credential id and public key the key creates, its signature counter, the name you give it (encrypted), when you added it, when it was last used and when you removed it. Each confirmation also leaves a single-use challenge for up to 2 minutes. The key only proves that you hold it: it never opens the vault alone and never becomes part of the vault key. No name, address or device serial number is sent to the key or stored for it.
The Token vault of a workspace and the Vault of a project work the same way for a team (Workspace, Token and Project, Vault). Your browser makes the two keys of a shared vault, wraps them for the identity key of each member who may hold them, and encrypts every table before upload. The identity key is a key pair your browser makes with your personal vault; its private half is stored encrypted under your personal vault key. The server stores the wrapped keys, the identity public keys and the ciphertext, checks the role of each member before it hands out a wrapped key, and writes to the audit log who opened the vault and who revealed or copied which cell position, never the value. When a member leaves, is removed, loses the role or the project, or deletes the account, the server deletes their wrapped keys at once and the next holder makes new keys in the browser. Nothing from a vault, personal or shared, is ever written to Google Drive.
Legal basisContract, Art. 6(1)(b) GDPR, for the vault. Our legitimate interest in detecting an unlock you did not make, Art. 6(1)(f), for the graphics card and IP records. Contract, Art. 6(1)(b), for the hardware keys you add.
KeptVault data until you delete it or your account. Shared vault data until a holder deletes it, the project or the workspace is deleted, or nobody can open it anymore and an Owner or Admin removes it. When you revoke a token or device, or rotate the vault key, its history of graphics cards and networks is deleted. Only the last ones stay on the revoked entry in your list until you delete your account. A hardware key stays until you delete the vault or your account; a removed key stays on your list as removed until then. A challenge is deleted when it is used, when you ask for a new one after it expired, or with the vault.
Google Drive storage
Needed to upload
To attach a file or paste an image, you connect your own Google Drive after sign-in, through a Google client you create yourself in Google Cloud. Synteum stores that client's id and its secret, encrypted, until you remove them or delete your account. What you upload goes into your Drive, in the folder Synteum, under your own terms with Google. Google receives the file, its name and its type. Synteum keeps only the file name, size, type and the Drive file id, so it can show the file to the members who may see the task. Synteum asks Google only for access to the files it creates. Members never get access to your Drive itself: they see the file only through Synteum. The access key from Google stays on our server, encrypted, and is deleted when you disconnect the Drive or delete your account. Without a connection you cannot upload. When you disconnect or leave a workspace, your files show as unavailable there.
Legal basisContract, Art. 6(1)(b) GDPR: storing your files where you chose.
KeptFiles stay in your Drive under your control. The access key until you disconnect or delete your account.
AI assistant
Off unless turned on
The assistant is off in every workspace until its owner turns it on. A member then asks it to create, rewrite or delete tasks. To answer, Synteum sends Anthropic, using an Anthropic API key that a member or the workspace added: the request, the task style of the workspace, and the tasks of the board (key, title, description, status, column, priority, type, the assignee's internal id) with up to 20 comments without their authors. The assistant only proposes changes. A person applies them, and a deletion needs a confirmation per task. Synteum stores API keys encrypted, a log of each use (who, which project, model, tokens, cost), and the proposals, encrypted with the workspace key. The request text itself is not stored.
Legal basisContract, Art. 6(1)(b) GDPR, for the member who uses it. For the colleagues named in the tasks sent: our legitimate interest, and that of the workspace, in providing the assistant the workspace turned on, Art. 6(1)(f).
KeptAPI keys until revoked or their owner leaves the workspace. Proposals 90 days. The usage log for the current month and the 12 before it. Anthropic keeps what it receives under the terms of the account that owns the API key.
Agents, the REST API and integrations
An AI client that connects to the MCP server at mcp.synteum.com signs in with your account and acts with your role, as described on the agents page. Programs use the REST API with your session or with a credential a workspace admin created. A workspace admin can also send workspace events to a webhook address, and give out a calendar feed link that shows tasks with due dates. These go only where the workspace sends them.
Legal basisContract, Art. 6(1)(b) GDPR.
KeptAn agent's access token lives 15 minutes, and its sign-in ends with your session. A calendar feed link works for 90 days.
Exports
When you ask for an export of your account or of a workspace, we build it as a file, encrypted on our server, and mail you when it is ready. A workspace can also turn on a nightly export.
Legal basisContract, Art. 6(1)(b) GDPR, and your right to data portability, Art. 20.
KeptAn export file 7 days. The nightly export keeps the last 7 copies.
Security, abuse prevention and records
To keep the service working and to prove what happened. Every request is logged with its time, method, path, result and the IP address it came from. Limits on the number of requests are counted per IP address in memory. So that a repeated request from someone who is not signed in does not run twice, its idempotency key is stored with the IP address for 24 hours. Actions in accounts and workspaces are recorded in an audit log, with who acted, what changed, and when. The audit log stores no IP address, and free text in it is encrypted or left out. A tamper-evident chain protects it.
Legal basisOur legitimate interest in securing the service, preventing abuse, and being able to show what happened in an account, Art. 6(1)(f) GDPR.
KeptRequest logs 30 days. Request counters 10 minutes. Idempotency keys 24 hours. Audit records 3 years.
Website analytics
Only with consent
To learn how people find and use the public pages of the website, so we can improve them. We use Google Analytics 4 (property G-DN5MT40QL0). It runs only after you choose Accept all or switch analytics on in the consent dialog or on the cookies page. Before that, the page loads nothing from Google. It sets two cookies, _ga and _ga_DN5MT40QL0, with a random visitor ID and the state of your visit. The signed-in app does not load Google Analytics. We never send a name, id or key of a workspace, project, board or task, a tag, any content you write, your email address or your account id: the page address keeps only campaign parameters, and the address of a synteum.com page you came from is reduced to a neutral path. Google signals and ad personalisation are off.
DataThe random visitor ID in the cookies, the public page you view with its path and title, the referring site, campaign parameters, engagement time and events on the page (scrolling, clicks on links to other sites, file downloads, the start of a form), whether you visited before, device type, browser, operating system, screen size, language, and approximate location (country and region) that Google derives from your IP address. Google Analytics does not log or store IP addresses of visitors in the EU.
Legal basisYour consent, Art. 6(1)(a) GDPR. Storing and reading the cookies needs your consent under Art. 5(3) of the ePrivacy Directive, in the Czech Republic § 89(3) of Act No. 127/2005 Coll. on electronic communications. You can withdraw it at any time (see Withdrawing consent).
RecipientGoogle Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, as our processor under the Google Ads Data Processing Terms. Google LLC in the USA can process the data as its subprocessor (see Transfers outside the EU).
KeptEvent data in Google Analytics: 2 months. The cookies: 13 months after your last measured visit, or until you withdraw consent, which deletes them.
Answering your messages
If you write to us, by email or through the contact form, we process your name, your email address and what you send, in order to reply. The contact form sends your message to our support mailbox.
Legal basisLegitimate interest, Art. 6(1)(f) GDPR, in answering you. Legal obligation, Art. 6(1)(c), applies when your message exercises a data-protection right.
KeptWhile we handle your message and as evidence that we handled it correctly. It is deleted after that.