Security pack

Your data

Version 1.0, November 2026 · The whole pack · PDF

What we keep, and where

Information Where it is kept Encrypted Kept for
Management system documents, registers, plans, approvals and their history Your company's and your sites' databases Disk (LUKS2) While you subscribe
Uploaded documents (standards, templates, reports, register attachments) Your company's place in the file store Disk; sensitive files with your company's key Until removed, or you leave
Drawing register: each drawing's fingerprint, name, title block, tags, links, summary, search text, small page images Your site's database and file store Disk While you subscribe
The drawings themselves Only while a batch is processed, on a temporary encrypted area not backed up Disk Deleted when you collect the results, or after 2 hours at most
Your Claude connection (API key, or cloud credentials) Your company's or site's settings Your company's or site's own key, then disk Until replaced or removed
People: name, email, role, sign-in history Your company's database (the email also in the directory, to know your company at sign-in) Disk While they have an account
Password hashes, authenticator secrets, recovery codes Your company's database Argon2id; authenticator secrets with your company's key; recovery codes hashed While they have an account
Audit log of sign-ins and changes Your company's database, hash-chained Disk While you subscribe; exportable at any time
Support requests and their replies The platform's directory database Disk While you subscribe
The service's own logs (no document content) The server Disk 90 days
Backups of all the above Backup server and an off-site copy Encrypted before leaving the server 30 daily, 12 monthly

Everything above is held in Australia.

Kept apart from other companies

  • Each company has its own databases (one for the company, one for each site) and its own place in the file store. The application chooses the database from the signed-in person's session, never from anything in the request, so a request cannot reach into another company.
  • On every release, an automated test signs in as one company and asks for every page and every API call with another company's names and ids: the release is stopped if anything comes back.
  • People belong to one company, and sign in with an address at one of the email domains your company has approved and verified (a DNS record, or checked by us by hand).

Encryption

  • In transit: TLS 1.2 or later from the browser to Cloudflare, with HSTS; an encrypted tunnel from Cloudflare to the server; TLS to Claude providers and to Postmark.
  • At rest: the server's data disk is encrypted (LUKS2). Secrets that are yours, such as your Claude credentials and your people's authenticator secrets, are also sealed with a key of your company's own (AES, through the Fernet scheme), which can be rotated.
  • Backups: encrypted on the server, before they leave it, with a key kept off the server.

What our administrators can see

Platform administration (our console) shows: companies and their sites, how many people, subscription and billing details, support requests you send us, and the service's health (counts of queued and failed jobs, sign-in failures, sessions). It never shows a document, a register entry, a file name, a person's documents, or what a job is about, and it cannot open your sites. Our administrators sign in with an authenticator, and from the internet only through Cloudflare Access, as themselves.

Running the server, its administrators could in principle reach the databases directly. That access is limited to the owner, through a private network with keys only, and is used only to operate the service: to restore a backup at your request, or to deal with an incident.

Your data, returned and deleted

  • At any time: documents download as Word, registers as Excel, and your company admins can export the audit log.
  • On request, and when you leave: a full export of your company's databases (in PostgreSQL's open format), its files and its settings, delivered encrypted.
  • When you leave: after the period agreed with you (30 days unless agreed otherwise), your company's databases, its files and its keys are deleted, and its entries in the directory removed. Copies in backups expire with the normal retention (12 months at most); destroying your company's key makes the secrets in those copies unreadable. We confirm the deletion in writing, with the date the last backup copy expires.

Personal information

IMS Creator holds a little personal information about your people (names, work email addresses, roles, sign-in history), and whatever your documents themselves hold. We handle it under the Australian Privacy Principles, as set out in our privacy notice. For the documents you write in IMS Creator, your company decides what goes in them; we process them only to provide the service.