Everything on this page is generated from the same lists and settings the software runs on, so it changes when they change. It is a summary: the privacy policy and section 12 of the terms are the authoritative text.
When a workspace is created you choose where its AI works: standard or EU hosting. An owner can restrict it further, for the whole workspace or per department, on the Security page.
Every model your workspace allows, including providers in the USA. A new team starts on Claude (Anthropic Ireland, Limited and Anthropic PBC, USA or worldwide (the provider may route requests globally)). The manager that answers in your workspace chat starts on OpenAI (OpenAI Ireland Limited and OpenAI, USA) where that provider is enabled, and an owner can choose another.
European data centres: the EU, plus Switzerland and Norway where a provider's EU zone includes them.
AI processing only on these routes, where the provider is enabled on our deployment:
Image and video generation have no EU route, so an EU-hosted workspace does not use them. Web search runs through an EU provider that passes the query to a US search service, and the knowledge base is indexed with an EU-hosted embedder.
Under both options, the application, the database and your files are here:
Every company that may process your data on our behalf, with the country it processes in and the legal basis for the transfer. The privacy policy carries the same list with a description of each.
List version 2026-10-18, in force from 2026-11-17 for workspaces created before it.
Added NVIDIA Corporation (NVIDIA NIM, USA) as an optional model provider (Nemotron 3.5 Super VL 120B); off unless configured and the workspace's data-residency policy allows the USA, and for workspaces created before 18 October 2026 it starts on 17 November 2026, or earlier if an owner accepts this list. In addition, the roles of OpenAI and Google now name every use the privacy policy already describes: besides running agent models, OpenAI transcribes dictation, reads replies aloud and generates images, and Google transcribes dictation, generates images and runs the Veo video engine — each only where configured and where the workspace's data-residency policy allows the USA.
We give at least 30 days' notice before we add or replace a sub-processor, and you may object (terms §12(d)).
Whether your business may use Entumo depends on the secrecy rules of your profession. The short answer per profession:
The full answer with the statutes, per profession
This is orientation, not legal advice. Your professional association, a data protection officer or a lawyer decides the individual case.
You are the controller, we are your processor (DSG Art. 9). Section 12 of the terms is the data processing agreement: accepting the terms concludes it, and Swiss law requires no separate signature.
These mechanisms are built into the product and checked by our automated tests on every release. They are our own engineering checks; no outside auditor has assessed them.
The API tokens and sign-ins your employees use for connected tools are stored encrypted (AES-256-GCM), each bound to its workspace and connector, and decrypted only on the server when a connector runs.
Accounts can require a code from an authenticator app, with recovery codes. The authenticator secret itself is stored encrypted.
Connecting a mailbox, exporting the workspace, making someone an owner or spending money asks for the password again when the last sign-in is more than 15 minutes old.
A new password is checked against a local list of common passwords and against public breach data. Only five characters of a hash are sent, never the password.
Actions your approval rules cover wait for a person. Each request and each decision is kept in the decision history, and consequential actions are written to the audit log.
Where a connector supports it, a change written to another system is read back from that system before a run reports it as done. A read that fails is reported as unverified, never as success.
Content written by people outside your company, such as incoming e-mails and web pages, is labelled as outsider-written before an employee reads it, and the run that read it is flagged.
Messages an AI employee sends on your behalf through the built-in channels open with a notice that AI wrote them for your company; public posts carry an AI label. The notice cannot be switched off.
Retention periods and your other rights are in the privacy policy.
Found a security problem, or received something harmful from a Entumo employee? Use the report page, no account needed, or write to abuse@momentumq.com.
In scope: vorenq.com and the application, tested with accounts you created yourself. Out of scope: other customers’ workspaces and data, third-party providers and connected tools, denial-of-service attacks, social engineering and physical access. Use the report page (choose “Something else” and start your description with “Security”) or the address above, and do not include customer data you came across.
We authorise good-faith testing inside this scope on our own systems and will not file a criminal complaint against you for it. We cannot authorise access to other customers’ data, to third parties’ systems or to the tools of connected customers, and this page does not waive anyone else’s rights.
We acknowledge reports as soon as we can and aim to fix confirmed vulnerabilities within 90 days; please give us that time before you publish details.