This policy explains how TadbirLabs handles information for Halora. It is written for transparency and app-store review, but it is not legal advice.
Who We Are
Halora is developed by TadbirLabs. You can contact us at tadbirlabs@gmail.com.
This policy applies to the Halora mobile app for Android and iOS and to the Halora pages hosted at tadbirlabs.github.io/halora.
Privacy Summary
Personal countdown content stays local
Your countdown titles, dates, notes, reminder choices, widget choices, and optional photo backgrounds are stored on your device unless you export or share them.
No account required
Halora does not require a TadbirLabs account. We do not operate a user-content backend for your countdowns.
No ads or sale of personal data
Halora is monetized through optional Premium purchases, not advertising. We do not sell personal information.
Privacy-safe diagnostics
Analytics and crash reporting help us understand feature use, purchase flow reliability, and app stability without collecting private event titles, notes, exact personal dates, photo paths, or photos.
Information Stored on Your Device
Halora stores app data locally so the app can work without an account. Local data may include:
- Countdown titles, event dates, categories, repeat settings, and notes.
- Reminder rules and scheduled local notification state.
- Theme, widget style, language, calendar, Premium state cache, and analytics preference.
- Optional photo background files that you choose for widgets.
- Compact widget snapshots used by native Android and iOS widget surfaces. These snapshots are designed for widget rendering and do not include notes.
- Manual backup files when you choose to export them. Backup files may include countdown content and should be kept private.
We do not automatically upload your countdown database or backup files to TadbirLabs servers.
Information We May Receive
| Category | Purpose | Examples |
|---|---|---|
| Product analytics | Understand conversion, retention, feature quality, and purchase flow reliability. | App opened, paywall viewed, package type selected, purchase or restore outcome, language changed, widget style selected, event category, event count bucket, app version, platform, locale, Premium active/inactive state. |
| Crash diagnostics | Find and fix stability issues in release builds. | Crash stack traces, error type, app version, OS version, device model, installation identifiers, and logs needed to diagnose the crash. |
| Purchase and entitlement data | Deliver and restore Premium access. | Store product identifiers, purchase status, entitlement status, anonymous RevenueCat app user ID, transaction metadata provided by Google Play or the App Store. |
| Support messages | Respond to your request. | Your email address and any information you choose to include when contacting us. |
Halora analytics deliberately excludes private countdown titles, notes, exact personal dates, personal names, photo files, photo paths, backup files, and raw RevenueCat identifiers.
Third-Party Services
Halora uses the following services for production app operation:
- Firebase Analytics for privacy-safe product analytics. Google privacy information is available at policies.google.com/privacy.
- Firebase Crashlytics for crash reporting and diagnostics. Google privacy information is available at policies.google.com/privacy.
- RevenueCat for subscription and entitlement management. RevenueCat privacy information is available at revenuecat.com/privacy.
- Google Play Billing and Apple in-app purchases for payment processing. We do not receive your full payment card details.
Analytics and Crash Controls
Halora includes a Settings control named "Share app analytics." In current release builds, privacy-safe analytics may be enabled by default. You can turn it off in Settings, and Halora will disable Firebase Analytics collection for that device.
Crashlytics may remain active in release builds to help diagnose serious app failures. Crash reports are intended to exclude your private countdown content.
Permissions
- Internet: used for purchases, entitlement checks, analytics, crash diagnostics, and store-related services.
- Notifications and exact alarms where supported: used only when you enable reminders.
- Boot completed on Android: used to restore local reminders after restart.
- Photo library or media access: used only when you choose a photo background.
- Files and sharing surfaces: used when you export, import, save, or share backup and share-card files.
Halora does not request access to contacts, microphone, phone calls, or precise location for its core countdown experience.
How We Use Information
- Provide countdowns, reminders, widgets, themes, backups, and share cards.
- Process Premium purchases, restore purchases, and enforce Premium access.
- Improve onboarding, conversion, retention, and app quality using privacy-safe analytics.
- Debug crashes and operational issues.
- Answer support, privacy, and legal requests.
- Comply with applicable law and app-store requirements.
Retention and Deletion
Local countdown data stays on your device until you delete it, clear app data, or uninstall the app. Manual backup files remain wherever you saved or shared them until you delete those copies.
Analytics, crash, and purchase records are retained by Firebase, Google, Apple, and RevenueCat according to their own retention practices. We keep support emails for as long as needed to respond and maintain basic business records.
See Data Deletion for practical deletion steps.
Your Rights
Depending on your location, you may have rights to access, correct, delete, export, object to, or restrict processing of personal information. Because Halora is local-first and account-free, most countdown content can be accessed, exported, changed, or deleted directly on your device.
For privacy requests, email tadbirlabs@gmail.com. We may need enough information to verify and process the request.
Children
Halora is not directed to children under 13, or the minimum age required by local law. We do not knowingly collect personal information from children.
Changes
We may update this policy when Halora changes, when legal requirements change, or when third-party services change. The updated date at the top of this page shows the latest version.