MyKalent

Last updated 22 November 2026

Privacy Policy

MyKalent is a scheduling service. This policy explains what we collect, why, who we share it with and the choices you have. We keep it short and we don't sell your data.

Who we are

“MyKalent”, “we” and “us” mean the operator of the MyKalent service at mykalent.app. You can reach us at [email protected].

We act as the controller for the account data of people who sign up (“hosts”). For the people who book time with a host (“invitees”), we process booking data on behalf of the host, who decides what to ask and how to use the answers.

What we collect

  • Account data: name, email address, username, time zone, language, password (stored only as a bcrypt hash), profile settings such as avatar, logo and brand color.
  • Scheduling data: event types, availability, and bookings, including invitee names, email addresses, guest emails, notes, answers to custom questions, phone numbers when a phone meeting is chosen, and the invitee’s time zone and language.
  • Team data: organization and team membership, roles and invitations.
  • Connected accounts: if you connect Google, Microsoft, Apple iCloud or Zoom, we store the access tokens (or app-specific password) needed to use them, encrypted with AES-256-GCM, plus the list of your calendars and the IDs of events and meetings we create.
  • Payments: subscription status and billing identifiers from Stripe. Card details are entered on Stripe’s pages and never reach our servers. For paid bookings we store the amount, currency and Stripe payment identifiers.
  • Security and usage logs: IP address, browser user agent, sign-in events and changes to sensitive settings, kept to protect your account and the service.
  • Website analytics: the pages you visit on mykalent.app, the referring site, your time zone, campaign (UTM) parameters and a random per-tab session ID, plus visits from AI crawlers and assistants. Secret links (booking management, polls, invitations) are masked before they are sent. We use this to understand how people find and use MyKalent.

How we use it

  • To provide the service: show availability, create bookings, send confirmations, reminders and updates, and run the workflows you set up.
  • To sync with the calendars and video tools you connect, at your request.
  • To bill subscriptions and process payments for paid bookings.
  • To secure accounts, prevent abuse and fix problems.
  • To contact you about your account and important changes to the service.

Our legal bases are performing our contract with you, our legitimate interest in running a secure service, compliance with legal obligations, and your consent where we ask for it (for example when you connect a calendar).

Google user data

When you connect Google Calendar or sign in with Google, MyKalent requests only what it needs:

  • Sign in with Google (openid, email, profile): your name, email address and Google account ID, used to create or sign in to your MyKalent account.
  • Calendar read access (calendar.readonly): the list of your calendars and the busy times in the ones you choose, so people can’t book you when you’re busy. We read busy times, not event contents.
  • Calendar events (calendar.events): to add your MyKalent bookings (with a Google Meet link if you choose Meet) to the calendar you pick, and to update or remove them when a booking changes.

MyKalent’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don’t use Google user data for advertising, we don’t sell it, we don’t use it to train AI or machine-learning models, and no human reads it unless you ask us to for support, it’s needed for security, or the law requires it.

You can disconnect Google at any time under Integrations in MyKalent, and revoke access at myaccount.google.com/permissions. Disconnecting deletes the stored tokens and calendar list.

Who we share data with

We share data only with service providers that help us run MyKalent, and only as needed:

  • Stripe for subscriptions and paid bookings.
  • Resend to deliver emails.
  • Twilio to send text messages, only if a host enables SMS workflows.
  • Google, Microsoft, Apple and Zoom, only when you connect them, to read busy times and create events and meetings.
  • Sight (usesight.dev) for cookieless website analytics.
  • Cloudflare for DNS. The application and database run on infrastructure we operate.

Hosts see the details of the bookings made with them, and webhooks or API keys a host configures may send booking data to systems the host chooses. We may disclose data if required by law. We never sell personal data.

Cookies and local storage

We use one strictly necessary cookie to keep you signed in (an httpOnly session refresh cookie). We store a few preferences in your browser’s local storage, such as theme and whether you’re signed in, and our analytics keeps a random session ID in session storage that is cleared when you close the tab. We don’t use advertising or third-party tracking cookies.

Retention

We keep account and booking data while your account exists. You can delete your account from Settings at any time; your data is then removed, and invitees with upcoming meetings are notified. Security logs are kept for a limited time. Backups are overwritten on a rolling basis. We may keep billing records as long as tax law requires.

Your rights

Depending on where you live (for example under the GDPR or Turkey’s KVKK) you can access, correct, export or delete your data, object to or restrict processing, and withdraw consent. You can export your data and delete your account in Settings, or email us. Invitees can contact the host or us. You may also complain to your data protection authority.

Security

Connections are encrypted with TLS, passwords are hashed, connected-account secrets are encrypted at rest, and access is limited to what each part of the system needs. No system is perfectly secure; if a breach affects you, we’ll tell you as the law requires.

International transfers

Some of our providers process data in other countries, including the United States. Where required, transfers rely on safeguards such as standard contractual clauses.

Children

MyKalent isn’t meant for children under 16, and we don’t knowingly collect their data.

Changes

If we change this policy in a meaningful way, we’ll update the date above and let account holders know by email or in the app.