ChronticSubprocessors
Third parties who may process data on our behalf
Last Updated: July 18, 2026
Overview
Chrontic uses a small number of third-party services ("subprocessors") to help operate the Service. Some are used for every account; others only activate if you or your admin choose to connect that integration. This list is referenced by our Data Processing Agreement and will be updated as subprocessors are added or removed.
| Subprocessor | Purpose | Data Processed | When Active |
|---|---|---|---|
| Stripe | Subscription billing and payment processing | Billing name/email, payment method details (we never see full card numbers) | All paid accounts |
| Sign-in ("Sign in with Google"); analytics if you accept our cookie banner | Name, email, profile picture; anonymized usage data if analytics is accepted | If you sign in with Google, or accept analytics cookies | |
| Atlassian (Jira) | Optional Jira integration — linking time entries to tickets, syncing worklogs | Jira ticket IDs, titles, and worklog data | Only if your admin connects Jira |
| Microsoft (Outlook / Microsoft 365) | Optional Outlook calendar integration | Calendar events and metadata | Only if you connect Outlook |
| Tempo | Optional Tempo integration — syncing worklogs with Jira accounts | Worklog entries, Jira account mappings | Only if your admin connects Tempo |
International Transfers
Chrontic's own infrastructure is hosted in Germany, within the EU. Some subprocessors above may process data outside the EU/EEA under their own safeguards. See our Privacy Policy for more detail.
Questions
If you have questions about a subprocessor or want to be notified of changes to this list, contact us at support@chrontic.com.