Security

Security pack

For the people who review IMS Creator for their organisation: IT security, privacy, risk and procurement. It describes the service as it runs today, in plain terms, with enough detail to answer a vendor security assessment.

Version 1.0, November 2026. It covers hosted IMS Creator at app.imscreator.com in its current configuration: the service runs on a dedicated server in Australia, owned and run by IMS Creator, behind Cloudflare. A version for the cloud configuration (Microsoft Azure) will be published before any customer is moved there, and you will be told.

In brief

  • Your company's information is kept apart. Each company has its own databases and its own place in the file store. A test on every release signs in as one company and asks for every page with another company's names and ids, and must get nothing back.
  • Our administrators cannot read your content. Platform administration shows companies, sites, numbers of people and the service's health, never a document or what it says.
  • An authenticator code is asked for before the password, passwords are checked against known breaches, and every sign-in and change is in your own tamper-evident audit log.
  • Claude runs on your own Claude account, under your own agreement with Anthropic, AWS or Google. Your key is encrypted with your company's own key and used only for your work. What is sent, and what the provider keeps, is set out in full in Claude and your documents.
  • Drawings are not stored: they are processed in batches and deleted within 2 hours at most.
  • Encrypted everywhere: in transit (TLS 1.2 or later), on disk (LUKS2), in backups (encrypted before they leave the server).
  • Backups continuously archived (at most 15 minutes of changes at risk), kept off-site, restored as a test every quarter.
  • Incidents: affected customers are told within 72 hours of our becoming aware.

What is in the pack

Section What it covers
Architecture and data flows The parts of the service, where each runs, and how data moves between them
Your data What we keep, where, how it is encrypted, for how long, and how it is returned and deleted
Claude and your documents What is sent to Claude, when, on whose account, and what Anthropic, AWS or Google keep
Identity and access Signing in, roles, sessions, the audit log, and our own administrators' access
Application security How the software is built, tested and kept up to date; plugins; the ASVS assessment
Hosting and operations The server, the network, monitoring, patching, backups and recovery
Incident response What we do when something goes wrong, and when you hear from us
Service providers The companies whose services we use, and what each sees
Shared responsibility What we look after, and what your company looks after
Common questions Short answers to the questions security questionnaires ask most
ASVS level 2 self-assessment The OWASP Application Security Verification Standard, requirement by requirement
Reporting a vulnerability How to tell us about a security problem

The pack is also a single PDF, ims-creator-security-pack.pdf, to attach to your assessment.

What we do not claim

IMS Creator is a young service run by a small team. It has no independent certification yet (such as ISO/IEC 27001 or SOC 2). What it has: a design written for security from the start, an OWASP ASVS level 2 self-assessment, automated tests of company isolation on every release, and this pack. Before the service grows beyond its first customers, an independent penetration test will be done, then yearly, and its summary shared with customers. Where something here is planned rather than done, it says so.

Questions

Write to [email protected]. We answer security questionnaires, and can join a call with your security team.