Skip to content
Bookly
FeaturesPricingDocsChangelog
Get started
Bookly

The meeting is booked. Bookly handles the rest.

Open source under AGPL-3.0. Self-host it, or let us run it for you.

Product

  • Features
  • Why Bookly
  • Pricing
  • Changelog
  • Documentation

Self-host

  • GitHub
  • Install guide
  • API reference
  • Report an issue

Company

  • About
  • Contact
  • Security

Legal

  • Privacy policy
  • Terms of service
  • Data processing agreement
© 2026 Cloudeo Solutions, LLC. Built by Ahmad Hakroosh.support@bookly-app.io

Privacy policy

Plain language first, the formal parts after. If anything here is unclear, ask us.

Last updated September 23, 2026

Who we are

The hosted Bookly service (“Bookly”, “we”) is operated by Cloudeo Solutions, LLC, Cloudeo Solutions, LLC. You can reach us at support@bookly-app.io. This policy covers the hosted service only. If you self-host Bookly, you are the operator and this policy does not apply to your installation.

Two kinds of people

Hosts create a workspace and use Bookly to take bookings. Guests book time with a host. For guest data, the host is the controller and Bookly processes it on the host's behalf; for host account data, Bookly is the controller.

What we collect

From hosts

  • Account details: name, email, password hash, profile photo and timezone.
  • Workspace content: event types, availability, contacts, notes, tasks and settings.
  • Integration data you connect: calendar events (to detect conflicts and create events), conferencing links, CRM records you choose to sync, payment status from Stripe. We store the tokens needed for these connections, encrypted.
  • Billing: plan, invoices and payment status. Card details are held by Stripe, not us.
  • Usage and logs: pages visited within the app, API requests, errors, and IP addresses in server logs for security and abuse prevention.

From guests

  • What you enter when booking: name, email, phone if asked, answers to the host's questions, timezone, and the time you booked.
  • If the host enabled it and you agreed, a transcript of the call on Bookly video, with speaker labels and any recap generated from it.
  • Emails, texts or WhatsApp messages sent to you about the booking, and their delivery status.

Why we use it

  • To run the service: show availability, create bookings, send confirmations and reminders.
  • To provide the meeting features hosts turn on: briefings, transcripts, recaps, tasks and follow-ups.
  • To bill hosts, prevent abuse, keep the service secure and fix bugs.
  • To answer support requests.

We do not sell personal data, show advertising, or use your content to train AI models. AI features send the relevant text (a contact's timeline, a transcript) to Anthropic to generate a briefing or recap; Anthropic processes it under their commercial terms and does not train on it.

Who else sees it

Sub-processors that host or deliver the service: the hosting and database providers, the email, SMS and WhatsApp delivery providers, Daily.co for Bookly video and transcription, Recall.ai for the notetaker that transcribes Google Meet, Teams and Zoom calls, Stripe for payments, Anthropic for AI features, and Sentry for error reports (with guest emails and phone numbers removed before anything is sent). Each is bound by a data-processing agreement; the full list with locations and purposes is in our data processing agreement. Data you choose to sync to Google, Microsoft, Zoom, HubSpot or Pipedrive is governed by their policies. We do not sell personal data and do not share it for advertising.

How long we keep it

  • Account and workspace data: until you delete the workspace, then 30 days in backups.
  • Transcripts and recaps: until the retention period the host set (default 90 days), or until an attendee deletes them, whichever is sooner.
  • Server logs: 30 days. Billing records: as long as tax law requires.

Your rights

You can access, correct, export or delete your data. Hosts do this from workspace settings. Guests can manage or cancel a booking from the link in their confirmation email, delete their transcript from the meeting page, and can email us for anything else. Where GDPR or similar laws apply, you also have the right to object, restrict processing, and complain to your supervisory authority. Guests should contact the host first, as the host controls their booking data; we will help either way.

Recording and transcription. When a host turns on transcription for a call, you are told on the booking page (or asked to agree there), in the confirmation email and in the call itself. Transcripts are kept for the period the host sets, and you can delete yours from your booking page at any time. Meeting notes and recaps are generated with AI from the transcript and are marked as such wherever they are shown.

Emails from hosts. Proposals, payment requests and follow-ups from a host carry an unsubscribe link; using it stops those emails from that host. Booking confirmations and reminders are part of the booking you made and continue.

California and other US state laws. You have the right to know what we hold about you, to delete it, to correct it, and not to be discriminated against for exercising those rights. We do not sell or share personal information as those laws define it, so there is nothing to opt out of. Requests go to support@bookly-app.io; we answer within 45 days.

Cookies

We use a session cookie to keep you signed in and a preference cookie for your theme. No advertising or cross-site tracking cookies. Embedded booking widgets set no cookies on the embedding site.

International transfers

Data is stored in the region shown on the security page. Where data leaves that region for a sub-processor, we rely on standard contractual clauses or an adequacy decision.

Children

Accounts are for adults (18 or older). Booking pages are not directed at children and we do not knowingly collect data from anyone under 13, or under 16 where local law sets that age; tell us if you believe we have and we will delete it.

Changes

We will post changes here and, for material changes, email hosts at least 14 days before they take effect. The date at the top shows the current version.

Sign in