Legal
Privacy policy
What personal data Fortress QMS collects, why, who handles it and the rights you have.
Last updated 17 November 2026
Draft. This text is awaiting legal review and may change before it takes effect.
This policy explains how we handle personal data. It covers visitors to our website, people who have an account on the Service, and the personal data that organisations put into it.
Who is responsible
For account and website data (see below) we are the controller. For Customer Data, meaning the records and files an organisation enters, including details of its own people, the organisation is the controller and we are its processor. If you are a colleague of someone who uses Fortress and want to exercise your rights over Customer Data, please ask your organisation first.
What we collect
| Data | Why | Lawful basis |
|---|---|---|
| Name, work email, password (stored only as a protected hash), terms accepted and when | To create and run your account and keep it secure | Contract |
| Sign-in and security events: sign-in time, two-factor and single sign-on use, IP address for network restrictions and blocked attempts | To keep accounts and organisations safe and to enforce settings your administrator chose | Legitimate interests, and contract |
| Organisation, role, seat, site and department membership | To give you the right access | Contract |
| Billing: subscription, seats, invoices and a payment reference. Card details are held by Stripe, not us | To take payment and meet tax obligations | Contract, legal obligation |
| Customer Data: the quality records, files and people details an organisation enters | To provide the Service to that organisation | On the organisation’s instructions (we are the processor) |
| Audit trail of changes, with who made them and when | To give your organisation a reliable record | Contract, legitimate interests |
| Emails you send us, and our emails to you about the Service, with delivery status | To answer you and to deliver notifications and invitations | Legitimate interests, contract |
| Technical logs: request records, errors, performance | To run, secure and fix the Service | Legitimate interests |
We do not run advertising or analytics trackers on this website or in the product, and we do not sell personal data.
Who we share it with
We use a small number of service providers (processors) who handle data on our instructions:
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, sign-in and file storage | London, UK |
| Vercel | Hosting of the application and the API | API in London; website files served from a global network |
| Stripe | Payments and billing | Global, with its own safeguards |
| Cloudflare | Domain name service | Global |
| Resend | Sending emails such as notifications and invitations, when switched on | Global |
We may also share data where the law requires it, to protect rights and safety, or in connection with a sale of the business, with notice to you.
International transfers
Customer Data is stored in the UK. Some of our providers may process limited data outside the UK. Where they do we rely on adequacy regulations or appropriate safeguards such as the UK international data transfer agreement or addendum.
How long we keep it
- Account data: while your account is active, and for a limited period afterwards for legal and security reasons. Periods to be confirmed
- Customer Data: while your organisation subscribes, then for a period to allow export before deletion. Period to be confirmed
- Billing records: as long as tax law requires.
- Security events and the access records of blocked attempts are cleared automatically after a short period.
Your rights
Under UK data protection law you can ask for access to your personal data, correction, deletion, restriction, a portable copy, and you can object to processing based on legitimate interests. To exercise a right over account data, use the contact page. You can also complain to the Information Commissioner’s Office (ico.org.uk) if you think we have handled your data wrongly. We would like the chance to help first.
Security
Every organisation’s data is separated at the database level. Data is encrypted in transit, files are private and open through short-lived links, access can be restricted by role, seat, site, two-factor sign-in, single sign-on and network address, and changes are recorded in an append-only audit trail. No system is perfectly secure. If a breach affects you we will tell you as the law requires.
Cookies and similar technologies
See the cookie policy. In short: only what is needed to sign you in and remember your settings.
Children
The Service is for businesses and is not intended for anyone under 18.
Changes
We will update this page when our practices change and show the date at the top. If a change matters to you we will tell you by email or in the product.
Contact
Use the contact page for anything about this policy.