Security pack
Architecture and data flows
IMS Creator is a web application: people use it in a browser (current Chrome, Edge, Safari or Firefox), and nothing is installed on your computers.
The parts
- Cloudflare receives every request: it answers for
app.imscreator.com, ends TLS, and applies its firewall, bot protection and rate limits. It passes requests to the server through a tunnel the server opens outwards: the server has no port open to the internet. - The application serves the pages and the API. Every request is checked for a valid session, the person's company, site and role before anything is read, in one place for the whole application.
- Workers do the longer jobs: writing documents with Claude, reading drawings, building reports.
- Databases (PostgreSQL): a directory of companies and sign-ins, then one database for each company and one for each of its sites. No query spans two companies' databases.
- File store (S3-compatible, private): uploaded documents, templates, report images and thumbnails, each company in its own place.
- Backups go encrypted to a separate backup server, which keeps an off-site copy.
How information moves
| Flow | From | To | Protection |
|---|---|---|---|
| Using the app | Your browser | Cloudflare, then the server | TLS 1.2 or later; HSTS; the tunnel is encrypted |
| Drafting a document | The server | Your Claude provider | TLS; your own credentials; see Claude and your documents |
| Reading drawings | A folder on your computer | The server, then back to your folder | TLS; files deleted from the server within 2 hours |
| Email (invitations, resets, notices) | The server | Postmark, then the recipient | TLS; links are single-use and expire |
| Backups | The server | The backup server, then off-site | Encrypted on the server before they leave it |
Cloudflare ends TLS at its edge, so requests pass through Cloudflare's network decrypted in transit, as with any service behind a content delivery network. Responses from the API are not cached there.
Where it runs
Everything that holds your information runs in Australia: the server, its backup server and the off-site copy. Your Claude processing runs wherever your Claude provider and region are (see Claude and your documents).
The cloud configuration (Microsoft Azure, with a region per customer) will be described in its own version of this pack.