Cookies a místní úložiště

Vaše volba pro tento web

S vaším svolením Synteum používá Google Analytics k počítání návštěv a ke zjištění, jak lidé nacházejí a používají veřejné stránky tohoto webu. Používá také místní úložiště tohoto prohlížeče, aby si pamatoval vaši nástěnku aplikace a předvolby rozhraní.

Nic volitelného se nespustí ani neuloží, dokud se nerozhodnete. Pokud odmítnete, všechny stránky budou dál fungovat. Analytika nikdy nevidí vaše pracovní prostory, projekty, nástěnky ani úkoly.

Svou volbu můžete kdykoli změnit odkazem Nastavení cookies v zápatí.

Synteum Zpět na úvodní stránku

Právní informace · Soukromí

Informace o ochraně osobních údajů

What Synteum does with personal data, for each part of the service: the website, the signed-in app, the REST API, the MCP server for AI agents, and the mail we send. Every statement on this page was checked against the code that runs the service.

Effective 12 November 2026 Version 2.4 Controller: SZEINER s.r.o.

At a glance

  • Synteum is a task platform with accounts. When you sign up, your account and the workspaces you create or join are stored on our servers, at a hosting provider in the EU.
  • The text of a workspace is encrypted on the server with a key for that workspace. Your personal vault is encrypted in your browser, and the server cannot read it.
  • Synteum sets one cookie of its own: the sign-in session cookie, and only when you sign in. With your consent, Google Analytics measures visits to the public pages of the website. The signed-in app never loads it, and there is no advertising.
  • You decide what goes into your workspaces, and you are the controller of that content. Synteum provides the tool and processes it for you.
  • Files you attach and images you paste go to your own Google Drive, which you connect after sign-in. Synteum itself stores only the icons of workspaces, projects and boards.
  • The AI assistant sends task text to Anthropic only when a workspace turns it on and a member uses an Anthropic API key. Google Drive, Google Analytics and Anthropic can involve a transfer outside the EU.
  • You can export your data and delete your account in Account settings. The deletion runs 30 days after the request.
  • Questions and requests: [email protected]. Security reports: [email protected]

Who is responsible

Synteum is operated by SZEINER s.r.o., a company registered in the Czech Republic. Synteum is a project management tool, and the responsibility is split by who decides what happens with the data.

  • Your workspace content. The person or organisation that owns a workspace decides what goes into it: tasks, comments, files, members. They are the controller of that content. SZEINER s.r.o. processes it on their behalf, only to run the tool (Art. 28 GDPR). A request about the content of a workspace goes to its owner first. We help them answer it.
  • Running the service. SZEINER s.r.o. is the controller of the data it needs to run Synteum itself: your account and sign-in, security and abuse records, the audit log, the mail the service sends, and messages you send to us.
Registered addressZbýšov 90, 683 52 Zbýšov, Czech Republic
Privacy contact[email protected]

What this notice covers

The public pages of synteum.com with the live board on the landing page, the signed-in app under synteum.com/app, the REST API under synteum.com/v1, the MCP server at mcp.synteum.com, and the mail that Synteum sends. The live board on the landing page works without an account and keeps its data in your browser. Everything else needs an account.

What is processed, why, and on what basis

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.
KeptUntil your account is deleted. See How long data is kept for what deletion removes.

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.

Stored on your device

Besides the sign-in cookie, the site keeps these items in your browser. The cookies and storage page lists them with their controls.

  • synteum-consent-v1 your choice about analytics and optional storage. Legal obligation, Art. 6(1)(c) GDPR: we must be able to show your choice (Art. 7(1)). When you are signed in, your choice is also saved with your account.
  • lanes-v5-app-v1 lanes-v16-sort lanes-v31-lang the landing board, its sort order and language. Only with your consent, Art. 6(1)(a) GDPR.
  • _ga _ga_DN5MT40QL0 cookies of Google Analytics: a random visitor ID and the state of your visit. Only with your consent, Art. 6(1)(a) GDPR (see Website analytics).
  • synteum-vault in IndexedDB: the key of a trusted device for your vault, created only when you make this browser a trusted device.
  • __pt-enter in session storage: a marker for the page transition, deleted when the tab closes. It holds no personal data.

The Synteum browser extension and the USB helper for the vault, if you install them, keep only the drive you chose. A Flipper Zero counts as such a drive: the helper reads and writes the token file in the .synteum folder of its SD card over its USB serial port. Your token file on that drive stays protected by its passphrase. Neither sends anything anywhere except to the synteum.com page you have open.

Who receives data

  • A hosting provider in the EU runs our servers and database.
  • Cloudflare, Inc. carries the traffic to synteum.com and sees each request, including your IP address.
  • Seznam.cz, a.s. delivers the mail we send and hosts our mailboxes in the EU.
  • Google, for the files you upload to your connected Google Drive (see Google Drive storage).
  • Google Ireland Limited, as our processor for Google Analytics, only when you consent to analytics (see Website analytics).
  • Anthropic, only when a workspace turns on the AI assistant and a member uses it (see AI assistant).
  • The members of your workspaces, within their roles, and the webhook addresses, calendar apps and programs a workspace admin connects.

We sell no data and share none for advertising. Google Analytics runs with Google signals and ad personalisation off.

Transfers outside the EU

Our servers and our mail are in the EU. Four recipients can process data outside the EU or EEA. Cloudflare, Inc. and Anthropic are based in the USA, a Google Drive may store files outside the EEA, and Google LLC in the USA can process Google Analytics data as the subprocessor of Google Ireland Limited. Each of them handles the data under its own safeguards for international transfers, such as the EU standard contractual clauses or the EU-US Data Privacy Framework where it participates. You can ask us for a copy of the safeguards at [email protected].

How long data is kept

AccountUntil deleted. Deletion runs 30 days after you request it in Account settings.
Sessions7 days without use, 30 days at most.
WorkspacesWhile they exist, then 30 days, then their keys are destroyed.
Mail queueContent until sent, the entry 30 days.
Exports7 days. Nightly exports: the last 7 copies.
Request logs30 days.
Audit records3 years.
AI assistantProposals 90 days. The usage log of a key: the current month and the 12 before it.
IntegrationsWorkspace events 1 year, while no notification or pending delivery needs them. Webhook deliveries 90 days after they finish.
Links in mailVerification and reset links: 7 days after use or expiry. Unfinished Google sign-ins: 7 days after they expire.
Website analyticsIn Google Analytics 2 months. Its cookies 13 months after your last measured visit, or until you withdraw consent.
Messages to usWhile we handle them and as evidence of correct handling, then deleted.
On your deviceUntil you withdraw consent, sign out, or clear this site's data.

When your account is deleted, we remove your sign-in data, two-factor data, sessions, preferences, consent records, exports, invitations to your address, your vault, your Drive connection and your API keys. We keep your account as an anonymous placeholder named "Erased account", because comments, logged time and history in workspaces of other people still point to it. Their text stays with those workspaces. Audit records stay for their 3 years.

How the service is secured

  • Encryption at rest. Account data and mail are encrypted with a platform key, and workspace content with a key for each workspace. A deleted workspace loses its key.
  • Zero-knowledge vault. The vault is encrypted in your browser. The server never holds its key.
  • Passwords. Stored only as Argon2id hashes. Two-factor sign-in is available to everyone, and required for Synteum's own administrators and moderators.
  • Encrypted connections. The site is served over HTTPS only, and browsers are told to keep it that way.
  • No outside code. Fonts and scripts come from synteum.com itself, and the browser is told to load nothing from elsewhere.
  • Tamper-evident audit log. Each record is chained to the previous one with a keyed hash.

These statements describe the service on the effective date. They are not a certification claim: Synteum holds no certification against any security or AI-management standard.

Incidents, reports, and concerns

If a security incident affects personal data, we assess it and, where the GDPR requires, inform the supervisory authority within 72 hours and the people affected without undue delay. If you notice something wrong, write to [email protected].

Security vulnerability reports go to the same address. Privacy concerns and everything else go to [email protected]. Good-faith reports are handled confidentially and without reprisal.

Your rights

Under the GDPR you can, at any time:

Access · Art. 15Ask what data we hold about you and receive a copy. Account settings also make an export for you.
Rectification · Art. 16Have inaccurate data corrected. You can change your name and language in Account settings.
Erasure · Art. 17Have data deleted. Account settings delete your account 30 days after the request.
Restriction · Art. 18Have processing paused while something is contested.
Portability · Art. 20Receive the data you gave us in a machine-readable form, through an export.
Objection · Art. 21Object to processing based on legitimate interest.

To exercise any of them, write to [email protected]. We respond within one month. If you own a workspace that other people use, you first transfer it or remove them before your account can be deleted.

You can also lodge a complaint with the Czech supervisory authority: Úřad pro ochranu osobních údajů (Office for Personal Data Protection), uoou.gov.cz.

Withdrawing consent

You can withdraw your consent to analytics and to optional storage at any time, as easily as you gave it: one click. Withdrawing stops Google Analytics at once, deletes its cookies and the stored preference items, and nothing from Google loads on later visits. It does not make the processing that happened before withdrawal unlawful. It ends it. Data Google Analytics already received is deleted when its 2 months end. To have it deleted sooner, write to [email protected].

Saved choice in this browser

No choice saved

Nothing optional runs or is stored. The consent dialog asks for a choice on the next public page you open.

The same withdrawal is available in other places:

  • On every public page: Cookie settings in the footer reopens the consent dialog, where you can reject all, or open Custom, switch a category off and save.
  • On the cookies page: one switch for analytics and one for preferences.
  • In your browser: clearing this site's data removes everything, including the consent record.

Is any of this required?

You can read the site and use the live board on the landing page without giving any personal data. An account needs an email address and a password: without them we cannot create it. Everything else in an account is up to you.

Automated decisions and profiling

There is no automated decision-making about you and no profiling within the meaning of Art. 22 GDPR. Task alerts rate tasks by their dates and state, not people. The 15-minute lock after 10 failed sign-ins is a temporary security measure. The AI assistant only proposes changes to tasks, and a person decides whether to apply them.

Changes to this notice

Material changes bump the version and effective date above. When the optional items or their notice change, the consent dialog's own notice version changes with it, and the dialog asks for a fresh choice.

2.412 November 2026Website analytics added: Google Analytics 4 on the public pages, only with consent, its data, legal basis, processor, transfer and retention. Its two cookies are listed under Stored on your device, Google Ireland Limited under Who receives data, Google LLC under Transfers outside the EU, and the retention under How long data is kept. Withdrawing consent now stops analytics and deletes its cookies. The consent dialog moved to notice version 2026-11-12.1.
2.38 November 2026Your vaults now lists the hardware keys you can add to a vault (credential id, public key, signature counter, encrypted name, dates) and their single-use challenges, how long both are kept, and the new security mails about them. The USB helper can keep the token file on a Flipper Zero.
2.28 November 2026Your vaults now covers the shared vaults of a workspace and its projects: the identity key of your personal vault, the wrapped keys per member, the audit of reveal and copy, and what happens when a member leaves. Google Drive now uses each user's own Google client (D328). How long data is kept now lists the AI assistant proposals and usage log, workspace events, webhook deliveries, mail links and unfinished Google sign-ins (D333).
2.18 November 2026Who is responsible now separates your workspace content, where the workspace owner is the controller and Synteum processes it for them, from the data Synteum needs to run the service. Uploads go to the uploader's own Google Drive, and the icons of workspaces, projects and boards are the only images Synteum stores, at most 0.5 MB each.
2.08 November 2026Rewritten to cover the whole service: accounts, sign-in with its session cookie, workspaces, mail, the personal vault with its device records, Google Drive, the AI assistant, agents and the REST API, exports, security records, recipients, transfers and retention. The earlier statements about no accounts, no cookies, and fonts and scripts from outside hosts no longer applied and were removed. The optional storage items are unchanged, so the storage dialog keeps its notice version.
1.431 October 2026Who receives data now says that mail we send and receive passes through Seznam.cz, a.s., which hosts our mailboxes in the EU.
1.318 July 2026Contact details set: general questions and rights requests go to [email protected], security and vulnerability reports to [email protected]. Footer contact link updated to match, and the controller's registered address filled in. Inventory, purposes, durations, and bases unchanged.
1.218 July 2026Rewording pass: the in-browser workspace is described as the Synteum web app throughout. Analytics line added under the processing purposes: none runs unless you accept cookies. Prose restructured to drop semicolons. Inventory, purposes, durations, and bases unchanged.
1.118 July 2026Added "How this site is secured" and "Incidents, reports, and concerns". Report channel noted at the top. No change to the processing inventory.
1.017 July 2026First publication. Matches storage-dialog notice version 2026-07-17.3.