Enterprise Data Protection

Data Processing Addendum (DPA)

Governing the processing of personal data under India’s Digital Personal Data Protection (DPDP) Act 2023 and the General Data Protection Regulation (GDPR).

Last Updated: November 2026 • Effective Date: January 1, 2024

Payments via Razorpay• PCI-DSS Level 1
ISO/IEC 27001 certified
OAuth 2.0 Restricted• Google & Outlook Sync
Built for India's DPDP Act• Booking data stored in Mumbai, India
Payments via Razorpay• PCI-DSS Level 1
ISO/IEC 27001 certified
OAuth 2.0 Restricted• Google & Outlook Sync
Built for India's DPDP Act• Booking data stored in Mumbai, India
Payments via Razorpay• PCI-DSS Level 1
ISO/IEC 27001 certified
OAuth 2.0 Restricted• Google & Outlook Sync
Built for India's DPDP Act• Booking data stored in Mumbai, India
Payments via Razorpay• PCI-DSS Level 1
ISO/IEC 27001 certified
OAuth 2.0 Restricted• Google & Outlook Sync
Built for India's DPDP Act• Booking data stored in Mumbai, India

1. Scope & Applicability

This Data Processing Addendum ("DPA") supplements the Terms of Service and Privacy Policy between Book Your Calendar ("Data Processor") and the organization or individual subscribing to our scheduling services ("Customer" or "Data Fiduciary").

This DPA applies to all processing of Personal Data carried out by Book Your Calendar on behalf of Customer in connection with scheduling appointments, consultations, payments, and calendar synchronization.

2. Data Location

Where we keep Customer data, in line with the Digital Personal Data Protection Act, 2023 (DPDP Act):

Booking data: Your booking data is stored in Mumbai, India.
Other providers: Some sub-processors work outside India. The sub-processors list shows where each one processes data.
Data in Transit: 100% of network traffic is encrypted via TLS 1.3 / HTTPS.

3. Security & Confidentiality Measures

  • ISO/IEC 27001 certified: Ethrise Solutions, the company behind Book Your Calendar, is ISO/IEC 27001 certified. The certification does not cover our vendors, such as Razorpay or Google, which hold their own certifications.
  • Payment Security: Payments are processed by Razorpay or, when a host connects it, PayU. Each says it is PCI-DSS compliant. Book Your Calendar does not store card numbers or other card details.
  • Calendar Access Scopes: We request only the OAuth 2.0 access each feature needs from Google Workspace and Microsoft Graph: basic sign-in scopes, the calendar access you grant and Google Docs or Drive access only if you connect them. Stored tokens are encrypted.
  • Role-Based Access Control: Strict least-privilege administrative access for internal staff.
  • Personal Data Breach: Book Your Calendar will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer's data, with the details Customer needs to meet its own duties, including reporting to the Data Protection Board of India within 72 hours where applicable.

4. Sub-processors

Customer provides general authorization for Book Your Calendar to engage sub-processors for hosting, the database, sign-in, payments, email and WhatsApp messages, calendar and video links, file storage, analytics and the integrations Customer connects.

A complete and current list of authorized sub-processors is publicly maintained at /sub-processors. Book Your Calendar will notify customers at least 30 days prior to onboarding any new infrastructure sub-processor.

The list shows each sub-processor’s purpose, the data it handles and where it processes data. It marks the ones that process data outside India.

5. Data Principal Rights & Retention

Under DPDP Act Sections 11-13 and GDPR Articles 15-22, Data Principals possess the statutory right to access, correct, complete, or request erasure of their personal data.

Retention Period: Active account booking histories are retained for the duration of the subscription. Upon account closure, end of service or verified deletion request, personal data is permanently purged from active production databases within 30 days, except records we must keep by law (invoices and payment records, for the period the law requires).

Annex A. AI Notetaker processing details

This annex applies only when Customer turns on AI Notetaker. It adds to sections 1 to 5 and does not replace them.

Roles
For the people in a recorded meeting, Customer is the Data Fiduciary and Book Your Calendar is the Data Processor, acting only on Customer’s instructions given through the AI Notetaker settings.
Subject matter and purpose
Recording the audio of Google Meet or Zoom calls Customer chooses, after the client agrees at booking, to produce a transcript, a summary and a to-do list for Customer. No other purpose, no advertising and no training of AI models by Book Your Calendar.
Nature of processing
Joining the call with a notetaker bot, receiving the audio, speech-to-text, AI note writing, storage, display to Customer and, if Customer connects it, saving a Google Doc to Customer’s Google Drive.
Data Principals
Customer’s clients and the other people in the recorded call.
Personal data
Call audio (audio only, no video), transcript, notes, meeting title, date and time, meeting link and the names people use in the call.
Sensitive data and children
Hosts must not use the notetaker for health or therapy sessions, or when anyone under 18 attends, even with a parent’s or guardian’s consent. We block it for events in those categories and for events where the host says someone under 18 attends. Customer must not instruct processing of children’s data or health data through AI Notetaker.
Duration
Audio: until it is transcribed, and within about a day if processing fails. Transcripts and notes: until Customer deletes them, and straight away when Customer’s account is deleted. On account deletion Book Your Calendar also asks its meeting and transcription providers to delete anything they still hold, and keeps trying for up to 30 days, and tries to delete the copies saved to Customer’s Google Drive. To delete those copies, it keeps Customer’s encrypted Google Drive access for up to 30 days after the account is deleted and uses it for nothing else. If anyone types /stop or Customer removes the notetaker, no recording, transcript or notes from that call are kept.
Customer’s instructions and duties
Customer tells participants about the recording, has a lawful basis and any consent needed, stops recording when someone objects and does not use AI Notetaker where recording is unlawful or not allowed.
Withdrawal and requests
A client’s “Withdraw and delete” link deletes the transcript and notes from that session and any copy saved to Customer’s Google Drive. Book Your Calendar helps Customer answer Data Principal requests about AI Notetaker data.
Transfers outside India
Meeting audio and transcripts leave India for these steps (including Japan and the United States), as section 16 of the DPDP Act, 2023 allows: meeting media goes to Japan (notetaker bot), with Recall.ai’s logs, account records and the meeting link possibly held in the United States; transcripts go to the United States (notes); The table below lists each provider.

AI Notetaker sub-processors

Customer authorises these sub-processors for AI Notetaker. They are also listed on the sub-processors page, with what each one keeps and for how long. The 30-day notice in section 4 applies to them. Sub-processors.

  • Recall.ai (Hyperdoc Inc.): AI Notetaker meeting bot: joins the Google Meet or Zoom call the host chose and passes the audio on. Meeting media in Tokyo, Japan (Recall.ai’s Asia region). Recall.ai’s logs and account records may be held in the United States.
  • Google Cloud (Mumbai, India): Runs our AI Notetaker audio receiver, which takes the audio from the meeting bot and sends it for transcription. Mumbai, India
  • Sarvam AI (Axonwise Private Limited): AI Notetaker speech-to-text, in India. India
  • Anthropic, PBC: AI Notetaker notes: writes the summary and to-do list from the transcript. Notes are written by Anthropic (Claude), processed and stored in the United States only.
  • Google LLC (Google Drive): Saves AI Notetaker notes as a Google Doc in the host’s own Drive, only if the host connects Drive. The Doc sits in the host’s Google account, under the host’s own terms with Google. Access is limited to files Book Your Calendar creates (drive.file). Depends on the host’s Google account.

6. Grievance Officer (DPDP Act)

Send data protection complaints to our grievance officer.

Grievance officer: Gaurav Bajaj, grievance@bookyourcalendar.com. We acknowledge within 2 business days and respond within 30 days.