Where your contracts are, and who can see them.
The questions a CFO asks before handing over the company's agreements, answered in one place.
Files in Norway, everything in Europe
Files are stored encrypted in Microsoft's data centre in Norway, each workspace in a storage container of its own. The register's database runs in Ireland. Files are read by Claude on Amazon Bedrock in Frankfurt, or on Best by your own EU endpoint. No file is sent to a model outside Europe.
Separated from other customers
Every row in the database carries its workspace, and every lookup is filtered on it. Inside the workspace, folder permissions decide who sees what.
No direct links
Files have no public address. Every opening goes through us, is checked against your access and is logged, including downloads and exports.
External readers
On Better and Best, an auditor or buyer gets a one-time link that expires after 48 hours, a 24-hour session, and only the folders someone opened for them, for at most 180 days. Every PDF they see is watermarked. They can't change anything.
Outside services that handle your data
Every company we use to process your data, what it does and where.
| Heroku (Salesforce) | Runs the app, its database and its job queue | Ireland |
| Microsoft Azure | Stores the files, encrypted, one container per workspace | Norway |
| Amazon Web Services | Reads the files with Claude (Anthropic's model) on Amazon Bedrock, answers questions, and sends the Monday email and the reminders | Germany |
| Only if you connect Google Drive. We read from your account and never write to it | Your account | |
| Fiken, Tripletex | Only if you connect your accounting system. We read from your account | Your account |
Data processing agreement
You are the controller of your contracts and the personal data in them. We are the processor. A data processing agreement comes with every plan, as part of the terms, and you can read it before you start.
Two ways to delete, and one that happens by itself
Most people who want to delete an agreement want to get rid of the file, not the knowledge of when it renews. So these are separate buttons, never the same one.
Delete the file, keep the entry
The document leaves every page at once and waits 30 days in the deletion queue, where it can be taken back. Then it is deleted from storage. Counterparty, dates, deadlines and history stay, so the Monday email keeps reminding you. The entry remembers what the file was called.
Delete everything
The file, the entry, the dates, the deadlines, the history and the log of who read it. The agreement waits 30 days in the deletion queue first, where it can be taken back. Only someone who manages its folder can do this.
Delete after parse
Fetch, read, confirm, and the file goes to the deletion queue by itself, to be deleted from our system 30 days later. The entry stays. Deletion happens only after a person has confirmed the reading, never on a suggestion alone.
With this on, the data room doesn't keep the documents. An auditor or buyer sees what the register says about them, not the files.
The log
Who has read what is kept for 12 months and then deleted automatically. We keep it as long as it answers who has seen what, and no longer.
Take everything with you
Everything in your workspace, in one archive you can take to another system, or to none. It works on every plan, and cancelling a plan deletes nothing. With delete after parse on, the archive holds the register, not the files.
- All files, in folders following the data room index
- The register as CSV, each date marked confirmed, corrected or suggested
- The register as JSON: parties, fields, deadlines, documents
- The history of each contract, and the access log