Privacy policy

1. What information is used

• Host account: email, name, timezone, availability, meeting types, team membership and profile details you choose to provide, including an avatar and company information.
• Guest booking: name, email, selected time and timezone, answers to the host's questions, and the booking's confirmation, cancellation or rescheduling status.
• Connected calendar: provider account email, selected calendars, encrypted refresh tokens and identifiers of events created for bookings.
• Service operation: session and access-key records, delivery status and technical diagnostic events used to operate and protect the service. Infrastructure providers also process network request data.

Public profile details and meeting descriptions are visible to people who open the booking link. Guest details and answers are shared with the host and relevant meeting participants through the booking, invitation and connected integrations. Do not include sensitive information that is unnecessary for the meeting.

2. Google Calendar, Yandex Calendar and Microsoft 365

Signing in and connecting a calendar are separate actions. Calendar access is requested when you connect it. The service reads availability and the calendar list, and creates, updates or removes calendar events associated with its bookings.

Google permissions are calendar.freebusy, calendar.events and calendar.calendarlist.readonly. Yandex uses calendar event, calendar list and free/busy permissions. Microsoft uses Calendars.ReadWrite and offline access. Event permissions allow broader access at the provider level than the operations the scheduling service performs.

Google's and Yandex's availability responses supply busy intervals. Microsoft's schedule response may contain additional event fields; the availability calculation extracts start and end times, not titles or descriptions. The calculated intervals are temporarily cached with a 60-second TTL and are not stored as a history of your external calendar events in the booking database.

Use of information received from Google APIs follows the Google API Services User Data Policy, including Limited Use requirements. Calendar data is used for scheduling, not advertising or training general-purpose AI models. Access or transfer for other purposes is limited to the exceptions allowed by that policy, such as an authorized support investigation, security or applicable law.

3. Cookies and analytics

Technical cookies support sign-in and the security of authentication flows. Google Analytics 4 is currently disabled on this deployment. Analytics code is not loaded in the dashboard, booking pages or meeting management pages. Browser settings let you manage cookies; blocking technical cookies can prevent sign-in.

4. Where information goes

Information needed for the selected features is processed by the service's hosting and storage providers, its transactional email provider and your connected calendar provider. Host-configured webhooks can send booking information to the endpoints the host selects. Calendar content is not sold or sent to advertising systems.

Provider names, storage regions and any cross-border processing depend on this deployment. Contact hello@mymeet.ai for details. No claim that all information remains in one country is made here.

5. Disconnecting, retention and data requests

Disconnecting a calendar in the dashboard removes its connection and token from the active service database. It does not revoke the authorization at Google, Yandex or Microsoft, erase existing events in the provider's calendar or delete previously sent invitations. You can also revoke access in your Google, Yandex or Microsoft account settings.

Bookings and account information remain in the database unless they are removed. The current dashboard has no self-service account export or account deletion. Request access, correction, export, deletion or withdrawal of consent by writing to hello@mymeet.ai; specify the account or booking concerned. Identity verification may be needed to protect the data.

Cancellation changes a booking's status; it does not erase its history. Deletion from the active database does not immediately remove data from earlier backups or from recipients' calendars and emails. Ask support for the applicable retention periods and how a deletion request affects these copies. This page does not promise an automatic deletion period that the service does not implement.

6. Security and independent deployments

Calendar refresh tokens are encrypted before storage using AES-GCM. Session identifiers and API keys are stored as hashes. Guest management links are signed and expire; anyone with a valid link can use it, so keep it private.

An independently hosted installation has its own operator, infrastructure and retention practices. The operator is responsible for configuring this notice for that deployment. Questions and data requests: hello@mymeet.ai.