DistroShift
Trust & Security

Your data is protected by design

DistroShift handles sensitive financial and employment data for hospitality businesses across Ireland. This page explains what we do to keep that data secure — in plain English, not marketing copy.

Encryption at Rest
All sensitive financial data is encrypted before it touches the database. IBANs and PPS numbers use AES-256-GCM with a unique random IV per record. Payment provider credentials and data exports use the same standard.
AES-256-GCMUnique IV per recordAuthenticated tag
Encryption in Transit
All traffic is served exclusively over HTTPS. Session cookies carry the __Secure- prefix, meaning browsers will only send them over encrypted connections. No data ever travels in plaintext.
HTTPS onlyHttpOnly cookiesSecure + SameSite=Lax
Role-Based Access Control
Granular, least-privilege permissions are enforced at the API layer on every request. Role claims in session tokens are never trusted on their own — they are re-verified against the database on each sensitive operation. Staff, roster, leave, tip, and billing operations each have independent permission gates.
Least-privilege modelAPI-layer enforcementRe-verified per request
Staff PIN Security
Clock-in PINs are hashed using an industry-standard key derivation function with a unique random salt per PIN. The plain PIN is never stored and never returned in any API response. All PIN comparisons use constant-time verification to prevent timing-based enumeration attacks.
Salted key derivationNever stored in plainConstant-time verification
Bot & Abuse Protection
The public demo-request form and every embeddable booking widget are protected by Cloudflare Turnstile, verified server-side. Both are fail-closed in production — if the secret key is not configured, the request is rejected rather than silently bypassed. Sign-in is protected by per-email rate limiting.
Cloudflare TurnstileFail-closed in prodPer-email rate limiting
Full Audit Log
Every significant action — staff creation, tip confirmation, admin changes, payout events, support access — is recorded with actor identity, timestamp, IP address, and before/after data. Audit records cannot be deleted by venue managers.
Immutable recordsActor + IP loggedWRC-admissible
Multi-Tenancy Isolation
Every database query is scoped to the authenticated business. It is architecturally impossible for one venue's manager to read or modify another venue's staff, roster, tips, or leave data through the API.
Scoped per accountSession-enforced tenantNo cross-venue access
Infrastructure
Application compute runs on Vercel in the EU (Dublin, Ireland — eu-west-1) and the database is Neon PostgreSQL on AWS eu-central-1 (Frankfurt, Germany). All personal data is stored in the EU. Transfers to US sub-processors are covered by Standard Contractual Clauses.
EU compute (Dublin)EU database (Frankfurt)SCCs for US transfers

What’s encrypted and where

DataStorageWhat you see in the UI
Staff IBANAES-256-GCM, encrypted at restLast 4 digits only (e.g. ****1234)
Staff PPS numberAES-256-GCM, encrypted at restMasked — never shown after entry
Clock-in PINSalted hash using industry-standard key derivation — plain PIN never storedPIN set / not set indicator only
Payment credentialsAES-256-GCM, encrypted at restNot displayed after saving
Data exports / backupsAES-256-GCM before upload to Blob storageDownload link (authenticated, time-limited)
Manager OTP codesHashed before storage, single-use, expire in 10 minEntered once at sign-in

Response headers on every request

HeaderValueWhat it prevents
X-Frame-OptionsSAMEORIGINClickjacking via cross-origin iframes
X-Content-Type-OptionsnosniffMIME-type sniffing attacks
Referrer-Policystrict-origin-when-cross-originReferrer header leakage
Permissions-Policycamera=(), microphone=(), geolocation=()Unwanted browser API access

Compliance posture

GDPRCompliant

Designed for GDPR compliance as it applies in Ireland. Data Processing Agreements available on request.

SOC 2Aligned

Built with SOC 2 Trust Service Criteria in mind across security, availability, and confidentiality. Formal certification is on our roadmap.

Tips & Gratuities Act 2022Compliant

Audit trail, staff statements, and distribution records meet WRC compliance requirements.

OWtA 1997Supported

Leave entitlements, working hour records, and public holiday handling align with the Organisation of Working Time Act 1997.

Your business is the data controller for your staff’s personal data. DistroShift acts as your data processor. A Data Processing Agreement (DPA) is available on request at info@distroshift.com. Application compute runs in the EU (Dublin, Ireland) and staff and financial data is stored in the EU (AWS eu-central-1, Frankfurt), with Standard Contractual Clauses in place for any US-based sub-processors.

Read our full Privacy Policy for details on what we collect, how long we retain it, and how to exercise your GDPR rights.

Incident response

In the event of a confirmed data breach affecting personal data, we will notify affected businesses within 72 hours of becoming aware of it, in line with our obligations under GDPR Article 33. Notifications will include the nature of the breach, categories of data affected, likely consequences, and the measures taken or proposed. Business owners are responsible for notifying their affected staff members where required.

Security incidents can be reported to security@distroshift.com.

Responsible disclosure

If you discover a security vulnerability in DistroShift, please report it responsibly by emailing security@distroshift.com. We will acknowledge receipt within 48 hours and aim to resolve critical issues within 72 hours. Please do not publicly disclose vulnerabilities until we have had a reasonable opportunity to address them. We appreciate responsible researchers and will credit disclosures where permission is given.

Questions

For security questions or to request a Data Processing Agreement, contact security@distroshift.com. For general privacy queries, use info@distroshift.com.