Booking privacy notice
Data and purposes
Dion processes your name, email, optional phone, request details, links, language, appointment times and booking status to schedule, contact and assist you. If you choose to connect Google, the system also processes your Google identifier (subject), verified email, Calendar session and booking-to-account links to synchronize events and let you view and manage your history. The system also processes IP addresses for anti-abuse/rate limiting, management tokens and technical data needed for security, retries and action records. Hashing an IP does not make it fully anonymous.
Providers receiving data
Cloudflare hosts the website/API, D1 and Turnstile; Microsoft 365/Graph sends email; Telegram delivers booking details to Dion for approval; Google Calendar/Meet handles events, invitations and meetings after approval, including email-only bookings. Depending on the flow, providers receive data needed for their function and may process it outside Vietnam under their own terms. Only the Google option requires a connection and calendar.events.owned permission. This permission allows reading, creating, editing and deleting events on calendars you own; the application only accesses the Diondam events it manages.
Retention and security
Bookings, action history and integration data are retained for operation, support and troubleshooting; there is currently no fixed automatic deletion period for all booking records. New booking tokens expire after 90 days; token expiry is not booking deletion. Expired replay data is cleaned in batches. Access is restricted, authentication tokens are hashed and some recovery data is encrypted; no system guarantees absolute security.
Data requests
Contact [email protected] to ask about, correct or request deletion of your data. Email or booking ownership may need verification. Some records may need retention for legal obligations or disputes; provider copies follow their retention mechanisms. Do not include tokens or passwords in support requests.
Google Calendar connection
Refresh tokens are encrypted in D1 and never sent to the browser. Connections remain until you disconnect or access is revoked. Disconnect Calendar on the booking page deletes the stored token and Calendar session and stops synchronization for linked bookings; it does not cancel bookings, erase booking history or delete existing events. History on the booking page is unavailable until you reconnect the same Google account (the same subject). Private management links continue to work while valid. You can also revoke access in your Google account settings. Manage existing events yourself after disconnecting and use the management link to cancel a booking. For data deletion, contact [email protected]. Google data is used only for booking functionality, not advertising or AI model training. Use and transfer of Google data adhere to the Google API Services User Data Policy, including Limited Use requirements.
Booking choices
Google sign-in is optional. You can choose email on the form without signing in or granting Calendar access: after approval, you receive a normal Google Calendar invitation from Dion, a Meet link and booking emails; use your private management link to view or cancel as permitted by the policy. If you choose Google, the system uses your existing Calendar connection session and granted permission to create a private event directly in your primary calendar after approval, with a Meet link; no invitation acceptance is needed and no duplicate invitation is sent. Keep management links private: anyone with a valid link can view and manage the booking.
Booking history and ownership
With Google connected, you can view history on the booking page, open each booking and cancel when permitted by the policy. Access is based on the booking’s link to your Google identifier (subject), not your email. Reconnecting the same account restores access to previously linked Google bookings even if the connection generation has changed; restored history access does not mean old events automatically resume synchronization. Email bookings are not automatically linked or included in Google history, even when the email addresses match.
Your other choices
Do not include sensitive information or other people’s data in briefs or links. You may choose not to use the form and email to ask about alternative scheduling. Booking status emails do not automatically subscribe you to marketing. This notice describes the booking flow, not every external service.