> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/security-and-privacy.md).

# Security and privacy

How dCal protects your workspace and your guests: what is encrypted or hashed, how manage links and API keys work, who can see what, what guest data is stored and what never is, tracking tags on booki

dCal stores what a booking needs and little else. This page explains what is kept about your guests, how your credentials and the links you share are protected, who in your workspace can see what, what you can delete yourself, and how to report a security problem.

***

## Encrypted, hashed or shown once

Every credential in dCal is either encrypted or kept only as a one-way hash, and none of them can be read back from the dashboard. One-off invite links are the exception, on purpose: each one can only book your event once, so dCal keeps it as is and you can copy it again while it is live.

| Secret                 | How dCal keeps it                                                                            | When you see it                                                                            |
| ---------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| HubSpot access token   | Encrypted (AES-256-GCM) and tied to your workspace. Checked with HubSpot before it is saved. | Never again after you paste it. The **Integrations** tab shows only its last 4 characters. |
| Webhook signing secret | Encrypted (AES-256-GCM) and tied to its webhook. Decrypted only to sign a delivery.          | Once, when you create the webhook.                                                         |
| API key                | Only a one-way hash (SHA-256), plus its prefix and last 4 characters.                        | Once, when you create the key.                                                             |
| A guest's manage link  | A random 256-bit token, stored only as a hash.                                               | In the guest's emails and on their confirmation screen.                                    |
| A one-off invite link  | A random 256-bit token, kept as is. Stops working after one booking or when you revoke it.   | In the event's **One-off invite links** list, to you.                                      |

Because each encrypted secret is tied to its workspace, a copy moved into another workspace cannot be decrypted there.

***

## Manage links

Every guest gets a link to manage their booking, in their emails and on the confirmation screen. Whoever holds that link can see the booking and reschedule or cancel it, so it works like a key to that one booking.

* The token in the link is random and long, and dCal stores only a hash of it.
* Each reschedule creates a new link. Links in older emails stop working and show *This link is no longer active*.
* Your copy of the booking emails never carries the guest's manage link, and neither does the meeting dCal writes to HubSpot.
* The manage page is never indexed by search engines, and other websites cannot show it inside a frame.
* Manage links live on `book.dcal.ai`, with your booking pages, apart from the dashboard. See [Booking pages on their own address](#booking-pages-on-their-own-address).

***

## Who can see what

A workspace is the privacy boundary. Everything you create, from events and schedules to bookings, settings, keys and webhooks, belongs to one workspace, and every dashboard request is limited to a workspace the signed-in person is an active member of: their own, or one they joined by invitation. A request for any other workspace, or for one whose invitation they have not accepted yet, is refused. An AI agent signed in by someone who is an owner or admin in several workspaces can name one of those, and only those.

| Role       | Can see and do                                                                                                                                                                                                                                                                                                                                                                       |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Member** | Their own events, schedules, bookings and connected calendars, and their own booking page.                                                                                                                                                                                                                                                                                           |
| **Admin**  | Everything a member can, on everyone's events, schedules and bookings, plus members (except owners), teams, the brand kit, the Dapta branding switch, the custom link, the **Notifications** and **Integrations** tabs, each event's **Tracking and pixels**, and the agent pages: **Connect your agent**, **Tools** and **API and webhooks** (API keys, webhooks and the API docs). |
| **Owner**  | Everything an admin can, plus transferring ownership and acting on other owners.                                                                                                                                                                                                                                                                                                     |

The **Bookings** page lists the bookings you host. API keys work for one workspace only: a booking outside it answers as if it did not exist. An AI agent signed in by an owner or admin acts with that person's access, and stops at its next request once they are no longer an owner or admin. See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md).

***

## What dCal stores about your guests

| Stored with a booking | Detail                                                                                                                                                                                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name and email        | From the booking form.                                                                                                                                                                                                                                          |
| Time zone             | The time zone the guest booked in, usually the one their browser reports.                                                                                                                                                                                       |
| Phone                 | Only when your event asks for it.                                                                                                                                                                                                                               |
| Notes                 | Optional, from the booking form.                                                                                                                                                                                                                                |
| Answers               | Their answers to your booking questions.                                                                                                                                                                                                                        |
| Other guests          | Email addresses entered in a guests question, or added through the API.                                                                                                                                                                                         |
| Language              | The language of the booking page they used. Their emails follow it.                                                                                                                                                                                             |
| Campaign (UTMs)       | The `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content` of the booking page's address or, on an embedded page, of the page that frames it. Only those five, each up to 128 characters; click IDs such as `gclid` or `fbclid` are not kept. |

What dCal does not store:

* **No IP address.** The rate limiter counts requests per address, but that counter lives only in memory and is never written next to a booking.
* **No browser or device details.** No user agent, no screen size, no operating system.
* **Nothing about the request in the logs.** Request logs record the route, the status and the timing, never query strings, bodies, headers, addresses, emails or names.

dCal sets no cookie of its own on `book.dcal.ai`, where your booking pages live; tracking tags you add to an event follow their vendor's own rules (see [Tracking tags on your booking pages](#tracking-tags-on-your-booking-pages)). One short-lived cookie exists on `app.dcal.ai`, where people sign in: a visitor who arrives there with campaign parameters (`utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`, `gclid` or `fbclid`) or from another website gets one cookie that holds only those values and the address of the site they came from. It lasts 10 minutes, scripts on the page cannot read it, and it is used only if that visitor signs up for dCal themselves.

***

## Product analytics

dCal can send product analytics, a record of how the product is used, to an analytics service. It is off unless whoever runs the deployment sets an analytics provider and its key; with nothing set, no analytics script loads and nothing is sent. When it is on:

* **Hosts** who are signed in are identified by their email, with their role and their workspace. dCal records which dashboard pages they open, without the part of the address after `?`, a few clicks, and steps such as signing up, connecting a calendar, setting hours, publishing an event and receiving a booking.
* **Guests** on booking pages are never identified: no profile, and nothing is stored on their device. Only a few steps are recorded on profile, event and team pages: the page opened, a day picked, a time picked, the form sent, the booking confirmed, and a click on the **Made with dCal.ai by Dapta** badge or the free-calendar invitation. Never their name, email, phone or answers. Manage pages and one-off invite links record nothing.
* **Never recorded:** session recordings, heatmaps, surveys or automatic click capture. Addresses lose everything after `?` and `#`, and campaign tags that look like personal data, such as an email, a phone number or a web address, are withheld.
* The analytics service still receives each visitor's IP address and browser details with every request.

A link that carries `?ph_id=` and opens the sign-in or the dashboard also leaves a 10-minute cookie, even when analytics is off. Nothing reads it then, and booking pages never set it.

***

## What leaves dCal

Some data leaves dCal on purpose, to the places you connect:

| Destination                                                                              | What is sent                                                                                                                                                                                                                                                                                                                                     | When                                                                                                                            |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| Your connected calendar                                                                  | An event with the meeting's title and time, the meeting link when there is one, and the guest as an attendee. Your calendar does not email the guest about it, except in the cases in [The calendar invite](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#the-calendar-invite).                                                      | When a booking is accepted. Moved on reschedule, removed on cancel.                                                             |
| HubSpot, if connected                                                                    | A contact (email, name, and the answers and campaign UTMs you map) and a meeting with the time, the host, the answers and the booking's campaign (UTMs) when it has one. Never the manage link.                                                                                                                                                  | When a booking is accepted. Updated on reschedule and cancel.                                                                   |
| Your webhooks, if any                                                                    | The event name, the booking ID, its status, times, title, its campaign (UTMs) when it has one and, on a cancellation, the reason. Never the guest's name, email or answers.                                                                                                                                                                      | On each booking change you subscribed to.                                                                                       |
| A website that embeds your booking page                                                  | The steps of a booking: the event viewed, the day and the time picked, and after the booking, the booking ID, its start time and the event's slug. No name or email.                                                                                                                                                                             | Only inside an embed.                                                                                                           |
| The tracking tools you set on an event                                                   | The page view, the day and time picked and the booking, with the event's slug, length, whether it is personal or team, the picked start and whether the booking is accepted or pending. Never the guest's name, email, answers or the booking ID.                                                                                                | Only on that event's booking page. See [Tracking tags on your booking pages](#tracking-tags-on-your-booking-pages).             |
| Your own page, if an event has **Redirect after booking**                                | The address you set, only to the guest who booked. With **Booking details on that page**, it also carries the event, its start and end time, the booking's status, the host's name and the campaign (UTMs). The guest's name and email are added only if you pick the option that includes them. Never the answers, the booking ID or its title. | Right after a booking on that event's page.                                                                                     |
| An AI agent you connect over MCP, through dCal's MCP server at `https://mcp.dcal.ai/mcp` | With an API key, what the key's access allows; signed in, what its owner or admin can reach through the tools. That means event types, open times and bookings. Text a guest typed arrives cleaned and marked as untrusted, and booking lists carry no names, notes or answers.                                                                  | Each time the assistant calls a tool. See [Connect an AI assistant (MCP)](https://docs.dapta.ai/dcal/developers/mcp-server.md). |
| Emails                                                                                   | The guest's copy has no answers, no notes and no other guests' details. Your copy has the guest's details and answers.                                                                                                                                                                                                                           | On each booking change.                                                                                                         |

***

## Tracking tags on your booking pages

Owners and admins can add tracking tags to an event, in **CRM Connection** > **Tracking and pixels**: a Meta Pixel, a PostHog project, a Google Tag Manager container, a Google Analytics 4 measurement ID or the HubSpot tracking code. See [Tracking and pixels](https://docs.dapta.ai/dcal/events/event-settings.md#tracking-and-pixels).

* **Where they load.** Only on that event's booking page, embedded or not: its personal or team booking page and its one-off links. Never in your dashboard, the design studio's preview, the event editor's draft booking preview, the guest's manage page, or your profile and team pages. A tag loads only when its ID is set: with none set, the page makes no request to any of those vendors.
* **What dCal's events send.** Each tool hears the page view, the day and the time picked, and the booking, with the event's details and nothing about the guest: never their name, email or answers, and never the booking ID. Meta's own automatic events stay off.
* **What a vendor can do on its own.** Some features you turn on in your vendor account can read more than dCal sends. With Meta's automatic advanced matching or HubSpot's collected forms on, the vendor can read the booking form, and a Google Tag Manager container runs whatever its owner adds to it. Those features are your choice and your responsibility.

***

## Booking pages on their own address

Your booking pages, team pages, one-off links and your guests' manage pages live on `https://book.dcal.ai`. The dashboard and the sign-in stay on `https://app.dcal.ai`. Because a tag can run code its owner adds, the two never share an address: dCal sets no cookie on `book.dcal.ai`, so nothing that runs on a booking page can reach a signed-in session.

***

## Rate limits and abuse

* **The public booking endpoints are throttled per visitor.** Each API server allows a visitor a burst of 60 requests that refills at 1 per second. Past it, the API answers `429` with a `Retry-After` hint. A real guest never comes close.
* **AI agents are throttled per key or sign-in.** dCal's MCP server at `https://mcp.dcal.ai/mcp` gives each key, and each signed-in person, bursts of 30 read calls, refilling at 1 per second, and 10 calls that change bookings (hold, book, move, confirm, decline or cancel), refilling at 1 every 5 seconds. Calls with neither, and calls from a sign-in that reaches no workspace yet, are counted per address. Keys and sign-ins are accepted only in the `Authorization` header, never in a URL. See [MCP tools reference](https://docs.dapta.ai/dcal/developers/mcp-tools.md).
* **Held times are capped.** A visitor who picks a time holds it for 10 minutes while they fill in the form, an AI agent can hold one for about 10 minutes, and one host can have at most 10 held times at once.
* **Double bookings are refused.** A booking can never overlap another accepted or pending booking of the same host: the database itself refuses the second one.
* **One booking per person** is an optional rule per event that allows each email address one upcoming booking on it. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).
* **Webhook addresses are checked.** A webhook must use `https://`, and an address that points to a private, internal or reserved network is refused when you add it and again before every delivery. Redirects are never followed.

***

## Pages other websites can show

Your public booking pages can be shown inside any website, which is what makes [embedding](https://docs.dapta.ai/dcal/share/embed.md) work. The dashboard, the sign-in screens and the guests' manage page cannot be shown inside another website.

***

## Signing out

**Sign out**, in the menu of your profile button at the bottom of the left menu, ends your dCal session. Your other Dapta products stay signed in. The next time you click **Continue with Dapta**, the Dapta sign-in screen asks which account to use. A dCal session otherwise lasts 30 days.

To disconnect an AI agent you signed in, remove the dCal connector in that app.

***

## Deleting data

Nothing is deleted automatically. Here is what you can remove yourself today, and what stays:

| You do                                                                | What is removed                                                                                     | What stays                                                                                                       |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Cancel a booking (**Bookings** > **Cancel**)                          | The calendar event, and any reminders still to be sent. The guest and you get a cancellation email. | The booking itself, marked **cancelled**, with the guest's details.                                              |
| Delete an event (**Events** > **Delete**)                             | The event, its hosts and its calendar choices. Its public page stops opening.                       | Its bookings, which are not cancelled. Cancel them first if needed.                                              |
| Disconnect a calendar (**Calendars** > **Disconnect**)                | The connection in dCal. dCal stops checking it and writing to it.                                   | Events already in your calendar, and your bookings. Nothing is deleted in your calendar.                         |
| Disconnect HubSpot (**Settings** > **Integrations** > **Disconnect**) | The stored token.                                                                                   | Everything already in HubSpot, which dCal never deletes. Your answer mappings, which come back if you reconnect. |
| Delete a webhook                                                      | The webhook and its signing secret.                                                                 | Whatever your endpoint already received.                                                                         |
| Revoke an API key                                                     | The key stops working.                                                                              | Its row, marked **revoked**.                                                                                     |
| Remove a member (**Settings** > **Members**)                          | Their schedules, their own events, their connected calendars and their team places.                 | Their past bookings.                                                                                             |

What you cannot do from the dashboard today:

* Delete a single booking, or the details a guest entered on it.
* Delete your whole workspace or account.

For either, or for any request about a guest's personal data, write to <support@daptatech.com>.

> **⚠️ Note:** Deleting in dCal never reaches copies that already left: an event in your calendar, a contact in HubSpot, or a payload your webhook endpoint stored. Delete those where they live.

***

## Reporting a security issue

If you think you found a vulnerability in dCal, do not open a public GitHub issue. Report it privately, in one of two ways:

* Write to `security@dapta.ai`.
* Open a private security advisory on the [GitHub repository](https://github.com/Dapta-Tech/dapta-calendars-slate): **Security** tab > **Report a vulnerability**.

Include a description, the impact, the steps to reproduce it (a proof of concept if you can) and the version or commit affected. The team aims to acknowledge a report within 3 business days and credits you in the advisory unless you prefer to stay anonymous.

If you run your own copy: until a 1.0 release, only the latest `main` receives security fixes. See [Self-hosting](https://docs.dapta.ai/dcal/developers/self-hosting.md).

## Related

* [API keys](https://docs.dapta.ai/dcal/developers/api-keys.md): create, scope and revoke keys.
* [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md): addresses, signing secrets and deliveries.
* [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md): who can do what in a workspace.
* [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md): what dCal writes to your CRM.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/security-and-privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
