dCal

Privacy Policy

Last updated: October 25, 2026

dCal, calendars for AI agents, is made by Dapta.ai (“we,” “our,” “us”). This policy explains what information we collect when you use dcal.ai, the hosted dCal app (app.dcal.ai) and its MCP connector (mcp.dcal.ai), how we use it and how we protect it. It applies the Dapta.ai Privacy Policy to dCal.

1. Information we collect

Account information. Your name, email address and workspace details when you sign up or sign in.

Connected calendars. When you connect Google Calendar or Microsoft Outlook, dCal keeps the names of your calendars, so you choose which ones to check, and reads when you are busy on them, so it never offers a time that is taken. It also creates, moves or deletes on your calendar the events of the meetings booked through dCal. It does not keep the title, description or guests of your other events. dCal never sees your password, and the access to your calendar is kept by the service that connects it, not in the dCal database.

Bookings. Your event types and the meetings booked with you, with what the person booking enters: their name, email address, time zone, notes, answers to your questions and the guests they add. You own your bookings; we store and process them only to run the service for you.

Connected AI agents. An AI agent you connect to the dCal MCP connector signs in with your account and acts only in workspaces where you are an owner or admin, or uses an API key you create, limited to the access you choose.

Usage data. Information collected automatically through cookies and similar technologies, such as pages visited and the campaign that brought you to the site.

2. How we use your information

3. Google user data and Limited Use

dCal uses Google APIs only to provide or improve the features of our application. When you connect Google Calendar, dCal uses that access to see when you are busy, to list your calendars and to create, move or delete the events of the meetings booked through dCal. From your other events it uses only the times you are busy; it does not keep their contents.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We do not sell Google user data, we do not use it for advertising, and we do not use it to develop, improve or train generalized AI or ML models. We do not share or transfer it to third parties, except as needed to provide the feature or as required by law.

4. Data retention and deletion

5. Disclosure of your information

We do not sell your information. We share it with third parties only with your consent, to comply with legal obligations, to protect our rights or property, or as part of a merger, acquisition or sale of assets.

When someone books with you, dCal writes the meeting to the calendar you connected, emails the person booking their confirmation, and sends the booking to the integrations you connect (for example a CRM or a webhook), on your instruction.

When you connect an AI agent, what it reads in dCal goes to the agent’s application (for example Claude, ChatGPT or Cursor), on your instruction; that application’s own policy covers what it does with it.

6. Security

Private data is stored encrypted, and our databases are backed up daily. API keys are stored only as a hash.

7. Open source and self-hosting

dCal is open source under the MIT license. If you run your own copy, your data stays on your infrastructure and this policy does not cover it.

8. Changes to this policy

We may update this policy. If the changes are significant, we will tell you on this site or by other means before they take effect.

9. Contact

Questions about this policy: [email protected].