Privacy Policy
This Privacy Policy explains what information Chronicle collects, how it is used, and the choices you have. It applies to the Chronicle iOS app and any related services we operate (collectively, the "Service"). By using Chronicle you agree to the practices described below.
1. Information we collect
1.1 Account information
When you sign in we use Sign in with Apple. Apple shares with us:
- A unique, Apple-issued user identifier;
- Your name (only if you choose to share it);
- An email address (which may be your real address or a private relay address generated by Apple).
We do not collect or store passwords. Authentication is handled by Supabase Auth (GoTrue) acting as our processor.
1.2 Content you create in the app
Chronicle stores the data you enter so it can be displayed across your devices, including:
- Time entries (title, notes, start and end times, duration, source);
- Categories (name, colour, ordering);
- Goals (target hours, period);
- Tasks (title, completion state, scheduled date);
- Preferences and app settings.
This data is stored locally on your device using SwiftData and, when you are signed in, synchronised to our backend so you can use Chronicle on multiple devices. Soft-delete timestamps are retained so that deletions sync correctly.
1.3 Apple Health data (HealthKit)
With your explicit permission, Chronicle reads the following from Apple Health to display alongside your timeline:
- Workouts (type, start and end times);
- Sleep analysis (timestamps);
- Mindful sessions (start and end times).
Chronicle requests read-only HealthKit access and never writes data back to Apple Health. Raw HealthKit samples are read on-device only and are not transmitted to our servers. When a workout, sleep block, or mindful-session entry is added to your Chronicle timeline, the resulting time entry is synced to your Chronicle account so it can appear on your other devices. That synced entry includes its title (for example, "Running"), start and end times, duration, the Apple-issued HealthKit sample identifier (UUID), and the HealthKit type and category. We do not use Health data for advertising, and we do not sell it or share it with data brokers, advertising networks, or any other third party. You can revoke HealthKit access at any time in Settings → Privacy & Security → Health → Chronicle.
1.4 Calendar data (EventKit)
With your explicit permission, Chronicle reads events from your iOS Calendar so they can appear on your timeline. We do not modify your calendars. When a calendar event is added to your Chronicle timeline, the resulting time entry is synced to your Chronicle account so it can appear on your other devices. That synced entry includes the event title, start and end times, duration, the EventKit event identifier, and the identifier and name of the source calendar. We do not share your calendar contents with advertising networks or any other third party. You can revoke calendar access in Settings → Privacy & Security → Calendars.
1.5 Location data (CoreLocation)
With your explicit permission, Chronicle monitors the places you visit using iOS visit monitoring so it can suggest activities based on where you are. For each recognised place, Chronicle stores on your device: the place's GPS coordinates (latitude and longitude), a label you may assign, visit and overnight counts, and any activities you have linked to that place. This data is stored locally only and is never transmitted to our servers. You can revoke location access at any time in Settings → Privacy & Security → Location Services → Chronicle.
1.6 Diagnostic and technical information
When the app communicates with our backend, our servers automatically receive standard request metadata (IP address, user-agent, timestamps, and, where relevant, error messages). This is used to operate, secure, and debug the Service. Chronicle does not integrate any third-party analytics, advertising, attribution, or crash-reporting SDK.
1.7 Information we do not collect
Chronicle does not collect: contacts, photos, microphone or camera input, the IDFA / advertising identifier, browsing history, or any data from other apps.
2. How we use information
We use the information described above to:
- Authenticate you and keep your account secure;
- Sync your time-tracking data between your devices;
- Render workouts, sleep, energy, and calendar events on your timeline;
- Provide, maintain, support, and improve the Service;
- Detect, prevent, and respond to fraud, abuse, and security incidents;
- Comply with our legal obligations.
We do not use your data for advertising, profiling, or automated decision-making that produces legal or similarly significant effects, and we do not sell or "share" your personal information as those terms are defined under U.S. state privacy laws.
3. Legal bases (EEA / UK users)
Where the GDPR or UK GDPR applies, we rely on the following legal bases: performance of a contract (to provide the Service you have requested), legitimate interests (to secure, debug, and improve the Service), consent (for HealthKit, Calendar, Location, and notifications, which you can withdraw at any time in iOS Settings), and compliance with legal obligations.
4. How information is shared
We share personal information only with the following categories of recipients, and only to the extent necessary:
- Apple Inc. — Sign in with Apple and push notifications.
- Supabase, Inc. — managed Postgres database and authentication that store your account and synced content.
- Google Cloud (Google LLC) — hosts our backend service (Cloud Run) which mediates between the app and Supabase.
- Authorities and other parties — when required by law, to enforce our terms, or to protect the rights, property, or safety of users or the public.
These providers process data on our behalf under contractual confidentiality and security obligations. Some of them may process data outside your country, including in the United States. Where required, we rely on appropriate safeguards such as the EU Standard Contractual Clauses.
We do not sell your personal information and we do not share it with data brokers or advertising networks.
5. Data retention
We retain your account and content for as long as your account is active. If you delete an item in the app, it is marked as deleted and removed from active sync; residual records are purged from our backend within 30 days. If you delete your account, we delete or anonymise your personal data within 30 days, except where we are required to retain it to comply with legal obligations, resolve disputes, or enforce our agreements.
Raw HealthKit samples and the underlying iOS Calendar event database are accessed on-device only and are not retained on our servers. Time entries that you add to your Chronicle timeline from HealthKit or Calendar are stored on our servers under the same retention rules as other time entries described above.
6. Security
We use industry-standard measures to protect your information, including TLS for data in transit, encryption at rest provided by Supabase and Google Cloud, row-level security policies that restrict each user's data to that user, and least-privilege access controls for our personnel. No method of transmission or storage is 100% secure; we cannot guarantee absolute security.
7. Your rights and choices
Depending on where you live, you may have the right to access, correct, export, delete, or restrict processing of your personal information, to object to processing, to withdraw consent, and to lodge a complaint with your local data-protection authority. You can exercise these rights by contacting us at the address in Section 11. We will respond within the timeframe required by applicable law.
You can also:
- Revoke HealthKit access in Settings → Privacy & Security → Health → Chronicle;
- Revoke Calendar access in Settings → Privacy & Security → Calendars;
- Revoke Location access in Settings → Privacy & Security → Location Services → Chronicle;
- Manage notifications in Settings → Notifications → Chronicle;
- Sign out or delete your account from within the app.
California residents: you have the rights described in the CCPA/CPRA, including the right to know, delete, correct, and limit. We do not sell or share personal information for cross-context behavioural advertising.
8. Children's privacy
Chronicle is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.
9. International transfers
We are based in our country of registration; our processors operate globally. By using Chronicle you understand that your information may be processed in countries other than your own. Where required, transfers are governed by appropriate safeguards such as the EU Standard Contractual Clauses.
10. Changes to this policy
We may update this policy from time to time. Material changes will be communicated through the app or by updating the "Last updated" date above. Your continued use of Chronicle after a change becomes effective constitutes acceptance of the revised policy.
11. Contact
If you have questions or requests about this policy or your personal information, contact:
Zan Labs
Email: chronicle@zanlabs.dev