Privacy Policy

Effective date: September 9, 2026 · Applicable product: ShiftAlarm (iOS)

In short: Your alarms, reminders, and preferences are stored only on your device. We do not sell or share your data. We use Firebase for crash reporting, remote configuration, and aggregated usage analytics so we can fix bugs and improve the app. Firebase may collect device-level identifiers and crash data; see Section 4 for details.

1. Who we are

"ShiftAlarm" (the "App") is developed and operated by an independent developer ("we" / "us"). Our contact details appear at the end of this policy. This policy explains how we handle data when you use the App.

2. Information we collect

We do not require account registration and do not collect your name, email, phone number, location, photos, contacts, or any content you create inside the App (alarms, reminders, shifts, preferences). The data we do handle is listed below.

2.1 Content you create (stored locally only)

Alarms and reminders (including repeat rules, tags, sound choices)
Shift/schedule records and skip records
Scheduled next-fire instances
App preferences (theme, default sound, free-tier usage counters, etc.)

This content is stored on your device locally using iOS SwiftData and App Group UserDefaults. It is not synced to iCloud and never passes through any server we operate.

2.2 Purchase information (handled by Apple)

When you subscribe to Pro or buy the Lifetime unlock, the transaction is processed and billed by the Apple App Store. We only receive the receipt information Apple passes through (used to verify the purchase and to support Restore Purchases). We never receive your payment account, card number, or full billing details. Apple's handling of your payment information is governed by Apple's own privacy policy.

2.3 Public holiday data

To support features such as "skip holidays when firing alarms", the App retrieves the statutory holiday list for your region from a public, official holiday data source. This request carries no information that can identify you; it is read-only reference data.

3. System permissions we use

The App follows a minimal-permission approach and requests permissions only when you actually use the related feature:

Notification (reminder) permission: requested only when you first enable a reminder, and we request only alert, sound, and badge. We do not request provisional or critical notifications.
AlarmKit authorization: requested only when you first save an alarm, so the alarm can be handed off to the system clock and still fire in silent, Focus, and Standby scenarios.

The App does not request: location, camera, microphone, contacts, photo library, motion and fitness, health, Bluetooth, local network, Face ID/Touch ID, or App Tracking Transparency (ATT).

4. Third-party services: Firebase

The App integrates the Firebase SDK (provided by Google) for three purposes listed below. Firebase operates as a separate data controller for the data it collects; its handling is governed by Firebase's Privacy Policy and Google's Privacy Policy. We do not share any of your local alarm/reminder/preference data with Firebase.

Firebase module	What it collects	Purpose	Linked to you?
Crashlytics (crash reporting)	Crash stack traces, app version, iOS version, device model, memory state at crash time, and a randomly generated Crashlytics installation UUID stored on-device. The UUID persists across sessions but resets when you uninstall or clear app data.	To diagnose and fix crashes. Linked to the Crashlytics UUID so we can see whether the same device hits the same crash repeatedly.	Yes, to a per-installation ID. Not to your name, email, or Apple ID.
Analytics (Google Analytics for Firebase)	Aggregated, anonymous usage events such as "alarm created", "paywall viewed", "subscription purchased"; a Firebase app instance ID; coarse device characteristics (model, OS version, locale, mobile network operator); and limited app performance metrics (e.g. cold-start time).	To understand which features are used and where to improve the product.	Yes, to a per-installation app instance ID. We do not send IDFA and have not enabled Firebase's integration with Google Ads for personalized advertising.
Remote Config	Retrieves server-side configuration values (e.g. feature flags, copy variants). No user content is sent in the request beyond the standard Firebase installation ID, which lets Firebase target configurations by app version or locale.	To toggle features and copy without shipping an app update.	Only by Firebase installation ID.

4.1 What we do with Firebase data

We use the data above solely to: (a) detect and fix crashes, (b) understand aggregate feature usage, and (c) deliver the correct remote configuration. We do not use Firebase data for advertising, do not sell it, and do not share it with third parties beyond what Firebase itself needs to operate the service.

4.2 What Firebase does with the data

Firebase may process and retain the data listed above according to its own policies. Google may use aggregated, de-identified data derived from Firebase to improve its own services. We cannot control Google's downstream use of aggregated data; please review Google's privacy policy linked above.

5. Other third-party services

Besides Firebase (Section 4), Apple's in-app purchase settlement, and Apple system frameworks (AlarmKit, UserNotifications, SwiftData), the App does not integrate any other third-party SDK, ad network, or analytics service.

6. Data sharing and sale

We do not share your local content (alarms, reminders, preferences) with any third party. We do not sell or rent personal data. Firebase receives only the categories listed in Section 4 in the course of providing its services.

7. Data retention and deletion

7.1 Local data

All of your local content remains on your device until:

you manually delete the corresponding alarm or reminder within the App, or
you uninstall the App (iOS then erases all associated data), or
you clear the App's data via Settings > General > iPhone Storage.

7.2 Firebase data

Crash and Analytics data is retained by Firebase according to its retention schedule (typically up to 90 days for raw crash events; longer for aggregated metrics). The Crashlytics UUID and Firebase app instance ID reset when you uninstall the App. To request deletion of Firebase-side data associated with your installation IDs, contact us at the email in Section 11 and we will forward the request to Firebase.

8. Your rights

Because all local data lives on your device, you remain in direct control at all times:

Access: view all alarms, reminders, and preferences inside the App at any time.
Deletion: delete items one by one in the App, or remove everything at once by uninstalling.
Backup/Export: back up via the iOS system backup mechanism to your personal iCloud or computer.
Opt out of Firebase: because Firebase does not require an account, the most reliable way to opt out is to uninstall the App. You can also disable Analytics data collection at the device level via the iOS Settings > Privacy & Security > Analytics & Improvements controls; this affects Firebase Analytics on this device globally.

If you need assistance, contact us at the email listed at the bottom; we will respond within a reasonable timeframe.

9. Children's privacy

The App is intended for a general audience. It is not marketed to children under 13 and does not knowingly collect any personal information from children. If you believe data has been collected in error, contact us and we will delete it promptly.

10. Links to other websites

The App or this policy may link to third-party websites (e.g., Apple's official documentation, public holiday data sources, or Google's privacy policy). We are not responsible for the privacy practices of those third-party sites; we encourage you to read their respective policies.

11. Changes to this policy

We may update this policy from time to time. Material changes will be surfaced in the App or on this page. Continued use of the App after a change constitutes acceptance of the updated policy. The "Effective date" at the top of this page reflects the latest version.

12. Contact us

If you have any questions about this policy or the App's data practices, please contact:

Email: peakfitdev@163.com