Privacy policy

Last updated: October 10, 2026

This policy covers BriefVoice Calendar, the booking service used by the BriefVoice voice assistant. The service is operated by Hlib Bezuhlyi. Contact: hlib.bezuhlyi9@gmail.com.

Google Calendar access

The calendar owner authorizes access through Google OAuth. We use calendar access to check busy times, create demo appointments with Google Meet links, and retrieve booking details to confirm a meeting or retry a booking without creating a duplicate.

The requested event permission allows viewing, creating, changing, and deleting calendar events. The current booking flow checks availability and creates and retrieves demo events; it does not automatically change or delete unrelated events. We also request permission to read calendar availability. We do not request access to Gmail messages, Google Drive files, or Google contacts.

Demo events include the caller's phone number, appointment time, and a call identifier. Google stores the event and generates the Meet link. People who already have access to the connected calendar may be able to see these event details.

Data we receive and store

SMS booking links use a Google Meet code; earlier links use a random booking identifier. Anyone holding the link can open the corresponding Google Meet meeting. The link endpoint does not display the caller's phone number or booking notes.

• Calendar busy intervals are used to calculate available appointment times. The booking service does not copy the full calendar into its database.
• Booking records contain the caller's phone number, timezone, call and request identifiers, appointment time, Google event identifier, Meet link, booking status, and SMS delivery status.
• Callback requests contain the phone number and any callback note supplied to the service. Operational records include request status and error diagnostics.
• Google OAuth credentials and refresh tokens are kept on the backend to maintain the authorized connection; they are not included in public pages or booking responses.

The booking service does not itself record call audio. A connected voice assistant and its voice, AI, or tracing providers may process conversation data and booking results as part of handling the call.

Why we use data

We use these data to offer available slots, arrange the requested demo, deliver its Meet link, handle callback requests, prevent duplicate bookings, and diagnose service failures. We do not sell Google user data, use them for advertising, or use them to train general-purpose AI models.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Existing bookings and the Google Calendar transition

Earlier versions used Cal.com for scheduling. For those bookings, Cal.com received the appointment time, attendee name and email, and a phone number when supplied, and returns booking identifiers and meeting information. These details may also be stored in the service database. New bookings use the Google Calendar integration described above after the operator authorizes the calendar connection.

Who receives data

• Google processes calendar requests, stores demo events, and provides Google Meet.
• SMSPLANET receives the recipient's phone number and SMS text, including the appointment time and Meet link, when an SMS is requested.
• The connected voice assistant receives offered slots and booking results, including the appointment time and Meet link, to communicate with the caller. Its configured providers may process these results to deliver that conversation.
• The operator receives callback details through the configured notification channel. Access to Google data by a person is limited to the owner's permission, security investigation, or legal requirements allowed by Google's Limited Use rules.
• Hosting and network providers, including Cloudflare, may process technical request information such as IP addresses and request metadata to deliver and protect the service.

Providers process information under their own terms and privacy policies. Transfers of Google user data are limited to delivering these features with the owner's consent, security purposes, or legal obligations permitted by Google's policy.

Storage, retention, and security

Booking and callback records are stored in the service's PostgreSQL database. The current service has no automatic deletion schedule: records remain until the operator removes them. OAuth credentials remain until the connection is removed or replaced.

The booking API requires authentication. Public pages contain no booking records or credentials. Access to backend credentials and stored records is restricted to service operation. Requests to Google and the SMS provider use HTTPS.

These public pages do not set application cookies or load analytics scripts. Network and hosting providers may maintain their own technical logs.

Revoke access or request deletion

The calendar owner can revoke BriefVoice Calendar's access at any time in Google Account connections. Revoking access stops future authorized calendar requests; it does not automatically remove existing calendar events or records already held by the booking service.

To request access to, correction of, or deletion of your booking or callback data, or removal of stored OAuth credentials, email hlib.bezuhlyi9@gmail.com. Include enough information to locate the booking, such as the phone number and approximate appointment date. We may need to verify that the request concerns your data. Deletion requests are handled by the operator; there is currently no automatic deletion endpoint.

Data already held by Google, SMS, or voice providers are subject to those providers' retention and deletion processes. Calendar events can also be removed by the calendar owner.

Changes to this policy

Updates will be published here with a revised date. If we introduce a new use of Google user data, we will disclose it and obtain the required consent before that use.