Security
Last updated: 16 November 2026
Your compliance records are the product. An auditor may one day ask for any job sheet, lab report or service report. This page explains how we protect them, in plain terms.
Where your data lives
BlueWave's databases and file storage run on Google Cloud in London (the europe-west2 region). Uploaded files, such as photos and lab reports, sit in private storage and open through links that expire after 15 minutes.
Some services process data outside the UK, or may do so. Payments for your BlueWave subscription and the email we send both go through companies in the United States. Address lookup goes through another company, and where it processes data is not confirmed. Our privacy policy names all three. Where the AI assistant is switched on, what it sends can leave the UK and the EEA too.
Encryption
All traffic between you and BlueWave is encrypted in transit with TLS. Requests over plain HTTP are redirected to HTTPS, and an HSTS header tells browsers to use HTTPS only. At rest, the databases and files sit on Google Cloud disks and storage buckets, which are encrypted by default.
Separation between businesses
Every record a business creates belongs to that business alone. Every query the office app and the engineer app make for a business's records is filtered by that business at the data layer, in the database and in the search index. That filter is what keeps one business's customers, jobs and job sheets out of another's view. Security questionnaires call this tenant isolation.
The separation is logical. Businesses share one database and one search index, and the filter keeps their records apart. BlueWave's own staff app reads across businesses, as the next section explains.
Access and sign-in
Sign-in runs through an identity provider that we host ourselves, and it issues short-lived, signed tokens. People sign in with an email address and a password. Anyone on your team can turn on two-factor sign-in with an authenticator app.
What a person can do depends on the roles they hold: office staff, engineer and user manager. Of a business's jobs and bookings, a person who holds only the engineer role sees the ones they lead or crew.
BlueWave staff use a separate app with a separate login. In it they can read your records to support you. The only things it lets them change are your team's accounts, your BlueWave billing and two switches, which turn the feedback button and the AI assistant on or off for your business. When they move a person out of a business, that also takes the person off their upcoming work there. It can leave a job without a lead engineer or crew. On a recurring job it can call off unstarted bookings: all of them if the person led the job, and otherwise the ones the person was due to lead.
When we need to see what you see, a support view shows your screen as one of your users. It lasts one hour and can't change anything.
Change history
Every save that changes a customer, site, asset, job, booking or contract records who made it, when and what changed, and BlueWave staff can read that field-by-field log. In the office app, a job's history lists what happened to the job and its bookings, and an asset's page lists its bookings and their job sheets.
Backups and recovery
Customer data is backed up automatically.
The AI assistant
The office app has an AI assistant that answers questions about your own jobs, bookings, assets and invoices. The AI assistant is switched off for every business until BlueWave switches it on for that business. Signing up does not switch it on. Only BlueWave staff can turn that switch, on or off, and it covers the whole business.
What it can read
It looks records up with the sign-in of the person asking, so every record it finds is one that person can open in the office app. It runs as its own service, apart from the rest of BlueWave. That service holds no database password. Every lookup goes through the same API the office app uses.
Its lookups cover jobs, bookings, assets, sites, customers, engineers, blocked time, contracts and invoices, and the figures on the office dashboard. Each lookup passes on a fixed list of fields.
It gets facts about a booking's job sheet, such as each form's name, who submitted it and when, and how many readings are out of range. Text that someone typed into a name, a description, instructions, a reason or a note goes as typed, so a phone number or a door code written in a job note is sent as written.
What we keep
BlueWave doesn't keep your chats. A chat lives in your browser and clears when you reload the page. Our logs record who asked, which lookups ran, which company answered, how long the answer took and what it cost. Our code does not write the question or the answer to them. When one of the companies that handle a question returns an error, we log the first 200 characters of its error message. A lookup that fails can also leave the words it searched for in our error log. BlueWave itself does not use your data to train any AI model.
Reporting a vulnerability
If you find a security problem, tell us at security@usebluewave.com and give us a reasonable chance to fix it before disclosing. Good-faith research is welcome; the boundaries are in our acceptable use policy. We'll acknowledge reports promptly and keep you informed.
Data protection
BlueWave's data protection setup is written for UK GDPR. It is a data processing agreement and a privacy policy, with its list of companies under "Who we share it with". This site runs no visitor analytics at all, which leaves us nothing to leak about the people who read this page.
Questions?
If security decides it for you, ask us the hard questions directly: security@usebluewave.com. Or book a demo and bring your security questionnaire along. If you buy for a larger organisation, the page for larger organisations sets out how BlueWave handles sign-in, hosting, staff access, change history and exit.