Chronaby PathShift home page

Data Processing Addendum

Last updated: · Effective: [EFFECTIVE DATE]

This Data Processing Addendum (“DPA”) is between Path Shift LLC, doing business as PathShift (“PathShift”) and the business customer that has accepted the Chrona Terms of Service (“Customer”, “you”). It is written for U.S. privacy laws.

1. Scope and how this addendum applies

This DPA applies when PathShift processes Customer Personal Data to provide Chrona. It is incorporated by reference into the Terms for every customer that wants it; no signature is needed. If you need a signed copy for your records, email privacy@thepathshift.com.

2. Definitions

3. Roles of the parties

You are the business or controller of Customer Personal Data. PathShift is your service provider or processor. You are responsible for having the rights and permissions needed to connect calendars to Chrona and to have PathShift process the data in them, including any obligations you owe to your clients or employer. PathShift is an independent business or controller only for the limited account and billing information it needs to run its own business (for example, tax and accounting records), as described in its Privacy Policy.

4. Processing on your instructions

PathShift will process Customer Personal Data only on your documented instructions. Your instructions are: the Terms and this DPA; the settings you choose in Chrona (such as which calendars to connect and whether to copy titles or descriptions); and the requests you make through the Claude connector. PathShift will tell you if it believes an instruction breaks Data Protection Laws, and may decline to follow it. If the law requires PathShift to process data in some other way, it will tell you first unless the law prohibits that.

5. Service provider commitments (CCPA/CPRA)

PathShift processes Customer Personal Data only for the limited and specified business purpose of providing, securing and supporting Chrona as described in the Terms. PathShift will not:

PathShift will comply with the obligations that apply to it under Data Protection Laws and give Customer Personal Data the level of privacy protection they require. PathShift will tell you if it decides it can no longer meet these obligations. You may take reasonable and appropriate steps to make sure PathShift uses Customer Personal Data in line with your obligations, and, after notice, to stop and fix any unauthorized use. PathShift certifies that it understands and will comply with the restrictions in this section.

6. Subprocessors

You authorize PathShift to use the subprocessors listed on our subprocessors page. PathShift will have a written agreement with each subprocessor with data-protection obligations at least as protective as this DPA, and is responsible for its subprocessors’ performance.

PathShift will update that page and email account owners at least 30 days [COUNSEL: confirm notice period] before adding a subprocessor that processes Customer Personal Data. You may object on reasonable data-protection grounds by emailing privacy@thepathshift.com within that notice period. We will discuss your concerns in good faith. If we can’t resolve them, you may cancel your subscription [COUNSEL: refund of prepaid fees for the unused period, if any].

Google, Microsoft (as provider of your own calendar accounts), Anthropic and calendar-feed hosts are not PathShift’s subprocessors: you direct Chrona to connect to them under your own agreements with them.

7. Confidentiality of personnel

PathShift will make sure that anyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality and has access only as needed to provide, secure or support Chrona.

8. Security

PathShift will maintain reasonable technical and organizational measures designed to protect Customer Personal Data, appropriate to the nature of the data, including the measures in Annex A. PathShift may update these measures as long as the overall level of protection does not decrease.

9. Help with consumer requests and assessments

10. Security incident notification

PathShift will notify you without undue delay after confirming a Security Incident, with a target of within 72 hours after confirmation. The notice will go to your account email and will describe, as far as known at the time, what happened, the data involved, the steps PathShift is taking, and a contact for more information. PathShift will update you as it learns more, take reasonable steps to contain and fix the incident, and reasonably cooperate with you on any notices you must give. Notice of a Security Incident is not an admission of fault.

11. Deletion and return of data

Event copies in your own calendars are kept or removed as you choose when you cancel or delete your account.

12. Audits and information

PathShift will make available information reasonably necessary to show that it complies with this DPA. Audits will take the form of PathShift’s written answers to your reasonable security and privacy questionnaires, together with relevant documentation, no more than once a year unless a Security Incident or a regulator requires more. PathShift does not offer on-site audits at this time and does not currently hold SOC 2 or ISO 27001 certification. Information PathShift provides under this section is PathShift’s confidential information.

13. Data location and restricted regions

PathShift and its subprocessors store Customer Personal Data in the United States. [BEN: confirm whether Stripe or the mailbox provider processes any Customer Personal Data outside the United States, and add a subprocessor-specific note if so] Chrona is not offered in the European Union, the European Economic Area, the United Kingdom or Switzerland, so this DPA does not include terms for those laws, such as standard contractual clauses.

14. Liability and order of precedence

Each party’s liability under this DPA is subject to the limitations and exclusions in the Terms. If this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA controls. This DPA ends when PathShift no longer processes Customer Personal Data for you.

Annex A: Security measures

Annex B: Details of processing

Details of processing
ItemDescription
Subject matterProviding Chrona: calendar sync and the optional Claude connector
DurationThe term of your subscription, plus the deletion periods in section 11
Nature and purposeReading events from calendars you connect; writing copies to your primary calendar; returning events to Claude and creating time blocks when you ask; account, billing, security and support
Categories of dataAccount and connected-account email addresses; hashed sign-in identifiers; calendar names, labels and IDs; OAuth refresh tokens and calendar feed links (encrypted); settings; sync bookkeeping hashes; session records; operational logs (IDs, counts, error codes). In memory only, never stored: event titles, descriptions, attendees, locations and times
Categories of peopleYou and your users; people whose names or details appear in events on the calendars you connect (for example meeting attendees)
Sensitive dataNot intended. Calendars may incidentally contain it; event content is processed only in memory and written only to your own calendars
LocationUnited States