Last updated
Where your data is hosted, who processes it, and how access to it is controlled.
Mandatum is hosted in the United States. Institutions can ask for a dedicated onshore deployment. These are the providers that handle data for us.
| Provider | What it does for Mandatum | Region |
|---|---|---|
| Vercel | Hosts and serves the Mandatum app | US East (iad1) |
| Supabase | Database, sign-in, and document storage | US East |
| Railway | Ingestion worker, document parsing (Docling), graph database (Neo4j), and cache (Redis) | United States |
| Anthropic | Analysis, chat, and drafting | To be confirmed |
| Voyage AI | Embeddings for search | To be confirmed |
| Isaacus | Embeddings for search | To be confirmed |
| Tavily | Web search | To be confirmed |
All traffic to and from Mandatum uses HTTPS. Our providers encrypt stored data under their standard configuration. We do not add a separate encryption layer on top of theirs today.
Each workspace is separate. Postgres row-level security limits every query to the workspaces the signed-in user belongs to. The application checks membership again on each request, so a single missed check does not expose another workspace.
Claude and ChatGPT connect to Mandatum through OAuth. The assistant receives an access token and sees only what the connecting user can see. To disconnect, open Settings, then Integrations, then Revoke.
Each authenticated action writes an entry to the audit log, including the user, the workspace, the action, and the time. Entries are hash-chained, so an edit to an earlier entry breaks the chain. The log is kept with the workspace it records.
Email hello@intergentech.ai (security address to be confirmed). Include what you saw and how to reproduce it. [Acknowledgement and customer notification timelines: to be set by counsel.]
A data processing agreement is available on request. Email us, and we will send the current version. Read the privacy policy for the full list of what we collect.