Verified sign-in
Access requires signing in with Google. Every credential is verified server-side before a session is ever created — client-supplied identity is never trusted on its own.
Encrypted credentials
OAuth refresh tokens used to send email are stored encrypted, never in plain text, and are never exposed to the browser or logged.
Role-based access
What a team member can see and do is determined server-side by their assigned role — never by anything the browser sends. Admin-only areas are enforced on every request, not just hidden from navigation.
Encrypted card data
A card number entered on a booking form is encrypted before it is stored, never kept as raw card data, and can be revealed only by explicitly authorized staff — each reveal is logged. The card's security code is held encrypted only until the manual charge is recorded and never longer than 24 hours after the booking form is signed. Booking forms are served over HTTPS in production.
Questions about a specific security practice? Get in touch.