Privacy Policy

Effective September 14, 2026

Reviewed for the Linear Clock 1.0.6 private-release candidate on September 14, 2026.

Who we are

Linear Clock is operated by Calendria Inc. in Toronto, Ontario, Canada. Privacy questions and verified data requests may be sent to hello@calendria.com.

Information you provide or choose

• Account name, email and sign-in provider when you create an account or use Apple or Google sign-in.
• App preferences such as language, themes, day structure, notifications and settings you choose to synchronize.
• Optional Calendar, while-in-use Location and Photos access. Source calendar items and source-library photos remain under the operating system's control.
• Saved places, Journey endpoints, focus/reflection content, Today records and selected photo copies, which are stored locally unless you share an export or use the routing/Maps features below.
• Referral codes, support messages and other information you deliberately send.

Information processed automatically

• A stable app-install identifier and a platform device identifier used for referrals, one-time trial enforcement and fraud prevention; platform/app version and security signals from Firebase App Check; and a push token if notifications are enabled.
• Purchase product, transaction and entitlement status from Apple, Google Play and RevenueCat. Calendria does not receive your full payment-card number.
• Advertising identifiers and consent choices where permitted. The free tier may receive Google AdMob ads after onboarding and the applicable consent flow. Active paid subscriptions are ad-free.
• Optional Firebase Analytics events only after you opt in. These may describe screens/features used, durations, purchase or ad funnel steps and reliability outcomes, but are designed not to include coordinates, addresses, calendar titles, reflection text or photo contents.
• Ordinary request metadata and limited server logs used to operate the service, enforce rate limits, diagnose failures and prevent abuse.

Journey Mode, geocoding and Maps

Journey Mode requests while-in-use location only after an explicit setup or Start action. Live tracking runs only while Linear Clock is foregrounded and active; it pauses while the app is backgrounded, another Maps app is open or the phone is locked. Linear Clock does not request background-location or Android location foreground-service permission and does not store a raw GPS trace.

Typed place/address text is processed by the device platform's geocoding service to return coordinates. Saved labels and place records stay local. If you request a traffic-aware route, Linear Clock sends the selected origin and destination coordinates and travel mode through Calendria's routing endpoint to Google Routes. An occasional refresh during an active foreground journey may send current position as the updated origin. The request also carries the app-install identifier, Firebase App Check token when available and ordinary network metadata. Calendar titles, saved-place labels and a sequence of GPS fixes are not included, and Calendria's application function is designed not to log route coordinates.

Familiar-place calendar matching and the estimated leave-by/travel-time chip happen locally and do not start live tracking. If you later request a route or open external directions, the relevant coordinates are used then. An explicit Apple Maps or Google Maps handoff places destination coordinates and travel mode in that provider's URL; the selected Maps provider then handles them under its own terms.

How we use and share information

Calendria processes information to provide timelines, widgets, watch features, alarms, Focus Sessions, Journey Mode and reminders; synchronize chosen settings; verify purchases, rewards and referrals; provide support; measure opted-in usage; protect the service; and comply with law. Information is shared only with service providers acting for these purposes, when you direct a share or Maps handoff, during a corporate transaction, or when legally required.

Relevant providers include Apple and Google platform services and sign-in, Google Firebase (Authentication, Firestore, Messaging, App Check and optional Analytics), Google Routes, Google AdMob, RevenueCat, Apple App Store and Google Play. Each provider may process data under its own terms and retention rules.

Storage, export, retention and deletion

• Local app data remains until you erase it under Settings → Privacy & Data or remove the app. The JSON export includes app storage and Today records and can contain profile/install identifiers plus saved-place, active Journey and history coordinates. Credential-like values are redacted and photo file references are listed, but image bytes are not bundled.
• Firebase account and synced settings remain while the account is active. In-app account deletion refreshes Firebase authentication and revokes linked Sign in with Apple authorization first on iOS, then deletes the signed-in user's synchronized settings and Firebase Authentication record. If Apple confirmation, identity-token or authorization-code retrieval, Firebase reauthentication or revocation fails, deletion does not begin.
• Referral, device-trial and fraud-prevention records can be keyed to an app-install or platform device identifier instead of the account UID. They are not automatically removed by in-app account deletion and may remain until a verified deletion request is processed or they are removed during anti-abuse maintenance.
• Provider records, logs and backups may remain for security, legal, billing, consent, fraud-prevention and backup purposes under Calendria's or the provider's applicable retention process. Store subscriptions are not cancelled by account deletion and must be managed through Apple or Google Play.

Use Account deletion if you cannot access the app or need a separately keyed record reviewed. Never send a password, authorization code or payment-card number by email.

Your choices

You may decline optional permissions, keep analytics off, revisit available advertising privacy choices in Settings, export or erase local data, delete your account, and request access, correction or deletion. Declining tracking does not prevent use of Linear Clock, although declining a feature-specific permission prevents that feature from using it.

Children

Linear Clock is not directed to children under 13 and Calendria does not knowingly collect their personal information. A parent or guardian who believes a child supplied personal information should contact us.

International processing and security

Service providers may process information outside your province or country. Calendria uses reasonable administrative and technical safeguards, but no system can guarantee absolute security.

Changes

We may update this policy as the app or law changes. The effective date will be updated and material changes will be communicated where required.