CheckAlarm — Privacy Policy

1. Who we are and scope

This policy applies to the CheckAlarm Android and iOS apps. The data controller is the sunlitwater.com Privacy Team. CheckAlarm has no user account, operator-hosted backend, or account-based cloud sync.

2. Information kept on the device

Alarm names and schedules, checklist text and photos, recorded alarm sounds, app settings, and check history are stored in the app's local storage. Photos taken with the camera or selected with the system picker are copied into the app's private storage. CheckAlarm does not intentionally upload this content to sunlitwater.com, Firebase, or AdMob.

The app also stores Firebase collection choices, advertising consent state managed by Google UMP, and earned additional-alarm credit.

Permissions and system services

• Alarms and notifications: used to schedule and display system alarms, reminders, and the active checklist.
• Camera/photos: used only when you add a checklist photo. Checklist photos remain in app storage unless you separately export them.
• Microphone: used only when you record a custom alarm sound; recordings remain in app storage.

3. Firebase Analytics and Crashlytics

Google Firebase may process app-instance or installation identifiers, coarse technical information about the device and operating system, app interactions, performance and diagnostic information, and crash stack traces. We do not intentionally put alarm names, checklist text, photos, recorded sounds, or precise location into Analytics events, user properties, Crashlytics keys, or logs.

Analytics remains off while the applicable regional requirement is being determined. It follows required regional consent and can be changed in Settings; outside regions requiring a choice, it is enabled unless turned off. Crashlytics is enabled by default and can be turned off in Settings.

Firebase Analytics event-level retention is configured to two months. Crash reports are generally retained by Firebase for up to 90 days. Aggregated or de-identified reports may remain longer where Google provides them without event-level or crash-level identifiers.

4. Advertising and consent

CheckAlarm uses Google AdMob for banner, interstitial, and rewarded interstitial ads, and Google User Messaging Platform (UMP) for privacy choices. Google and advertising partners may process advertising and device identifiers, IP address and IP-derived approximate location, ad interactions, product interactions, and technical diagnostics for delivery, measurement, frequency control, fraud prevention, and permitted personalization.

• Ads are not requested until UMP indicates that ads may be requested.
• Ad requests use Google's unspecified treatment and limit ad content to the T rating.
• UMP presents required regional choices. On iOS, App Tracking Transparency permission may be requested only where applicable. Declining a choice results in restricted, limited, or non-personalized advertising where supported.
• Privacy choices can be revisited from Settings whenever UMP requires an entry point.

A banner may appear at the bottom of Home, an interstitial may appear after a completed alarm check, and a clearly introduced rewarded interstitial is optional when creating an additional alarm. Test alarms and lock-screen transitions do not show the completion interstitial.

5. Purposes and legal grounds

Local alarm, checklist, photo, and sound data is processed to provide features you request. Essential device and consent settings are processed to operate the app and comply with law. Where required, consent is used for Analytics, personalized advertising, and tracking. Security, fraud prevention, limited advertising, diagnostics allowed by your settings, and service improvement may otherwise rely on contract performance or legitimate interests where the applicable law permits.

6. Retention and deletion

• Check history is automatically limited to 90 days and can also be deleted in Settings.
• Alarm, checklist, photo, and recorded-sound data remains until you edit or delete it, reset the app, or uninstall the app, subject to operating-system backup behavior.
• Turning off Crashlytics deletes an unsent report held by the app. Turning off Analytics stops future collection; data already processed follows Firebase retention settings.
• Google retains advertising, consent, Analytics, and diagnostics data according to its service terms and retention controls.

7. Service providers and international transfers

Google LLC and its affiliates provide Firebase, AdMob, and UMP. Data may be transmitted over an encrypted network when those services operate and processed in the United States and other countries where Google or its subprocessors maintain facilities. Google describes its safeguards, retention, and subprocessors in its service documentation. We do not sell your local alarm or checklist content.

See How Google uses information from partner services, the Google Privacy Policy, Firebase Privacy and Security, and Google Business Data Responsibility.

8. Your choices and regional rights

You can change Analytics and crash-reporting choices in Settings, use the UMP privacy entry point when shown, deny iOS tracking permission, delete check history, delete local content, or uninstall the app. Because CheckAlarm has no account and sunlitwater.com does not receive your local content, we ordinarily cannot retrieve data stored only on your device.

• EEA, UK, and Switzerland: you may request access, correction, deletion, restriction, portability, or objection, withdraw consent without affecting earlier processing, and complain to your supervisory authority.
• United States, including California: where applicable, you may request access, correction, or deletion and opt out of sale, sharing, targeted advertising, or profiling. sunlitwater.com does not sell personal information. Use UMP choices to limit advertising sharing or contact us for a request.
• Republic of Korea: you may request access, correction, deletion, suspension of processing, or withdrawal of consent and may contact the privacy team or the competent privacy authority.

We will not discriminate against you for exercising applicable privacy rights. We may need enough information to verify and respond to a request, but do not send alarm content, photos, or identification documents unless specifically requested and necessary.

9. Security, changes, and contact

We use platform sandboxing, permission controls, encrypted network connections supplied by the SDKs, and collection-off defaults while applicable privacy requirements are being determined. No storage or transmission method can be guaranteed completely secure.

We may update this policy when the app, law, or third-party services change. Material changes will be reflected by a new effective date on this page.