Security & trust

How StrikeGrid protects customer and incident data.

StrikeGrid stores responder contact details and incident records. Access is restricted by organisation and role, and response events are recorded so they cannot be rewritten by application users.

UK and EU data residency

Customer data is stored in the UK or EU according to the service configuration and customer requirements.

Organisation isolation

Requests and data access are scoped to the customer organisation.

Role-based access

Admin, Operator and Viewer roles limit who can change plans, run responses and review records.

Append-only incident history

Application users cannot edit or delete recorded response events.

Separate communication providers

The response workflow is kept separate from the services used to place calls and send messages.

Data minimisation

StrikeGrid collects the contact and incident information needed to run the response.

Authentication and access control

Authentication and permission checks protect customer and administrative areas.

Recoverable processing

Queued work, duplicate-event protection and recovery controls help active responses continue after a temporary failure.

Security information

Review the controls before you buy.

Detailed security, privacy, subprocessor and service-resilience documents will be published before general availability. Prospective customers can review the current system design, data flows and deployment controls with the StrikeGrid team now.

Security review

Review identity, permissions, data flows, hosting and communication providers.

Procurement questions

Send us your data-protection and supplier-security questions for a written response.

See StrikeGrid in action

Bring one of your Response Plans. We’ll show you how it runs.

Book a demo →