Your information,
handled carefully.

What the site collects

If you submit a booking request, it stores your name, email, requested service, requirements, chosen time, and status so the owner can respond. The contact form stores your name, email, and message. Visitors do not need accounts.

The assistant stores its messages and a random session identifier so it can maintain context. Use Clear conversation to request deletion of that chat session. The website also keeps short-window rate-limit counters to reduce spam.

Where information goes

When deployed, website requests pass through Cloudflare Pages/Workers, with application records stored in Supabase. Images uploaded to the media library are served from a public-read bucket; only upload images intended for public display.

If the owner enables a hosted AI provider, the current question and relevant approved business notes are sent to that provider to generate a reply. Hosted provider calls are disabled by default. The owner must explicitly unlock them, and a provider may charge for requests. When configured to use Ollama, the website routes requests through an owner-managed, Access-protected tunnel.

Gmail notifications are not connected at this stage. The owner should publish final provider and retention details before launch.

Owner access and retention

Only the designated owner dashboard is intended to read booking/contact records. Administrator routes require the owner's Supabase account, an allow-list entry, and a verified authenticator factor. Booking and contact records remain stored until the owner removes them or applies a retention policy; no automatic deletion schedule is configured yet.

To ask about or request deletion of a booking or contact message, use the contact page and include the email address used for that request. Do not send passwords, authenticator codes, or sensitive personal details.