On this page
What this addendum covers
This Data Processing Addendum ("DPA") is between DUDECODE LLC ("Calday") and the business that uses Calday ("Customer"). It is part of the Calday Terms of Service. If the two conflict on personal data, this DPA wins.
It covers personal data that Customer puts in Calday about its own clients, team members and contacts, and that Calday processes to provide the service ("Customer Personal Data"). Annex 1 describes it.
It doesn't cover data Calday collects about Customer itself, such as account and billing details. The Privacy Policy covers that.
Roles
For Customer Personal Data, Customer decides why and how it is used. Calday processes it only for Customer. Where US state privacy laws apply, Calday acts as Customer's "service provider" or "processor".
Customer's instructions
Calday processes Customer Personal Data only:
- to provide, secure, support and fix Calday,
- as Customer directs through its use of Calday and its settings,
- as the law requires. If the law requires other processing, Calday tells Customer first unless the law forbids it.
Calday doesn't:
- sell or share Customer Personal Data,
- use it for its own advertising or marketing,
- combine it with data from other sources, except as needed to provide Calday,
- keep or use it for any purpose outside this DPA.
Calday may use de-identified, aggregated data (for example, total bookings across all customers) to run and improve Calday, as long as it can't be linked back to Customer or any person.
Customer is responsible for having the right to collect Customer Personal Data and give it to Calday, including any notices and consents its clients need.
Confidentiality
Only Calday staff and contractors who need Customer Personal Data to do their work can access it. Each of them is bound by a duty of confidentiality.
Security
Calday keeps reasonable technical and organisational measures to protect Customer Personal Data, appropriate to the risk. Annex 3 lists them. Calday may improve these measures over time but won't make them less protective.
Subprocessors
Customer allows Calday to use the subprocessors listed in Annex 2. Calday publishes the current list at calday.com/subprocessors.
Before adding or replacing a subprocessor, Calday updates the list and notifies Customer at least 30 days in advance. Customer can object by email within that time, for a reasonable data protection reason. Calday and Customer will then try to find a solution. If they can't, Customer can close its account and get a refund of any prepaid fees for the unused period.
Calday puts data protection terms in place with each subprocessor that protect Customer Personal Data at least as well as this DPA. Calday stays responsible for its subprocessors' work.
Security breaches
If Calday confirms a breach that affects Customer Personal Data, it notifies Customer within 72 hours. The notice includes what Calday knows at the time: what happened, what data and how many people are affected, and what Calday is doing about it. Calday sends updates as it learns more.
Calday helps Customer meet any duty Customer has to notify its clients or a regulator. Telling Customer about a breach doesn't mean Calday admits fault.
Helping with requests from Customer's clients
If one of Customer's clients asks Calday to see, correct or delete their data, Calday tells them to contact Customer and doesn't answer the request itself, unless the law requires it.
Customer can see, edit and delete its clients' data in the app. For a copy of the data, Customer emails support@calday.com. Where Customer can't do something itself, Calday helps within a reasonable time.
Calday also gives reasonable help with privacy assessments and questions from regulators about Customer Personal Data.
Audits
Once a year, Customer can ask Calday to complete a reasonable security questionnaire. Calday answers within 30 days.
If a regulator requires more, or after a breach, Customer can ask for a remote review on at least 30 days' notice, at Customer's cost. Calday may first ask Customer to sign a confidentiality agreement. On-site audits aren't included.
Where data is stored
Calday stores Customer Personal Data in the United States. If this changes, Calday notifies Customer in the same way as for a new subprocessor.
Deleting data
After Customer's account closes, Calday deletes Customer Personal Data within 90 days, including backups. Before closing its account, Customer can ask Calday for a copy of its data. On request, Calday confirms the deletion in writing.
Calday may keep data longer only where the law requires it, and then keeps protecting it under this DPA.
Liability and term
Each party's liability under this DPA is subject to the limits in the Terms of Service.
This DPA applies for as long as Calday processes Customer Personal Data.
Annex 1: Processing details
Whose data. Customer's clients, Customer's team members, and other contacts Customer adds.
Types of data. Names, emails, phone numbers, bookings and booking history, services, notes, messages, payment status and amounts. Card details stay with Stripe.
Sensitive data. Not intended. The Terms of Service ban health records, card numbers and government ID numbers.
Purpose. Scheduling, booking, client management, reminders and payments for Customer.
How long. While the account is open, then deleted within 90 days.
Annex 2: Subprocessors
Amazon Web Services (AWS). Hosting, database, backups and email sending. All Customer Personal Data. United States.
Stripe. Payment processing. Client names, emails and payment details. United States.
Amplitude. Product analytics. Client names, emails and app IDs, and usage events. United States.
Annex 3: Security measures
Calday has these measures in place:
- Data is encrypted in transit (HTTPS) and at rest on AWS.
- Automated, regular backups.
- Only people who need production data to do their work can access it.