Trust · For procurement

Security controls, mapped to SOC 2

Jeanus is not yet SOC 2 audited, and we will not claim a posture we have not earned. What follows is the control set we implement today, mapped to the SOC 2 Trust Services Criteria, so your security team can assess us during procurement without a questionnaire round-trip. Everything not yet done is marked honestly.

21Implemented
3In progress
4Planned

Security (Common Criteria)

Protecting the system against unauthorised access, use, or modification.

Role-based access control
Owner / admin / rep roles gate both the UI and every API route. Reps are scoped to their own customers and leads within a tenant.
Implemented
Multi-factor authentication
TOTP 2FA available to all users and required for staff (Pixel & Shovel) accounts.
Implemented
Tenant isolation
Every query is filtered by tenant ID at the application layer and again by Postgres Row Level Security. A Playwright regression test runs against the live deployment to catch cross-tenant leaks.
Implemented
Encryption in transit
TLS 1.2+ on every connection; HTTPS enforced end to end.
Implemented
Encryption at rest
AES-256 on the database volume and on encrypted backup snapshots (Supabase / AWS).
Implemented
New-IP sign-in alerts
An email alert fires when an account signs in from an unrecognised IP address.
Implemented
Audit logging
Authentication and data-change events are recorded. Tenant admins can view their tenant slice; a fuller export is available on request.
Implemented
Secrets management
The service-role key that bypasses RLS is used only in server-side routes and never exposed to the browser. Secrets live in the platform secret store, not in source.
Implemented
Secure SDLC
Pull-request review, TypeScript type-checking, and an automated database schema-drift check run before merge.
In progress
Vulnerability management
Automated dependency vulnerability alerts are enabled. A formal patch cadence and tracking policy are being documented.
In progress
Penetration testing
No third-party penetration test has been commissioned yet. We plan to run one ahead of our first enterprise contract.
Planned

Availability

Keeping the system available for operation and use as committed.

Managed, redundant hosting
Application on Vercel, database on Supabase (managed Postgres, multi-AZ) in the UK / EU region.
Implemented
Encrypted backups
Daily encrypted database snapshots retained for 30 days.
Implemented
Breach notification
Commitment to notify affected customers within 72 hours of a confirmed breach.
Implemented
Incident response plan
An informal runbook is in place; a formal, documented incident-response plan with defined roles is in progress.
In progress
Disaster recovery (RTO/RPO)
Point-in-time backups exist; a formal DR runbook with tested restore targets is planned.
Planned

Confidentiality

Protecting information designated as confidential.

Data segregation
Each tenant’s data is logically isolated and enforced at the database layer.
Implemented
Least privilege
Access is limited by role and, within a tenant, by rep ownership. Staff access to customer data is limited and logged.
Implemented
Data retention & deletion
Customers can export their data at any time and request deletion; deletion is honoured as part of a data subject request.
Implemented

Processing Integrity

Ensuring processing is complete, valid, accurate, timely and authorised.

Input validation
Server-side validation on API routes; typed request handling throughout.
Implemented
Schema-drift checks
An automated check validates every database query against the live schema in CI, so a mismatched column is caught before it ships.
Implemented
Idempotent, signed integrations
Outbound webhooks are HMAC-SHA256 signed with an auto-retry queue and manual replay; retries are byte-identical.
Implemented

Privacy

Handling personal information in line with commitments and regulation.

UK GDPR / ICO registration
Registered with the ICO (ZC068491). A Data Processing Agreement is available.
Implemented
Consent management
Analytics and website-visitor tracking are gated on cookie consent; IP addresses are hashed before storage.
Implemented
Subprocessor transparency
A current list of subprocessors is published at /subprocessors.
Implemented
Data subject requests
Access, export and deletion requests are supported.
Implemented

Formal attestations

Independent audits and certifications.

SOC 2 Type I / II
Not yet audited. We will pursue a SOC 2 examination when a customer contract requires it, and can scope one against the contract value.
Planned
ISO 27001
Not yet certified. On the roadmap alongside SOC 2 for UK / EU enterprise buyers.
Planned

Running a vendor review?

Read the full security overview and the subprocessor list. For a completed security questionnaire, a DPA, or to scope a penetration test against your contract, email hello@pixelandshovel.co.uk.

Last reviewed: 2026-07-28.