Fire Suite

Data Processing Agreement

Version 1.9 · Last updated: 15 November 2026

When you use Fire Suite to manage your staff, you decide what happens to their personal data and we act on your instructions. This document is the agreement that says so, and sets out what we are obliged to do. It is required by Article 28 of the UK GDPR, and it forms part of our Terms of Service.

In short

1. Who is who

This agreement is between SafeerTec Ltd, a company registered in England & Wales ("we", "us", "the Processor"), and the business that holds a Fire Suite account ("you", "the Customer", "the Controller").

For personal data about your staff — their hours, pay, documents and so on — you are the controller and we are your processor. You decide what is collected and why; we act on your instructions.

For personal data about your own account — the name and email of whoever signs up, and your billing records — we are the controller, because we decide to keep those in order to run our business. Our Privacy Policy covers that part.

2. How this agreement comes into force

It is incorporated into the Terms of Service. By creating a Fire Suite account you accept it, and no signature is needed. If your organisation requires a signed counterpart, email info@safeertec.com and we will sign one.

It lasts as long as your account does, plus any period in which we still hold your data under clause 9.

3. What we are instructed to do

We process personal data only on your documented instructions. Your instructions are: this agreement, the Terms of Service, and the ordinary use you make of the product's features. We will not process your staff's personal data for any other purpose.

In particular, and so it is written down rather than assumed:

If we are ever required by law to process your data differently — by a court order, for example — we will tell you before doing so unless the law forbids us from telling you.

4. Details of the processing

The subject matter, duration, nature, purpose, types of personal data and categories of data subject are set out in Annex 1, as Article 28(3) requires.

5. Confidentiality

Everyone we allow to access your data is bound to keep it confidential. Today that is a small, named group of people within SafeerTec Ltd, and access is limited to those who need it to support you or to keep the service running.

6. Security

We take the technical and organisational measures required by Article 32. The measures actually in place are listed in Annex 2, which describes what we do rather than what is typical — so you can judge it, and so you can see where the limits are.

7. Sub-processors

You give us general authorisation to use the sub-processors listed in Annex 3. Each is bound by terms that are no less protective than these, and we remain responsible to you for what they do.

If we intend to add or replace one, we will give you at least 30 days' notice by email to your account's registered address. If you reasonably object on data protection grounds within that period, we will work with you to find an alternative; if we cannot, you may terminate the affected part of the service and we will refund any fees covering the period after termination.

8. Your obligations, and helping you with yours

You are responsible for having a lawful basis for the data you put into Fire Suite, for telling your staff what you are doing with it, and for the accuracy of what you enter.

We will help you meet yours, taking into account the nature of the processing and the information available to us:

9. Deletion and return

On request at any time, and in any case when your account ends, we will delete your personal data or return it to you, at your choice.

We would rather write the paragraph above than the shorter one that says everything disappears in thirty days. Both the write-protection rule and the append-only backups are there to stop your records being destroyed, and a contract that promised instant erasure would be promising to weaken them. If that trade-off does not suit your organisation, tell us before you sign rather than after.

10. Personal data breaches

If we become aware of a personal data breach affecting your data, we will notify you without undue delay and in any event within 48 hours, by email to your account's registered address and by telephone if we hold a number for you.

You have 72 hours to decide whether to tell the ICO, so our notification is meant to leave you time to decide rather than to be the last word. It will describe what happened, which data and roughly how many people are affected, what we think the consequences are, and what we are doing about it. Where we do not yet know something, we will say so and follow up rather than delay the first notification.

We will not notify your staff or any regulator on your behalf unless you ask us to in writing — that is the controller's decision, not ours.

11. Audit and information

We will make available the information you reasonably need to show that we are meeting these obligations, and will respond to a reasonable written due-diligence questionnaire within 30 days.

You may audit us, or appoint an independent auditor to do so, once in any 12-month period on 30 days' written notice, and additionally after a breach affecting your data. Audits take place in business hours, must not unreasonably disrupt the service, and the auditor must be bound by confidentiality and must not be a competitor of ours. We do not hold ISO 27001, SOC 2 or any equivalent certification, and we would rather say so here than let a certification logo answer the question for us.

12. International transfers

Your data is stored and processed in Germany and, for backups, in the European Union. Transfers from the UK to the EEA are permitted under the UK's adequacy regulations.

Some sub-processors in Annex 3 are United States companies, identified as such in the table together with exactly what each one receives. Where a transfer to a country without UK adequacy is involved, it is made under the UK International Data Transfer Addendum to the European Commission's Standard Contractual Clauses, or another lawful transfer mechanism, together with the additional safeguards noted in Annex 3.

13. Liability and precedence

The limitations and exclusions of liability in the Terms of Service apply to this agreement, and the total liability of either party under both taken together does not exceed the cap stated there.

If this agreement and the Terms of Service conflict on anything to do with the processing of personal data, this agreement wins.

14. Governing law

This agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction. "UK GDPR", "controller", "processor", "personal data", "personal data breach" and "processing" have the meanings given in the UK GDPR and the Data Protection Act 2018.

15. Changes

We may update this agreement where the law changes or the service does. We will give you at least 30 days' notice of any change that materially reduces your protection, by email to your account's registered address. The version and date at the top of this page tell you which version you are reading.


Annex 1 — Details of the processing

Subject matter and duration

Providing the Fire Suite applications to you, for as long as you hold an account, plus the deletion periods in clause 9.

Nature and purpose

Hosting, storing, organising, displaying, analysing and backing up the records you create, so that you can run staff rotas, record attendance, calculate pay, keep right-to-work and certification records, manage stock and suppliers, reconcile money, and run screens in your premises.

Categories of data subject

Types of personal data

CategoryWhat it includesWhich app
Identity & contactName, email address, telephone number, address where you record oneFireAttend
EmploymentJob role, start date, contracted hours, hourly rate, pay method, availability, rotaFireAttend
AttendanceClock-in and clock-out times, hours worked, variances against the rota, edits and who made themFireAttend
PayGross pay per week, payslips, frozen pay weeks, wage payments matched against your bank recordsFireAttend
Right-to-work and certification documentsImages or PDFs of passports, BRPs, visas, share-code checks, settled-status letters and food-hygiene certificates, with their expiry dates. These may reveal nationality or immigration status.FireAttend
LocationA check, at the moment of clocking in or out, of whether the person's device is at the workplace. Foreground only — there is no background tracking, and no location history is kept beyond that check.FireAttend
Account & securityUsername, hashed password, two-factor settings, login activity, an append-only audit log of changes made in the dashboardPlatform
Supplier and order recordsSupplier invoices and delivery notes, which may contain names of individuals at your suppliersFirePantry, FireBridge
Delivery customersFor each delivery, the customer's first name, phone number, delivery address and your note for the driver. These are encrypted, shown to the driver only once they accept the delivery, and deleted 24 hours after it is delivered or cancelled. Your company also keeps an encrypted customer record: first name, phone, latest delivery address, which channels they ordered through and when, and a consent record that stays empty until the customer gives consent themselves. Never a surname or email address.FireDrive

On FireDrive customer records. They are your company's alone: never shown to another restaurant on FireDrive, or to FireDrive itself. You can erase any one of them at a customer's request (FireDrive → Deliveries).

Special category data. Fire Suite has no field for health, biometric, racial or ethnic, religious, political or trade-union data, and we ask you not to put any in. A right-to-work document can nevertheless reveal nationality or immigration status, so those documents are treated as the most sensitive thing in the system: they are stored with a two-year deletion lock against accidental loss, and they are never shown on any public page or screen.

Annex 2 — Technical and organisational measures

What is actually in place as at 15 October 2026. Where there is a limit, it is stated rather than left out.

Access control

Encryption

Resilience and backups

Organisational

What we do not have. We hold no ISO 27001, SOC 2 or Cyber Essentials certification. We are a small company and there is no 24-hour staffed operations desk. We would rather you knew that before signing than after an incident.

Annex 3 — Sub-processors

Everyone other than us who may handle your data, what they do, and where they are. This list is current as at 15 November 2026; clause 7 governs changes.

Sub-processorWhat it doesWhat it seesWhere
netcup GmbH Server hosting. The application and its database run here. Everything, as the host of the system. Germany
Cloudflare, Inc. Storage of uploaded documents and images (R2), DNS, and traffic in front of the site. Uploaded files, including right-to-work documents, and request metadata. United States (company); EU storage region
Anthropic PBC Reads dates off a photographed document, and reads supplier invoices, so a person confirms a date instead of typing it. If a shop switches on the rota assistant, also suggests the rota changes a manager asks for. If a restaurant switches on FireDrive's slip scanner, also reads a photographed delivery slip, so staff check a delivery's details instead of typing them. If a shop switches on the VAT pack file sorter, also says what a file added to the VAT pack is — which bank or card statement and which period, or a receipt — so it goes in the right section. Every result is proposed for a human to review, never filed or applied automatically, except that the file sorter places each file in the section it names, marked as sorted by AI, for the owner to check and move. Images or PDFs of right-to-work and certification documents at the moment they are scanned, and supplier invoices. Only if a shop switches on the rota assistant: that shop's rota for the week being edited — staff names, roles, scheduling priority, availability and shift times — at the moment a manager asks it something. Only if a restaurant switches on the FireDrive slip scanner: the photo of a delivery slip, which shows the customer's name, delivery address and phone number and usually what they ordered, at the moment somebody scans it. Only if a shop switches on the VAT pack file sorter: a file the owner adds to the VAT pack that Fire Suite's own readers cannot place — typically a bank or card statement, or a photo of a receipt — at the moment it is added. A statement shows the account's transactions, which can include wages paid to staff by name. Never your staff's pay records, contact details or attendance data beyond what such a statement shows. United States
Google LLC (Google Maps Platform) Turn-by-turn directions for FireDrive drivers inside the FireDrive app, finding a delivery address on the map, and suggesting addresses while restaurant staff or FireDrive HQ type one into FireDrive. For a delivery a FireDrive driver navigates to: the delivery address and its map point, and the driver's location while they navigate. While staff type an address into FireDrive: what they type, and the address they choose. Never the customer's name or phone number. United States
Twilio Connects calls between a FireDrive driver and your customer, where calling is switched on for your restaurant. The customer's phone number, the driver's where a call goes to their phone, and what is said on the call. Calls are not recorded. Twilio keeps its own record of each call, including those numbers. We delete each call's record from our Twilio account after the delivery: 24 hours after by default, and never more than 30 days after. Twilio may keep copies of its own beyond that. United States
Stripe, Inc. Takes your subscription payment. Your billing contact and payment details. No staff data. United States / Ireland
Resend Sends account emails, payslip emails and alerts. Recipient email addresses and the content of those messages. United States
Functional Software, Inc. (Sentry) Tells us when something in Fire Suite goes wrong, so we can fix a fault before you have to report it. A report of each fault: what failed and where in our code, when, and the shop and page or background task it happened in. The wording of a fault can include a member of staff's name or an internal reference. Never the content of what was sent to us, cookies, passwords or sign-in links: those are removed on our server before a report leaves it. United States (company); EU storage region
Backblaze, Inc. Holds the encrypted off-site backup copy. Nothing readable. The copy is encrypted before it leaves our server and Backblaze does not hold the key. European Union
Render and Neon A dormant standby copy of the application and database, kept so the service can be restored quickly. Not used to serve the live service. A database copy. No uploaded documents. European Union

On the document scanner. It is the one place your staff's most sensitive documents leave our own servers, so it gets its own paragraph rather than a row in a table. A document is sent only at the moment somebody scans it, only to extract dates, and Anthropic's API terms provide that inputs submitted through it are not used to train their models. If you would rather your documents were never sent to it, tell us and we will turn the feature off for your account — your managers then type the expiry dates in by hand, and nothing else changes.

On the rota assistant. It is off for every shop until you switch it on in Store settings, and switching it on or off is recorded in your activity log. While it is on, the week's rota for that shop is sent only when a manager asks it something, and it only ever proposes changes: nothing on the rota changes until a manager approves it. Switch it off and nothing more is sent.

On the slip scanner. It is off for every restaurant until you switch it on (FireDrive → Deliveries), and switching it on or off is recorded in your activity log. While it is on, a slip's photo is sent only at the moment somebody scans one. What it reads is filled into the delivery form for a person to check and correct before the delivery is added. We do not keep the photo. Switch it off and nothing more is sent.

On the VAT pack file sorter. It is off for every shop until you switch it on (FireBridge → VAT pack, or Company → AI), and switching it on or off is recorded in your activity log. While it is on, a file is sent only when the owner adds it to the VAT pack and Fire Suite cannot tell from its name or text what it is. The answer says only what kind of document it is, who issued it, the last four digits of the account and the period it covers; no transaction or amount is taken from it. The file itself is kept in the VAT pack, as every added file is. Switch it off and nothing more is sent.

Contact

Questions about this agreement, a data subject request, a due-diligence questionnaire or a signed counterpart: info@safeertec.com.

You can also complain to the UK Information Commissioner's Office at ico.org.uk.