Security and trust

Your data, in the UK, in its own lane.

Where PyroPortal data lives, how one company is kept apart from the next, and what we do not yet claim. Send this page to whoever signs off on software.

Ask a security questionPlatform features

Where your data lives

The API runs on Azure App Service in the UK West region and the database is Azure SQL in UK South. The marketing site, the portal front-end and the public booking pages are served through Cloudflare. Your data does not leave the UK for storage.

Tenant isolation at the database

Every tenant table carries a tenant key and the database enforces Row-Level Security on it. The API sets the tenant context for each request, and a query with no tenant context returns nothing. Isolation does not depend on application code remembering to filter.

Signing in

Authenticator-app two-factor authentication with QR enrolment, secrets stored encrypted. Put users in the Require-MFA group and they cannot sign in without it. Passwords must be at least 12 characters and are checked against known breach lists; repeated failures lock the account for a period. Login and password endpoints are rate-limited per address.

Who can see what

Permission groups with per-area rights, viewing and editing separated. There is no single all-powerful admin flag. Crew members get a portal that shows only their own shows.

Integrations and public pages

AI assistants connect through per-user MCP tokens you can revoke at any time from Settings. Public booking pages are addressed by a random token, never a numeric ID, and answer every failure with the same generic response so a probe learns nothing.

Backups and continuity

Azure SQL takes automated backups with point-in-time restore. The API and front-ends deploy from version control, so a rebuild is a redeploy. Ask us for the current retention window before you rely on it.

What we do not claim yet

A security page that only lists strengths is a marketing page. These are the things a larger buyer will ask about that are not in place today.

  • Single sign-on (SSO / SAML). Every user signs in with email, password and optional two-factor.
  • A published penetration-test report, or an ISO 27001 or SOC 2 certificate. We have neither yet and will not put a badge on the site until we do.
  • A data processing agreement on the site. One is available on request.
  • Customer-managed encryption keys.
  • A public status page.

Found something? Email hello@pyroportal.co.uk with the details and we will reply within one working day.

Common questions

Is PyroPortal hosted in the UK?
Yes. The API runs on Azure App Service in UK West and the database on Azure SQL in UK South. Cloudflare serves the front-ends from its edge network, and stored data stays in the UK regions.
Can another company on PyroPortal see our data?
No. Tenant isolation is enforced with Row-Level Security at the database on every query, not just in application code. A request without a tenant context returns nothing.
Do you support two-factor authentication?
Yes, authenticator-app two-factor with QR enrolment. Add users to the Require-MFA group to make it mandatory for them.
What happens to our data if we leave?
Every list page exports to CSV and your data is available through the API for as long as your account is open. Tell us when you are leaving and we delete the tenant on a date you choose.
Do you have a DPA, a pen-test report or ISO 27001?
A data processing agreement is available on request. We do not yet have a published penetration test or an ISO 27001 or SOC 2 certificate, and we say so here rather than imply otherwise.

Read the privacy policy