Data and consent
Forms record a purpose-specific consent and do not subscribe visitors to marketing. Submitted records require the client-owned database to be configured.
Privacy draft ↗Trust comes from
clear controls and limits.
This page explains the intended safeguards in the current website release and the dependencies required before production use.
Access control
Account access is verified server-side. Roles are database controlled, and members can only access records permitted by the configured database rules.
Read account FAQ ↗Payment integrity
Checkout is not activated until client-owned PayPal credentials, agreed pricing and provider verification are configured. A browser redirect is never treated as proof of payment.
Payment draft ↗Production readiness
Before launch, the client must approve policies and operator details, configure Supabase, SMTP, anti-spam, booking and payment services, apply the database script, and complete security and integration checks.
Report a concern