Chronaby PathShift home page

Privacy Policy

Last updated: · Effective:

1. Who we are

Chrona is a calendar-sync service operated by Path Shift LLC, doing business as PathShift (“PathShift”, “we”, “us”), 140 Northwood Drive, Hiawatha, IA 52233. This policy explains what information Chrona handles, why, and the choices you have. It covers chrona.thepathshift.com, app.chrona.thepathshift.com and mcp.chrona.thepathshift.com.

2. Summary

3. What we collect and store

Chrona reads events from the calendars you connect (Google Calendar, Microsoft 365 or Outlook.com, or a published calendar feed link) and writes copies into one primary calendar you choose. You can also choose, per calendar, to have Chrona copy events from calendars you pick into it, optionally only during hours you set. Copies say only “Busy” unless you choose, per calendar, to also copy titles and/or descriptions. Private events are always copied as “Busy”. To do this, we store the following:

Information Chrona stores
InformationWhy we keep itHow it’s protectedHow long we keep it
Account email (from Stripe Checkout)Your account, billing and service emailsEncrypted with a key specific to your accountUntil you delete your account, or 90 days after your subscription ends
Stripe customer and subscription IDsLinking your account to billingStored as plain identifiersSame as your account
Sign-in identity: a one-way hash of your Google or Microsoft account ID, and that account’s emailSigning you inID hashed; email encryptedSame as your account
Connected accounts: email addresses, calendar names, labels you add, provider calendar IDsShowing your dashboard, sending emails about connections, calling Google and MicrosoftEncrypted with a key specific to your accountUntil you disconnect the account or delete your Chrona account
Refresh tokens (the long-lived OAuth permission Google or Microsoft gives Chrona) and calendar feed linksKeeping your calendars in syncEnvelope-encrypted with a key held in a hardware security module (Azure Key Vault). Our public web app can encrypt these but cannot decrypt themDeleted immediately when you disconnect or your subscription ends, except kept for up to 30 days when needed to finish removing copies (see below)
Settings: primary calendar, sync options, time zone, working hoursMaking the product workStored as plain settingsSame as your account
Sync bookkeeping: hashed event-occurrence IDs, IDs of copies, version tags, opaque meeting hashesUpdating and removing copies without duplicatesHashes and opaque IDs only; no event contentRemoved with the copies, the connection or your account
Sign-in sessions (hashed tokens) and sign-in flow stateKeeping you signed in securelyHashedSessions: up to 14 days, or 3 days if idle. Sign-in flow state: 10 minutes. Expired records are purged daily
Claude connector grants: client registrations and hashed refresh tokensGiving Claude the access you approvedTokens hashedAccess tokens last 1 hour; refresh tokens 30 days and are rotated. Revocable in your dashboard; removed when you delete your account
Operational logs (Azure Monitor / Application Insights)Reliability and securityOur application logs record only IDs, counts and error codes, never event titles, descriptions, attendees, email addresses or feed links (checked automatically). The hosting platform’s request logs record which pages were requested30 days
Key Vault audit logsSecurity, including investigating any suspected breachRecord which of our services used which key; no customer data365 days

“Pending cleanup”: if you disconnect a calendar or your subscription ends and you asked us to remove the copies Chrona made, we may need the refresh token for a short time to delete them from your calendar. In that case only, we keep the token for up to 30 days, then delete it.

Information from your sign-in provider

When you sign in with Google or Microsoft, the provider tells us your account ID and email address. The provider may also share your name and profile picture as part of standard sign-in; Chrona does not store them.

Payment information

Stripe, Inc. processes payments. Stripe collects your email, billing address and card details on its own pages. Chrona never sees your card number. Stripe gives us your billing country and card country, which we use only to apply the regional restrictions described below. Stripe is certified as a PCI DSS Level 1 service provider.

Visiting our website

Our website at chrona.thepathshift.com sets no cookies and uses no analytics or tracking. As with any website, our hosting provider (Microsoft Azure) receives technical information such as your IP address to deliver pages and protect the service.

4. What we never store

Event titles, descriptions, attendees, locations and times are never written to Chrona’s storage. They exist only in memory while a sync or a Claude request runs, and they are written only to your own calendars (or returned to Claude when you ask). An automated test checks every table to confirm this. We also never store your card number, your name, or your passwords.

5. How we use information

We use the information above only to:

Product news. We may also email account owners occasional news and offers about Chrona and PathShift. Every one has an unsubscribe link, and unsubscribing doesn’t stop service emails. We send these, and keep support records, using HubSpot. HubSpot receives only your account email (from checkout), your name if you give it to us, and your conversations with us. It never receives data from your Google or Microsoft accounts, including the email addresses of accounts you connect.

We do not use your information for advertising, we do not sell it, and we do not use it to make decisions about credit, lending or eligibility.

6. Google user data

Chrona’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What Google data we access and why

How we limit use of Google data

7. Microsoft user data

We access Microsoft 365 and Outlook.com calendars through Microsoft Graph with calendar-only permissions, never mail or files: Calendars.Read for calendars you copy from, and Calendars.ReadWrite only for the account with your primary calendar, a calendar you chose to receive copies (“Copy events into”), or a calendar where you turned on “Let Claude create events here”. If your organization’s administrator approves Chrona, the administrator approves read-only calendar access; receiving copies on that organization’s calendar also needs its approval for write access. We handle Microsoft data under the same rules as Google data above: we use it only to provide Chrona’s features, never store event content, never use it for advertising, never sell it, and never use it to train AI models.

Calendar feed links

If you add a published calendar feed link (an ICS address), we treat the link like a password: it is encrypted the same way as refresh tokens and deleted when you remove the feed or your subscription ends.

8. Claude and AI

Chrona does not use AI on your data and does not train any AI model.

You can choose to connect Claude, an AI assistant made by Anthropic, PBC, to Chrona. If you do, only when you ask Claude a question about your calendars, Chrona fetches the relevant events live and returns them to Claude. That information is then sent to Anthropic and handled under your own agreement with Anthropic and Anthropic’s Privacy Policy, not this policy.

What Claude receives: when you connect Claude, it receives event titles (and descriptions only when it asks for them) from your primary calendar and from every calendar on your diagram, even calendars you copy into your primary as “Busy”. Private events appear to Claude as “Busy (private)”. Anthropic handles that data under your agreement with Anthropic. On calendars where you turned on “Let Claude create events here”, Claude can ask Chrona to create a time block; these have no attendees, so no invitations are sent.

You can disconnect Claude at any time in your Chrona dashboard, and you can turn off “Let Claude create events here” per calendar.

9. Cookies

Chrona uses only first-party, strictly necessary cookies to keep you signed in and protect sign-in flows. There are no analytics, advertising or social-media cookies, no tracking pixels and no fingerprinting, and our website sets no cookies at all. Stripe sets its own cookies on Stripe-hosted checkout and billing pages. See our Cookie Notice for the full list.

10. How we share information

We do not sell personal information, and we do not share it for cross-context behavioral or targeted advertising.

11. How long we keep information

12. Security

We designed Chrona to protect your data: connections are encrypted with HTTPS; refresh tokens are encrypted with keys held in a hardware security module; personal data is encrypted with a key specific to your account; storage and Key Vault are firewalled to accept connections only from Chrona’s own private network and services; and our services use separate, least-privilege identities. No system is perfectly secure. Read more on our Security page.

13. Your choices

14. U.S. state privacy rights

Depending on where you live, U.S. state privacy laws (such as the California Consumer Privacy Act as amended by the California Privacy Rights Act, and similar laws in other states) may give you rights over your personal information. We honor the requests below for all customers, wherever they live.

Your rights

Categories of information

In the past 12 months, we have collected the categories below, from you, your sign-in and calendar providers, and Stripe, for the purposes in section 5. Retention is in section 11.

Categories of personal information (U.S. state law terms)
CategoryExamples at ChronaDisclosed to
IdentifiersAccount email, connected-account emails, hashed sign-in IDs, Stripe IDsService providers (Microsoft Azure, Stripe)
Commercial informationSubscription status and billing history (held by Stripe)Stripe
Internet or other electronic network activitySession records, application logs (IDs, counts, error codes), platform request logs (which pages were requested)Microsoft Azure
Account access credentialsEncrypted OAuth refresh tokens and calendar feed linksMicrosoft Azure (encrypted storage and key management)
Calendar content (processed in memory only, never stored)Event titles, descriptions, times, attendeesOnly the destinations you choose: your primary calendar, and Anthropic if you ask Claude

How to make a request

Use the self-service export and delete options in your dashboard, or email privacy@thepathshift.com. To protect your account, we verify requests by asking you to sign in or to confirm the request from your account email. We may ask for more information if we can’t verify you.

Authorized agents: someone you authorize can make a request for you. We’ll ask for your signed permission and may ask you to verify your identity directly with us.

Response time: we respond within 45 days. If we need more time, where the law allows, we’ll tell you why and how long.

Appeals: if we decline your request, you can appeal by replying to our decision or emailing privacy@thepathshift.com with “Appeal” in the subject. We’ll respond within 45 days and explain our decision. If you’re not satisfied, you can contact your state attorney general.

Non-discrimination: we won’t deny you service, charge you a different price or give you a different level of service because you exercised your privacy rights.

15. Children

Chrona is a business service for adults (18 and over). It is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has given us information, email privacy@thepathshift.com and we will delete it.

16. Where Chrona is offered and where data is stored

Chrona is hosted, and your data is stored, in the United States (Microsoft Azure, East US 2 region). Chrona is offered only to individuals and organizations in the United States (see our Terms). We use your billing address and card country to enforce this at checkout.

17. Changes to this policy

We’ll post changes here with a new “Last updated” date. For material changes, we’ll email account owners before the changes take effect.

18. Contact us

Privacy questions and requests: privacy@thepathshift.com
Security issues: security@thepathshift.com
Mail: Path Shift LLC, 140 Northwood Drive, Hiawatha, IA 52233