SECURITY

Security at Assuraz

How Assuraz protects the records you and your employees keep in it: where it is hosted, how it is encrypted, how sign-in works and how each company's data is kept apart.

UK hosted

Application, database and files in Microsoft Azure UK data centres

Encrypted

HTTPS everywhere, with encryption at rest for the database and files

Two-factor

Multi-factor authentication on every account sign-in

Scanned

Every uploaded file checked for malware

Isolated

Each company’s data separated and checked on every request

Backed up

Automated database backups with point-in-time restore

This statement describes how Assuraz is built and hosted today. It is still being reviewed and should be checked before being relied on as a final statement.

Last updated: 23 October 2026

Hosting and data residency

Assuraz runs entirely on Microsoft Azure, and both the application and your data are hosted in Azure's UK data centres. Your records, uploaded files and backups are held in the UK. Azure's data centres are independently certified against ISO/IEC 27001 and other recognised standards, and physical security of the buildings and hardware is managed by Microsoft.

Application
Azure App Service (Linux, Node.js), UK region
Database
Azure SQL Database, UK region
Files and attachments
Azure Blob Storage, UK region
Email notifications
Azure Communication Services
Infrastructure access
Restricted to the people who operate and support the service

Encryption

Everything between your browser and Assuraz travels over HTTPS, and browsers are told to use nothing else. Data is also encrypted between the application and its database, and again where it is stored.

In transit
HTTPS (TLS) for every page, file and API request
HTTPS enforcement
HTTP Strict Transport Security (HSTS) for one year, including subdomains
Application to database
Encrypted connection to Azure SQL
Database at rest
Azure SQL encryption at rest (Transparent Data Encryption)
Files at rest
Azure Storage encryption at rest (AES-256)
Authenticator secrets
Encrypted in the database with AES-256-GCM

Sign-in, sessions and two-factor authentication

Every Assuraz account sign-in needs a password and a second, one-time code. A correct password on its own never signs anyone in. Base Camp, the employee portal, offers the same two-factor authentication for each employee to turn on.

Two-factor authentication
Required on every account sign-in: an authenticator app (TOTP, RFC 6238: 6 digits, 30-second codes) or a code sent by email
Email codes
Stored only as a hash, single use, expire after 10 minutes; requests are throttled
Recovery codes
Issued once when two-factor is set up, stored only as a hash, each usable once
Passwords
Never stored in readable form; hashed with bcrypt, a deliberately slow algorithm that resists brute-force attacks
Password reset
By an emailed link that expires after one hour; only a hash of the link is stored, and requests are throttled
Sessions
A random 256-bit session ID, held on the server and signed with HMAC-SHA256 in the cookie
Session cookie
HttpOnly (not readable by scripts), Secure (HTTPS only) and SameSite=Lax
Signing out
Deletes the session on the server, so the cookie cannot be reused

Access control and data separation

Each company's data is visible only to its own users, and to a consultancy where the company works with one through Assuraz. Every request to the server is checked against who is signed in and which company they are working in before any data is read or changed, so a user cannot reach another company's records by design, not just by convention.

Request checks
Every API request is authenticated, then limited to the company in view
Roles
Platform administrator, company user and consultant user, with company administrators managing their own users
Employees
Base Camp uses a separate sign-in and session, and shows employees only their own records and what their company publishes to them
Suspended accounts
A suspended company can sign in to read and export its records but cannot change them
Reception tablets
Each reception tablet must be paired once by a signed-in administrator, who enters a short code shown on the tablet; the tablet then holds its own key in a secure cookie. A copied link does nothing on an unpaired device. Each tablet can only sign people in and out at its reception, within limits on how often, and shows people on site by first name and initial only
Site sign-in
CDM site sign-in pages use their own long random link, which can be replaced at any time, and only allow signing in and out at that site

Application security

Assuraz sends modern browser security headers on every page, limiting what a page can load and how it can be embedded, to protect against cross-site scripting, clickjacking and content sniffing.

Content Security Policy
Enforced: scripts, styles, fonts and images only from Assuraz and a short list of named providers; no plugins; Assuraz pages cannot be framed by other sites
Clickjacking
X-Frame-Options: SAMEORIGIN
Content sniffing
X-Content-Type-Options: nosniff
Referrer
Referrer-Policy: strict-origin-when-cross-origin
Device features
Camera, microphone and location turned off by Permissions-Policy
Database queries
Parameterised throughout, protecting against SQL injection
Server details
Framework version headers removed

Files and malware scanning

Documents, certificates, safety data sheets, photos and other uploads are stored in Azure Blob Storage, which has Microsoft Defender for Storage malware scanning turned on, so every uploaded file is scanned. Files are served through Assuraz itself, after the same sign-in and company checks as everything else, rather than from public links.

Backups, continuity and retention

The database is backed up automatically and continuously by Azure, with the ability to restore it to a point in time. Backups stay in Azure and are managed as part of the hosting, so no company needs to set them up or remember to run them. When a company stops using Assuraz, its data is handled under our published retention stages; see the Privacy Statement.

Service providers

We use a small number of providers, each only for the job described.

Microsoft Azure (UK)
Hosting, database, file storage, malware scanning and email delivery
Stripe
Subscription payments. Card details go straight to Stripe and are never seen or stored by Assuraz
Anthropic
Optional AI drafting features (for example a policy or a construction phase plan). Only the text needed for that draft is sent, from our server, and only when a user asks for one

Reporting a concern

If you believe you have found a security issue or vulnerability in Assuraz, please tell us through your account administrator or the contact form, giving as much detail as you can. We will look into every report and keep you informed.

Assuraz
Privacy StatementSecurityCompliance Management System