Updated: September 2025

Privacy Policy

1. Introduction

1.1 This Privacy Policy explains how the Calflow application (the “App”) handles information. It applies only to the iOS/iPadOS/macOS App. We do not operate a website for this App. 1.2 We designed the App to run primarily on‑device. We do not operate backend servers and do not store your content on developer systems. 1.3 We do not collect your personal content. The developer cannot see your calendars, events, reminders, notes, tags, or other in‑App data. 1.4 If you enable iCloud, your data is stored under your Apple ID in iCloud, managed by Apple. We cannot access your iCloud data. 1.5 We use Google Firebase (Crashlytics and limited Analytics for stability) only to investigate crashes and bugs. We do not use targeted advertising or cross‑app tracking and we do not sell data.

2. Scope

2.1 This Policy covers the App only. If you interact with Apple services (e.g., iCloud, App Store) or Google Firebase, their terms and privacy notices also apply.

3. Data We Do Not Collect or Store

3.1 We do not collect, receive, or store the following on developer systems:

  • (a) Calendar data (e.g., titles, notes, attendees, time ranges);
  • (b) Reminders (e.g., titles, notes, due dates);
  • (c) User content created in the App (e.g., notes, tags, categories, settings content);
  • (d) Contacts or precise location;

4. Data Processed for Diagnostics (via Firebase)

4.1 Purpose. To detect, diagnose, and fix crashes/bugs and improve App stability. 4.2 Provider. Google Firebase acts as our data processor for diagnostics; we remain the controller. 4.3 Categories (examples). Depending on configuration, Firebase may process:

  • (a) Crash & diagnostics: stack traces, exception messages, crash timestamps, limited app state (e.g., foreground/background), minimal session info for reproduction;
  • (b) App information: app version/build, basic events around failures (e.g., app launches when relevant);
  • (c) Device/system: device model, OS version, language/locale, time zone;
  • (d) Identifiers: a random app instance ID or IDFV used only to group events from the same install over time (no IDFA);
  • (e) Network metadata: IP address may be processed by Google to deliver the service and derive coarse region. We do not receive or retain IP addresses. 4.4 Use. We use diagnostics only to measure stability (e.g., crash‑free sessions), reproduce issues, and prioritize fixes. Data is handled in aggregate or pseudonymous form; we do not attempt to identify you. 4.5 Configuration. Advertising features and cross‑app tracking are disabled. Data is configured for this App’s diagnostics only. 4.6 Retention. Diagnostics are retained by Firebase for a limited period necessary for the purposes above and then aggregated and/or deleted per provider settings.

5. Storage & Transfers

5.1 No developer servers. We do not run backend servers for the App and do not store your content on developer systems. 5.2 On‑device. Your content stays on your device unless you enable iCloud. 5.3 iCloud (optional). If enabled, data is stored under your Apple ID in iCloud and governed by Apple’s terms and policies. Apple may process and transfer data per its infrastructure; we cannot access your iCloud data. 5.4 Diagnostics. Limited diagnostics data is stored by Google (Firebase) on our behalf as processor; Google’s infrastructure may involve international transfers under its terms.

6. Security

6.1 On device, the App relies on platform‑level protections (e.g., sandboxing and system encryption where available). 6.2 For diagnostics, we select providers that implement appropriate technical and organizational security measures. We do not have direct access to your user content.

7. Payments

7.1 In‑app purchases are processed by Apple via the App Store. We do not receive your payment card details.

8. Your Choices & Controls

8.1 On‑device and iCloud. Manage data on your device via system/App settings. For iCloud data, use Apple’s tools and policies. 8.2 Diagnostics preferences. If the App provides a setting such as “Share anonymous diagnostics,” you may disable it (where available). This does not affect essential crash logging required for stability where permitted by platform policies.

9.1 We may disclose information if required by applicable law (e.g., valid court order). Because we do not hold your content on our servers, such cases are limited in scope.

10. Changes to this Policy

10.1 We may update this Policy from time to time.