Booking privacy

Details you share

We store your name, email, company, chosen topic, optional project brief, appointment time and timezone. We also keep the booking’s status, reference, creation time and a history of administrative changes. These details let us reserve your time, prepare for the call, contact you and manage changes or cancellations.

Your booking is visible to authorized Dot staff through a password-protected workspace. It is not listed publicly. Please leave passwords, API keys, payment details and sensitive personal information out of your project brief.

Google Calendar and Meet

The Dot host can connect a Google account. Guests do not need to connect their own calendar to book. For the connected host, we access the verified account email, calendar availability and booking events. The permissions allow us to create, read, update and delete events on calendars the host owns. We use this access to avoid scheduling conflicts, create invitations and Google Meet links, and manage booked calls. We do not request Gmail or Google Drive access.

When calendar scheduling is enabled, the appointment details and your name, email, company, topic and project brief are included in the Google Calendar event. Google processes these details to provide Calendar, invitations and Meet. Meeting participants may see the organizer’s identity and event details.

We store the connected host’s account email and authorization credentials on the server, along with the booking’s Google event identifier and Meet link. Credentials are not sent to guests. Availability checks use busy time intervals; we do not copy the host’s unrelated calendar event titles or descriptions into the booking database.

Google account data is used only to provide scheduling. We do not sell it, use it for advertising, or send it to AI models for inference or training. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Service providers and browser storage

Our hosting and database providers process booking data to run this service. Infrastructure providers also process connection information, such as an IP address, to deliver and protect requests. If email notifications are enabled, the notification provider receives the booking reference and appointment time. Google’s services are also subject to Google’s Privacy Policy.

Your browser stores your timezone preference and a booking receipt that lets you return to the confirmation during the session. Admin access uses an expiring session cookie. Admin sign-in protection uses keyed hashes of IP addresses and short-lived attempt counters.

Storage, cancellation and deletion

Booking records and their change history are stored on the server. Cancelling a call changes its status; it does not automatically erase the booking record. There is currently no automatic deletion schedule. We use retained records for scheduling, follow-up and resolving booking issues.

To request access, correction or deletion of your booking details, email sales@usedot.xyz from the address you used to book. We may need to verify your request. Where data must be retained for a legal obligation or an unresolved dispute, we will explain the applicable limit.

The connected host can revoke Dot Booking’s access in Google Account connections and ask us to remove the stored connection credentials. Revoking access stops future calendar access but does not by itself delete existing calendar events, invitations or booking records. Recipients and providers may retain their own copies under their policies.

Your choices

We use the details you provide to respond to your meeting request and arrange the call, and use limited technical data to secure the service. Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, request a portable copy, or contact your data protection authority. Send privacy questions and requests to sales@usedot.xyz.

We will update this page when booking data practices change. A new use of connected Google data will require an updated disclosure and any required authorization before it begins.