Privacy Policy

Effective Date: April 12, 2026 | Developer: Brilliancestack Technologies (OPC) Pvt Ltd | Contact: support@brilliancestack.com

  In plain language: Next Timer reads your calendar to fire alarms. That calendar data stays entirely on your device and is never sent to our servers. We use Google services for analytics, crash reporting, and advertising. You control whether ads are personalised through a consent prompt shown at first launch.

1. Introduction

Next Timer ("the App") is developed by Brilliancestack Technologies (OPC) Pvt Ltd. This Privacy Policy explains what information the App collects, how it is used, and how it is protected. By using the App you agree to the practices described here.

2. Information We Collect

Calendar data — stored on your device only

To set alarms for your calendar events, the App reads the following from your device's Android Calendar after you grant the READ_CALENDAR permission:

Calendar account name and email address
Event title, start time, end time, and recurrence rule

This data is stored exclusively in a local database on your device. It is never transmitted to our servers or any third party. Event descriptions, locations, and attendee lists are not read or stored.

Usage analytics — sent to Google

We use Firebase Analytics to understand how users interact with the App. This collects anonymised in-app events (such as alarms triggered and settings changed), device model, Android version, app version, and country derived from IP address. No personal names, email addresses, or calendar content are included in analytics data.

Crash reports — sent to Google

We use Firebase Crashlytics to detect and fix app crashes. It collects crash stack traces, device model, OS version, and app version. No calendar data or personal information is included.

Advertising data — sent to Google (with consent)

The App displays ads through Google AdMob. For users who consent to personalised advertising, AdMob may collect the Android Advertising ID, approximate location from IP address, device type, and ad interaction data. Users who decline consent will receive non-personalised contextual ads instead. Users who purchase "Remove Ads" will not see any ads.

Purchase information

The "Remove Ads" purchase is processed entirely by Google Play. We receive only a purchase token confirming the transaction. We do not collect, store, or have access to any payment or billing information.

3. How We Use Information

Data	Purpose
Calendar data (local)	Display your events and fire alarms at the correct time
Usage analytics	Understand feature usage and improve the App
Crash reports	Detect and fix stability issues
Advertising data	Display advertisements (personalised or non-personalised based on your consent)
Purchase token	Verify the "Remove Ads" purchase and disable ads

4. Data Storage and Retention

On-device data — calendar and event data is retained on your device for as long as the App is installed. Uninstalling the App deletes all locally stored data.
Google-held data — Analytics and Crashlytics data is retained on Google's servers per Google's data retention policy. You may request deletion via Google's privacy tools.
AdMob — governed by Google's advertising data policies.

5. Third-Party Services

Service	Provider	Purpose	Data sent	Privacy policy
Firebase Analytics	Google LLC	Usage analytics	Anonymous events, device info	Link
Firebase Crashlytics	Google LLC	Crash reporting	Stack traces, device info	Link
Google AdMob	Google LLC	Advertising	Advertising ID, device info (with consent)	Link
Google Play Billing	Google LLC	In-app purchases	Purchase token only	Link

All Google services are subject to Google's Privacy Policy. Data may be processed on servers located in the United States or other countries where Google operates.

6. Advertising and Consent

On first launch, users in regions where required by law are shown a consent prompt. You may accept personalised ads or decline — non-personalised contextual ads will be shown if you decline. To change your preference after the initial prompt, manage your settings in Google Settings → Ads on your device. Purchasing "Remove Ads" removes all advertising entirely.

7. Permissions

Permission	Why it is needed
READ_CALENDAR	Read your calendar events to schedule alarms
POST_NOTIFICATIONS	Show alarm and reminder notifications
USE_FULL_SCREEN_INTENT	Display full-screen alarm overlay on the lock screen
SCHEDULE_EXACT_ALARM	Fire alarms at the exact time of your events
INTERNET	Required by Firebase Analytics, Crashlytics, and AdMob
com.google.android.gms.permission.AD_ID	Required by Google AdMob for advertising (subject to consent)
RECEIVE_BOOT_COMPLETED	Reschedule alarms after device restart

8. Your Privacy Rights

Depending on where you live, you may have rights regarding your personal data — such as the right to access, correct, or request deletion of data held about you. Calendar data stored on your device is deleted automatically when you uninstall the App. For data held by Google (Analytics, Crashlytics, AdMob), please use Google's privacy tools or refer to Google's Privacy Policy. For any other privacy questions or requests, contact us at support@brilliancestack.com.

9. Children's Privacy

The App is intended for users aged 13 and older. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information through the App, please contact us and we will take steps to delete it.

10. Changes to This Policy

We may update this Privacy Policy from time to time. The effective date at the top of this page will be updated when changes are made. Continued use of the App after changes are posted constitutes acceptance of the updated policy.

11. Contact Us

For privacy-related questions or requests, contact:
Brilliancestack Technologies (OPC) Pvt Ltd
support@brilliancestack.com