Skip to content
Fire Safety ServicesDigital LogbookYour workspace →

Clear information, kept together

Customer data-processing terms

How we handle customer-controlled logbook information, including security, suppliers, assistance and return or deletion.

Version 2026-10-23.1 · Updated 23 October 2026

Explore the free demo →
Included in your contract documents. These terms apply where we process logbook personal data on a customer’s behalf. Reading this page does not start a purchase. Download the full processing terms.

On this page

  1. 1. Parties, scope and status
  2. 2. Processing schedule
  3. 3. Documented instructions and confidentiality
  4. 4. Security and resilience
  5. 5. Sub-processors and change notices
  6. 6. International processing
  7. 7. Rights, impact assessments and regulatory assistance
  8. 8. Personal-data breaches
  9. 9. Return, deletion and protected recovery copies
  10. 10. Information, audits and changes

1. Parties, scope and status

The processor is the legal operator identified in section 1 of the subscription terms. The customer is the organisation or person identified in the accepted order and authorised workspace details. These terms apply only to personal data we process on that customer’s behalf, including where the customer is itself an authorised processor.

The customer remains responsible for its own controller obligations, lawful instructions and authority. Our separate controller activities—account administration, security, statutory financial records and our own support administration—are explained in the privacy notice. Stripe also has independent controller responsibilities for parts of payment processing. Purely personal use does not automatically make an individual an organisational controller.

Where applicable, these processing terms form part of the accepted subscription contract and its retained document package. Mandatory data-protection law and applicable transfer clauses take precedence over conflicting wording. Statutory consumer rights are not restricted.

2. Processing schedule

Subject and purpose: operating a customer’s fire-safety logbook, including authorised checks, corrective actions, schedules, collaboration, evidence, exports, support and recovery. Processing includes collection, organisation, storage, retrieval, correction by appended history, authorised disclosure, backup and removal.

People: the customer’s authorised users, employees, responsible contacts, contractors and other people lawfully identified in premises records. Data: names, work contact details, account and membership identifiers, premises/contact information, check authorship and results, dates, notes, actions, evidence images/documents and their metadata. Account and technical data may also be processed for the separate controller purposes described above.

Duration: while the instructed workspace service continues, followed by authorised export/return, removal and the limited retention described below. Ending paid recording alone does not end the retained read/export workspace or instruct deletion. The service is not intended for special-category data, criminal-offence data, identity documents, payment-card data or children’s records; do not upload these without a separate lawful assessment and written agreement.

3. Documented instructions and confidentiality

The operator will process customer-controlled data only on documented lawful instructions, including instructions about transfers, unless UK law requires otherwise. In that case it will inform the customer before processing unless legally prohibited. Workspace configuration, authorised use and verified written support requests form part of the instructions. It will promptly tell the customer if an instruction appears to infringe applicable data-protection law and seek clarification rather than silently extending its use.

People permitted to handle customer data must be authorised for the task and bound by contractual or statutory confidentiality. Access is limited to what is needed to deliver, secure, support or recover the service. Customer records must not be sold, published as examples or reused for the operator’s marketing.

4. Security and resilience

The operator will maintain measures appropriate to the processing risk under Article 32: verified sign-in, organisation/premises and role checks, restricted server-side credentials, private evidence access, protected server mutations, audit/history controls and bounded uploads. Provider transport/storage safeguards and independently encrypted recovery copies support those measures.

The current design retains original checks with appended corrections, preserves evidence when actions are archived, separates the fictional demo, and tests exports and recovery. The operator must regularly review access, dependencies, configuration, backup outcomes and recovery tests. There is no claim of uninterrupted service, end-to-end encryption of every email, malware scanning of every upload or a third-party security certification. The customer must secure its users, devices and exported files.

5. Sub-processors and change notices

The customer gives general written authorisation to the service providers identified in this processing schedule: Neon/Databricks for database, authentication and primary evidence storage; Netlify for application hosting and processing; Cloudflare R2 for encrypted independent recovery; Resend for operational messages and delivery status; and IONOS where customer-controlled support content is handled in the support mailbox. Stripe is engaged for billing under its relevant processor and controller arrangements. Each provider receives only information needed for its function.

We use applicable written contracts imposing equivalent processor obligations and remain responsible to the customer for our sub-processors’ performance. We maintain the provider list, processing-location information and applicable safeguards and make relevant information available on request.

Before an intended new or replacement direct sub-processor handles affected data, we give at least 14 days’ written notice to the customer’s nominated contact, with an opportunity to object on reasonable data-protection grounds. We assess objections and seek a safe alternative. If unresolved, we arrange cessation of affected processing and return/removal, subject to statutory rights. Provider notices do not replace our direct customer notice.

6. International processing

Processing is not UK-only. The database project is in Frankfurt, independent backups use EU jurisdiction, Netlify functions are configured in Ohio and Resend states that its message/account data is stored in the US. Provider support and onward processing may involve further locations.

We address applicable restrictions before making a restricted transfer. Depending on the actual recipient, roles, covered data and onward processing, this uses applicable adequacy arrangements or contractual safeguards such as standard contractual clauses with the UK Addendum, with the required assessment and supplementary measures. A provider’s registry entry does not remove the need to check actual scope.

The customer may request the relevant mechanism and assessment summary, subject to necessary confidentiality. Transfers remain subject to documented lawful instructions and applicable transfer safeguards.

7. Rights, impact assessments and regulatory assistance

Taking account of the nature of processing and available information, the operator will provide appropriate technical and organisational assistance with access, correction, erasure, restriction, portability and objections; security obligations; impact assessments; and prior consultation with the supervisory authority where required.

A request about customer-controlled logbook information will be promptly forwarded to the relevant customer unless law requires a different response. The operator will not independently disclose another person’s workspace merely because a request is received. Identity, authority and scope must be checked proportionately, and assistance must not obstruct applicable deadlines. Requests concerning the operator’s own controller records will be handled separately.

8. Personal-data breaches

The operator will notify the affected customer without undue delay after becoming aware of a personal-data breach affecting data processed on its behalf. It will provide available details about the nature and likely effects, affected categories and approximate numbers where known, contact route, and containment/remediation measures, with further updates as facts become available.

It will preserve necessary evidence, investigate, mitigate and assist the customer with notifications and other legal duties. An incomplete investigation is not a reason to withhold an initial notification. The controller determines its own reporting obligations; this does not postpone any separate duty the operator has as a controller. Contact the support address in the subscription terms for a suspected incident; never send passwords or full payment details.

9. Return, deletion and protected recovery copies

When the instructed processing ends, the customer may choose return or deletion of the data processed on its behalf. Available authorised exports support return. The operator will arrange secure removal of remaining copies unless law requires their retention, explaining the scope, basis and period of any required hold. Financial-record retention is not a blanket reason to retain every premises document.

The agreed review normally includes a seven-day cancellation safeguard, subject to statutory deadlines and urgent lawful requests. Billing-linked closure currently needs separate financial review. It must not be represented as completed merely because a subscription is cancelled or an action archived.

Independent backups normally expire after 31 days and are protected against deletion for their first 30 days. Pending expiry, removed data is kept beyond ordinary use and recovery must respect the deletion-suppression ledger. That separately encrypted ledger contains minimal removal identifiers, not names, emails or evidence, and is reviewed for continuing recovery necessity. Removing a live record does not promise immediate destruction of every protected backup. The operator will confirm completed removal or explain any remaining restriction.

10. Information, audits and changes

We make information necessary to demonstrate the applicable Article 28 obligations available and allow and contribute to audits and inspections by the customer or its authorised independent auditor. Reasonable confidentiality, scope, notice and security arrangements protect other customers but do not remove lawful audit rights or prevent urgent or regulatory inspections.

Material instructions and processing changes are documented. A later website edit does not retrospectively replace the version included in the customer’s retained contract package. Future changes require appropriate notice and any agreement required by law.

TermsPrivacyCookiesProcessing termsEmail choices
Fire Safety Services Digital Logbook