Privacy Policy
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
- Chrona reads events from calendars you connect and copies them into the calendar you choose as your primary, and, if you choose, into other calendars you pick (for example, Busy blocks on a client’s calendar during that client’s working hours). By default, copies say only “Busy”.
- We never store event titles, descriptions, attendees, locations or times. They exist only in memory while a sync or Claude request runs.
- We don’t sell or share personal information, we don’t show ads, we don’t use AI on your data, and we don’t train any AI model.
- We use only strictly necessary cookies. No analytics or tracking.
- You can export or delete your data yourself, any time, in your dashboard.
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 | Why we keep it | How it’s protected | How long we keep it |
|---|---|---|---|
| Account email (from Stripe Checkout) | Your account, billing and service emails | Encrypted with a key specific to your account | Until you delete your account, or 90 days after your subscription ends |
| Stripe customer and subscription IDs | Linking your account to billing | Stored as plain identifiers | Same as your account |
| Sign-in identity: a one-way hash of your Google or Microsoft account ID, and that account’s email | Signing you in | ID hashed; email encrypted | Same as your account |
| Connected accounts: email addresses, calendar names, labels you add, provider calendar IDs | Showing your dashboard, sending emails about connections, calling Google and Microsoft | Encrypted with a key specific to your account | Until you disconnect the account or delete your Chrona account |
| Refresh tokens (the long-lived OAuth permission Google or Microsoft gives Chrona) and calendar feed links | Keeping your calendars in sync | Envelope-encrypted with a key held in a hardware security module (Azure Key Vault). Our public web app can encrypt these but cannot decrypt them | Deleted 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 hours | Making the product work | Stored as plain settings | Same as your account |
| Sync bookkeeping: hashed event-occurrence IDs, IDs of copies, version tags, opaque meeting hashes | Updating and removing copies without duplicates | Hashes and opaque IDs only; no event content | Removed with the copies, the connection or your account |
| Sign-in sessions (hashed tokens) and sign-in flow state | Keeping you signed in securely | Hashed | Sessions: 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 tokens | Giving Claude the access you approved | Tokens hashed | Access 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 security | Our 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 requested | 30 days |
| Key Vault audit logs | Security, including investigating any suspected breach | Record which of our services used which key; no customer data | 365 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:
- provide Chrona: sign you in, sync your calendars, show your dashboard and answer Claude requests you make;
- send service emails, such as trial reminders, receipts, connection problems, price-change notices and security notices, and, unless you unsubscribe, occasional product news;
- bill you and enforce regional and sanctions restrictions;
- keep Chrona secure and reliable, and prevent abuse; and
- comply with law and enforce our Terms.
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
- Sign-in (openid, email): to sign you in and identify your Google account.
- Calendar list, read-only (
calendar.calendarlist.readonly): to list your calendars so you can choose which to sync and which is your primary. We store calendar names and IDs, encrypted. - Events, read-only (
calendar.events.readonly): to read events and copy them into your primary calendar, and to answer your Claude requests. Event content is never stored. - Events on calendars you own (
calendar.events.owned), requested 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”: to create, update and delete the copies Chrona makes, and to create a time block when you ask Claude to. Chrona only changes or deletes events it created. It never edits or deletes your own events.
How we limit use of Google data
- We use Google user data only to provide and improve the user-facing features of Chrona that you use: copying availability (and, if you choose, titles and descriptions) into your primary calendar, and answering your requests through Claude.
- We transfer Google user data to others only: (a) as needed to provide those features, at your direction (for example, writing copies to your Microsoft primary calendar, or returning events to Claude, and so to Anthropic, when you ask); (b) to our service provider Microsoft Azure, which hosts and processes it on our behalf under contract; (c) for security purposes, such as investigating abuse; (d) to comply with applicable law; or (e) as part of a merger, acquisition or sale of assets, with notice to you.
- We do not use or transfer Google user data to serve ads, including personalized, retargeted or interest-based advertising.
- We do not sell Google user data.
- We do not allow humans to read Google user data unless: you give us your affirmative agreement for specific data; it is necessary for security purposes, such as investigating abuse; it is required to comply with applicable law; or the data is aggregated and anonymized and used for internal operations.
- We do not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models.
- We do not use Google user data to determine credit-worthiness or for lending purposes.
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
- Service providers that process data for us under contract: Microsoft Azure (hosting, encryption keys, email delivery, logs), Stripe (billing), Microsoft 365 (our support, privacy and security mailboxes) and HubSpot (support records and product-news emails). See our list of subprocessors.
- Destinations you direct: your own Google or Microsoft calendars, and Anthropic when you ask Claude about your calendars (see what Claude receives).
- Legal and safety: when required by law, or to protect the rights, safety and security of our customers, PathShift or others.
- Business transfers: in a merger, acquisition or sale of assets, with notice to you, and subject to this policy.
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
- Refresh tokens and feed links: deleted immediately when you disconnect a calendar or your subscription ends (up to 30 days only if needed to finish removing copies).
- Connected-account details (emails, calendar names, labels): until you disconnect the account or delete your Chrona account.
- Account, settings and sign-in identity: until you delete your account, or 90 days after your subscription ends.
- When you delete your account: your subscription stops renewing and Chrona keeps working until the end of the period you’ve paid for. At that point copies are removed (or kept, as you choose), tokens are deleted, and your account data is erased, normally within a day. If Chrona can no longer reach your primary calendar to remove copies, we keep only what's needed to finish that for up to 30 days. If your subscription has already ended, deletion starts right away.
- Sessions: up to 14 days (3 days idle). Logs: 30 days (application logs and platform request logs).
- Billing records stay with Stripe as required for tax and accounting.
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
- Control what’s copied: choose “Busy”, title, or title and description for each calendar, or remove a calendar, in your dashboard.
- Export your data: dashboard → Account → Download my data gives you a JSON file of everything we store about your account.
- Delete your account and data: dashboard → Account → Delete my account. Deletion happens at the end of the period you’ve paid for (you can cancel it before then), or right away if your subscription has ended.
- Disconnect a calendar account in your dashboard, or revoke Chrona’s access directly with the provider: Google Account third-party connections, Microsoft My Apps (work or school accounts) or Microsoft account app permissions (personal accounts).
- Disconnect Claude in your dashboard.
- Cancel your subscription in your dashboard. See the subscription terms.
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
- Know and access: ask what personal information we have about you and get a copy.
- Delete: ask us to delete it.
- Correct: ask us to fix inaccurate information.
- Portability: get your data in a portable format (our export is a JSON file).
- Opt out of the sale or sharing of personal information, targeted advertising, and profiling for significant decisions. Chrona does not sell or share personal information, does not do targeted advertising and does not profile you, so there is nothing to opt out of. We honor Global Privacy Control (GPC) browser signals as an opt-out request all the same.
- Limit use of sensitive information: we use account credentials, such as refresh tokens, only to provide the service you asked for.
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.
| Category | Examples at Chrona | Disclosed to |
|---|---|---|
| Identifiers | Account email, connected-account emails, hashed sign-in IDs, Stripe IDs | Service providers (Microsoft Azure, Stripe) |
| Commercial information | Subscription status and billing history (held by Stripe) | Stripe |
| Internet or other electronic network activity | Session records, application logs (IDs, counts, error codes), platform request logs (which pages were requested) | Microsoft Azure |
| Account access credentials | Encrypted OAuth refresh tokens and calendar feed links | Microsoft Azure (encrypted storage and key management) |
| Calendar content (processed in memory only, never stored) | Event titles, descriptions, times, attendees | Only 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