Security & trust
This page describes controls implemented in the Digital Services Platform and separates them from legal compliance or independent certification claims.

Key authentication, tenant, user, service, submission, storage and billing events are written to a per-tenant SHA-256 hash chain. Chain verification detects missing or changed records.
Configured services can deliver submission packages to S3, Azure Blob, Google Cloud Storage, Google Drive, OneDrive, SharePoint, Dropbox or SFTP. Successful deliveries are marked external-only and their submitted values are scrubbed locally.
Production startup requires HTTPS-facing application URLs. Persisted storage credentials and OAuth tokens are encrypted with Fernet using a server-side key.
External deliveries can include JSON or CSV output, original attachments and a manifest containing SHA-256 checksums.
Key authentication, tenant, user, service, submission, storage and billing actions write records into a per-tenant log. Each record references the SHA-256 hash of the previous record and stores its own. To tamper with a single entry, an attacker would have to re-hash every entry that came after. We'd detect the change on the next chain verification.
A live excerpt from one tenant's chain
auth.login_succeededauth.login_failedclient.createduser.createduser.updateduser.deleteduser.invitedform.createdform.updatedform.deletedform.share_token_regeneratedsubmission.viewed_listsubmission.created_publicstorage_config.createdstorage_config.updatedstorage_config.deletedsubscription.changedsubscription.cancelledPlans with external storage enabled can deliver submissions into the storage destination configured for a workspace or service. Successful deliveries are marked external-only in the portal, while pending deliveries retain the data needed to complete the job. That makes data residency a function of your chosen destination for completed external workflows.
Persisted storage credentials and OAuth tokens are encrypted with Fernet using the server-side storage configuration encryption key.
Talk to an integration engineerProduction startup rejects non-HTTPS frontend, authentication and OAuth callback URLs, as well as wildcard CORS.
Persisted storage credentials and OAuth tokens are encrypted with Fernet using a required production key.
SuperTokens provides email magic-link and one-time-code sign-in, browser-session refresh, logout and revocation.
Protected routes enforce viewer, editor, admin and platform-admin permissions and tenant-scoped access.
Stripe webhook handlers validate provider signatures before state-changing events are processed.
Public services support publish controls, optional CAPTCHA and configurable per-service IP rate limits.
ServiceRecord combines security, traceability, data controls and portable records to help organisations operate with greater confidence. These capabilities can support your compliance programme while keeping responsibilities clear.
HTTPS guardrails, passwordless authentication, tenant-scoped access checks and encrypted integration secrets help protect the platform and its connections.
Tamper-evident audit records, event metadata and chain verification provide traceability for important operational activity.
External storage destinations and portable submission packages help organisations control where completed records are delivered and retained.
Implemented controls and exportable evidence can support GDPR, UK GDPR and internal governance programmes alongside your organisation’s policies and procedures.
The platform provides technical safeguards and evidence. Your organisation remains responsible for how personal data is collected, used, retained and governed.
ServiceRecord's controls can support GDPR and UK GDPR obligations, but using the platform does not by itself make an organisation compliant or represent an independent certification.
Our product team can walk procurement, IT and compliance teams through the implemented controls.