Chronaby PathShift home page

Security at Chrona

Last updated:

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

We encrypt what we keep

We limit access

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:

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:

Out of scope:

Rules for testing

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.