Trust & Security

Security built in, not bolted on

GuardFlow holds sensitive operational, staff and compliance data for UK security firms. Here's a plain-English, honest account of the controls we have in place today.

What's in place today

Role-based access control

Every user has a defined role: company owner, operations manager, HR, finance or staff, plus custom roles you define. What each person can see and do is scoped to their role, so officers and managers only ever access what's relevant to them.

Row-level security on every table

Access rules are enforced in the database itself, not just the interface. Each company's data is isolated by tenant at the row level, so one customer can never read or write another customer's records.

Audit logging

Sensitive actions are recorded to an audit trail with the user and timestamp, giving you accountability over changes to staff, compliance, finance and operational records.

Encrypted in transit and at rest

Every connection to GuardFlow uses HTTPS with TLS 1.2 or later, so data moving between your team, our servers and the database is encrypted in transit. Stored data is encrypted at rest by our infrastructure provider.

Private document storage

Compliance documents, incident photos and site files are held in private storage and opened through short-lived links, only by authorised users in the owning company.

Database hosted in Zurich, Switzerland

The production database and file storage are hosted in Zurich, Switzerland, which the UK recognises as providing an adequate level of data protection. The application runs on Cloudflare's network, and our other providers process data where they choose. Automated backups are provided by our database provider.

Records that can't be quietly changed

Clock-ins, written occurrence book entries and key custody records can't be edited or deleted through GuardFlow. A corrected clock time is kept alongside the original punch, so the history stays intact.

Least-privilege administration

Platform administration is limited and role-gated. Support access to a customer account through the app (View as) is controlled and logged. Our operators can also run queries directly on the production database through the hosting platform, and those are not recorded in the application audit log.

GDPR-conscious by design

We provide a Data Processing Agreement, a clear privacy policy and tooling to support data subject access and deletion requests. Personal data is collected for defined operational purposes only.

Who handles data for us

These companies process customer data on our behalf. What each one can handle, and when it is used, is in the UK GDPR statement.

  • Supabase

    Database, sign in and private file storage.

  • Cloudflare

    Runs the GuardFlow application on its network and delivers it to browsers, so each request is processed at a Cloudflare location that Cloudflare chooses. Also provides the bot check on the free trial sign up form.

  • Lovable

    Builds and publishes the application. Its gateway carries every call our servers make to Stripe, and it relays the signed event that starts each sign in email. Our production database project sits in Lovable's own organisation on the database provider, so Lovable also administers the account that holds it.

  • Stripe

    Payment processing for subscriptions and invoices, for companies billed through GuardFlow.

  • Resend

    Delivers the email GuardFlow sends: sign in links, invitations, reminders, alerts and reports.

  • Twilio

    Sends text messages and places voice calls. Texts go out when a manager sends an officer a shift reminder, when a shift with no guard yet starts within 4 hours, and for incident alerts and control room alerts. Texts and calls go out for a welfare check that has not been answered.

  • Expo

    Delivers push notifications to the GuardFlow Companion mobile app, passing them on to Apple and Google. Also delivers over the air updates of the app's own code.

  • Lovable AI gateway

    Passes requests from the operations assistant and the morning briefing to a language model chosen by the gateway. Our default is a Google Gemini model. Nothing is changed unless a manager first confirms the exact change.

Your data, your control

  • Your data belongs to you and can be exported.
  • We process personal data as a processor on your behalf, under a Data Processing Agreement.
  • We support data subject access and deletion requests.