Security at Chrona
Chrona is trusted with access to calendars, including clients’ calendars, so we designed it to hold as little as possible and to protect what it does hold. This page summarizes how, and how to report a security issue.
How we protect your data
We keep as little as possible
- Chrona asks for calendar permissions only, never mail or files, and connects calendars read-only by default (write access only for your primary, and for any calendar you let Claude add events to).
- Event titles, descriptions, attendees, locations and times are never stored. They exist only in memory during a sync or a Claude request. Automated tests check every table to confirm this.
- Our application logs record only IDs, counts and error codes (checked automatically). The hosting platform’s request logs record which pages were requested. All logs expire after 30 days.
We encrypt what we keep
- Refresh tokens (the long-lived permission Google or Microsoft gives Chrona to reach your calendars) and calendar feed links are envelope-encrypted with a key held in a hardware security module (Azure Key Vault). Every use of that key is audit-logged.
- Email addresses and calendar names are encrypted with a key specific to each customer.
- All connections use HTTPS.
We limit access
- Chrona’s services run under separate managed identities with only the permissions each needs. The public web app can encrypt tokens but cannot decrypt them.
- No passwords or keys are kept in code.
- Storage and Key Vault are firewalled to accept connections only from Chrona’s own private network and services.
- You sign in with Google or Microsoft, so your Google or Microsoft protections, including multi-factor authentication if you use it, apply to your Chrona account.
- Incoming webhooks are verified (signatures for Stripe, secret tokens for Google and Microsoft), and automated tests check that each customer’s data is isolated from every other customer’s.
- Chrona’s code gets a separate AI-assisted security review before launch. It has not had a third-party audit or penetration test.
Certifications: Chrona does not have SOC 2 or ISO 27001 certification yet. Our hosting provider (Microsoft Azure) and payment processor (Stripe) maintain their own certifications.
See also our Privacy Policy and list of subprocessors.
Vulnerability disclosure policy
We welcome reports from security researchers and anyone else who finds a weakness in Chrona.
How to report
Email security@thepathshift.com with:
- a description of the issue and where it is;
- the steps to reproduce it, and a proof of concept if you have one;
- the impact you think it has; and
- how to contact you, and whether you’d like to be credited.
We’ll acknowledge your report within 5 business days and keep you updated as we investigate and fix it. Our security.txt file has the same contact details.
Scope
In scope:
- chrona.thepathshift.com
- app.chrona.thepathshift.com
- mcp.chrona.thepathshift.com
Out of scope:
- Services run by Google, Microsoft, Stripe or Anthropic. Please report issues in those to the company concerned.
- Social engineering or phishing of PathShift staff or customers.
- Denial-of-service attacks, load testing or anything that degrades the service.
- Physical attacks on offices or equipment.
Rules for testing
- Use only your own accounts and calendars, or test accounts you create.
- Access only the data you need to show the issue. If you reach anyone else’s data, stop, don’t keep or share it, and tell us right away.
- Don’t violate anyone’s privacy, change or delete other people’s data, or disrupt the service.
- Give us reasonable time to fix the issue before you disclose it publicly. We ask for 90 days from your report, and we’ll work with you on timing.
Safe harbor
If you make a good-faith effort to follow this policy, we consider your research authorized. We won’t pursue legal action against you for it, and if a third party takes legal action against you over research that followed this policy, we’ll make it known that your work was authorized. If you’re unsure whether something is allowed, ask us first at security@thepathshift.com.
No bug bounty
We don’t run a paid bug bounty program. With your permission, we’re happy to thank you publicly.