Privacy policy

Blaze Squad Ltd · last updated 15 October 2026

This policy covers this website and every Blaze Squad Ltd app: Fire Suite Pro (the assessor's suite, including FRA Pro, Door Pro, CS Pro, Strategy Pro, PPM Pro, FIV Pro and HRB Pro), Fire Passport (the Responsible Person's companion app), Plan Stack, Callbook Pro and The Nutriplan. Blaze Squad Ltd operates the cloud services described below; who is responsible for what is set out under “Your rights”.

This website

This site sets no cookies and runs no analytics. If you email us, we hold your correspondence to answer it.

• Ask a surveyor. When you send a question through the box on this site, we hold your name, email address, the role you choose, the building type if you give it, your question, the page you sent it from, and a one-way scrambled form of your connection address (used only to stop the box being flooded). The question is emailed to Mark Blooman so that he can answer it, and the copy we hold makes sure none is lost. Ask us at the address below and we will delete it.
• Signing pages. Where a surveyor using HRB Pro sends you a link to blazesquad.co.uk/sign to confirm an instruction, see “Signing an instruction” under Fire Suite Pro.

Fire Suite Pro (assessor app)

• Signing in. Assessors sign in with an email one-time code or a passkey. We hold the account email address, organisation membership and passkey public keys — never a password.
• Assessment data is stored in our cloud and on the device. While an assessor is signed in, buildings, assessments, findings, photographs, floor plans, signatures and published reports are synchronised over an encrypted connection to our cloud database and file store, where they are shared with the other devices and members of the assessor's organisation. The device keeps a working copy so assessments continue offline. Signed out, data stays on the device only.
• Held whether or not the building uses Fire Passport. An assessment is stored in our cloud because the assessor is signed in, not because the building has any relationship with us. Where the building's Responsible Person has never used Fire Passport, and where its owner or manager holds no account with us at all, the assessment, its findings, photographs and signatures are still held under the assessor's organisation. Referring an assessment to a Fire Passport record is a separate, deliberate act that changes who can see it; it does not change whether it is stored.
• People named or shown in an assessment. An assessment may record the names and contact details of responsible persons, managing agents, contractors and occupants, and photographs taken in and around a building may show people or their property. The assessor or firm carrying out the assessment decides what is recorded and is the controller for it; we hold it on their behalf. Requests about that content are directed to them — see “Your rights”.
• How long assessment data is kept. Each published report and the data behind it is held for a set period from the date it was published, after which it is deleted:

  Report	Held for	Where the building is on Fire Passport
  Fire risk assessment	15 months	30 months
  Fire door survey	15 months	30 months
  Staircase survey	63 months	126 months
  Height and storey assessment (HRB Pro)	6 years	6 years
  Any other published report	15 months	30 months

  The periods double where the assessment was instructed through, or returned to, a Fire Passport building record, because the record is then part of a building's continuing history rather than a single engagement.
• Work that is never published. An assessment that is never published is held for a maximum of twelve months from the last time it was worked on, then deleted. Nothing unpublished is kept indefinitely.
• You are warned before anything is deleted. We notify the assessor's organisation ahead of a deletion date so that anything wanted for their own records can be downloaded first. The report remains the assessor's to keep; what expires is our copy of it.
• Renewing a report does not extend the one it replaces. When a report is renewed, the new version is held for its own full period from its own publication date. The version it supersedes keeps the period it already had and is deleted when that expires, under the same rules. Renewal therefore keeps the current assessment available; it does not preserve the whole history indefinitely.
• What deletion does not reach. Two things survive. The record that a publication took place — its reference, time and charge — is kept for billing integrity. And any copy already delivered elsewhere, such as a report emailed to a client or an assessment sent into a Fire Passport record, has left our control and cannot be recalled by deleting ours. An assessor or firm may also ask us to remove their hosted data earlier, on verified request.
• Hosted questionnaire forms. Where an assessor sends a building manager a hosted pre-inspection questionnaire, the answers submitted are transmitted over an encrypted connection through our cloud infrastructure to the assessor's app and are used only to populate that assessment.
• Signing an instruction (HRB Pro). A surveyor may send a client a link to a signing page on this site. The page holds, temporarily, the surveyor's firm name, the report reference, the property, the client's name, the instruction and, once signed, the client's answers to its four questions, their acknowledgement that they received the surveyor's briefing note, the signer's typed name, their capacity, the drawn signature and the time of signing. It holds no email address and no connection address. The surveyor sends the link themselves; we email nothing. The link itself is deleted once the surveyor's app collects the signature, and an unsigned link no more than 60 days after it was created. A signed instruction — whether signed through the link or in person on the surveyor's device — is kept on our server for six years from signing, with the briefing note as the surveyor sent it and each report they issue from it, and then deleted. The surveyor's firm can read that copy; nobody can change or remove it before the six years are up.
• Publishing and sending reports. When a report is published, a record of the publication (reference, time and charge) is kept for billing integrity, and the published report is stored with the organisation's assessment data. Where the assessor emails a report to a client from the app, the email is sent through our infrastructure and a record of the send is kept.

Fire Passport (Responsible Person app)

• Signing in. Responsible Persons sign in with an email one-time code or a passkey, with one-time recovery codes for account recovery. We hold the account email address, organisation membership and passkey public keys — never a password.
• Building records are stored in our cloud. Signed out, building records save only on your device. Once you sign in, your records — including any personal emergency evacuation plan details you enter — are stored in our cloud database under your organisation, so your portfolio follows you across devices and is shared with colleagues in the same organisation. Records already on the device are copied to your account when you first sign in.
• Sending records and notices. Records and fire-safety notices sent from the app are delivered through our cloud infrastructure, and a delivery record is kept — including when the recipient first views and acknowledges it — so both sides hold an audit trail. A few actions (such as handover invitations) instead open a pre-addressed email in your own mail app.
• Invites. An assessor's invite contains the building reference and the assessor's contact details, used to route your record to them. Organisation invites carry the invitee's email address and role.
• Tender documents are deleted after three months. Returns to a tender are held sealed until the return date, then released simultaneously and sent to the issuer, the Responsible Person and anyone else listed on the tender, with every document in one zip file. A competing tenderer never receives another tenderer's return. The uploaded documents — specifications, priced bills, method statements, certificates — stay on our servers for three months from the release date, and the release email states that date. After it, those files are deleted and the record of the deletion is kept. The tender record itself — who was invited, who returned, what they bid and who won — is retained in the Management Log as the Responsible Person's evidence that a proper procurement took place.

Plan Stack

• Without a Fire Passport account, nothing leaves your device. The plans you import, your projects and their versions are kept in your own web browser's storage. Saving a project writes a file to your own device.
• With a Fire Passport account. If you sign in and save a project to one of your buildings, the project and the stacked plans are stored with that building's Fire Passport documents, where everyone who has that building in Fire Passport can open them. They are then held and controlled as the rest of that building record is.

Callbook Pro

Callbook Pro has its own privacy notice, which says what it holds for businesses and for their customers, where it is stored, and how long it is kept: callbook.blazesquad.co.uk/privacy. In short: Blaze Squad Ltd is responsible for your Callbook Pro account, and each business you book with is responsible for the details you give it. Records are stored with Supabase in London. Booking emails go from the business's own email account, not from us.

The Nutriplan

The Nutriplan Histamine & Carbohydrate Index is a reference page that runs in your browser. It has no account, collects no personal data, sets no cookies and runs no analytics. Nothing you search for is sent to us. It is hosted for us by Netlify.

How data is hosted

Our cloud database and file store are operated for us by Supabase; this website, Plan Stack and Callbook Pro's web app are served by Cloudflare, and The Nutriplan by Netlify. Emails we send, such as sign-in codes, go through Resend. Data is encrypted in transit. Hosted data is kept while the account or organisation it belongs to remains active, and removed on verified request (see “Your rights”).

What we do not do

• No sale or sharing of personal data with third parties for marketing.
• No advertising, profiling or cross-app tracking in any Blaze Squad app.

Your rights

Under UK GDPR you may request access to, correction of, or deletion of personal data, and you may complain to the Information Commissioner's Office (ico.org.uk). For the content of a fire risk assessment, the assessor or firm that carried it out is the controller, and Blaze Squad Ltd hosts that content as their processor. For a Fire Passport building record (including any evacuation plan details), the Responsible Person or their organisation is the controller, and we host it as their processor. Blaze Squad Ltd is the controller for accounts, billing and publication records, and for this website. Requests concerning the content of an assessment should be directed to the assessor who carried it out; requests about anything else — including deletion of hosted data — come to us at the address below.

Contact

Blaze Squad Ltd, Cypress Lodge, Station Road, Potter Heigham, Great Yarmouth, England, NR29 5HX.
Email: mb@blazesquad.co.uk

Changes

We will post any changes to this policy on this page with an updated date above.