한국어
Habit Builder Privacy Policy
Effective: 2026-09-08 · App: Habit Builder (com.eltacrew.habitdeck) · Developer: EltaCrew
Summary — Habit Builder has no server.
Your habits, logs, and mood notes are stored only on your phone. There is no sign-up or login, and no personal data is sent to the developer. Uninstalling the app deletes everything.
1. Information processed
| Item | Details | Stored |
|---|
| Habit list | Name, type, goal, colour, repeat settings | On device (Room DB) |
| Logs | Date, value (cups, minutes, kg…), logged time | On device (Room DB) |
| Mood notes | A 5-level mood and a one-line note you type | On device (Room DB) |
| Sleep records | Bedtime and wake time you enter yourself. Nothing is auto-detected. | On device (Room DB) |
| Reminder delay log | How late a reminder arrived (milliseconds), used only to decide whether to show a battery hint. No content is stored. | On device |
| Preferences | Theme, units, week start, app lock PIN | On device |
| Backup file | A JSON file you export yourself, to a location you choose. | Location you choose |
| Share text | When you tap share, today's progress is composed as text and handed to another app of your choosing. | Not stored |
None of the above is transmitted to any external server. There is no account, and the developer cannot access your records.
2. Permissions
| Permission | Purpose | Required |
|---|
| Notifications (POST_NOTIFICATIONS) | Habit reminders at the time you set | Optional |
| Exact alarms (SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM) | Needed to fire at the exact time you set. Without it Android batches and delays reminders. | Optional |
| Boot completed (RECEIVE_BOOT_COMPLETED) | Re-schedules alarms after a reboot. | Required |
| Battery optimisation exemption (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) | Used only to open the system settings screen when reminders arrive late. | Optional |
| Vibrate (VIBRATE) | Notification vibration | Optional |
| Internet / Advertising ID (INTERNET, AD_ID) | For ads only. Logging needs no network. | For ads |
3. App lock PIN
The 4-digit app lock PIN is stored as-is on your device. It hides the screen and is not encryption — do not rely on it for sensitive information. The PIN is never transmitted.
4. Advertising (third party)
Habit Builder shows ads via Google AdMob. AdMob (Google) may collect advertising ID and device information to serve ads. Users in the EEA and UK are shown a consent form (UMP) on first launch.
5. Retention & deletion
- All records stay on your device.
- Uninstalling the app permanently deletes all data. No separate deletion request is needed.
- A backup file you exported yourself remains where you saved it; deleting it is up to you.
6. Children
Habit Builder is not directed at children and does not knowingly collect personal information from children.
7. Contact
Privacy inquiries: [email protected]
8. Changes
Any changes to this policy will be posted on this page.
Crash reporting and usage analytics (Firebase) — added 2026-09-18
The app uses Google Firebase Crashlytics and Firebase Analytics (Google LLC) to collect diagnostic information when the app crashes or hits an error, and statistics about which screens and features are used.
- Data collected: crash logs (stack trace and the screen where the error occurred), device model, OS version, app version, an app-instance identifier (Firebase installation ID), app interactions (screen views, feature usage counts, session length, and the step and error type when a feature fails), and approximate location (country/region inferred from IP address).
- Not collected: name, email, contact details, or anything you type into the app.
- Purpose: fixing errors and improving the service. Not used for advertising or marketing.
- Processor: Google LLC (Firebase). Data is stored on Google servers.
- Retention: crash data for 90 days; usage statistics are deleted after the period set in Google's retention settings.
- Opt-out: this collection is required for the app to function and cannot be switched off individually. Uninstalling the app stops further collection.
Details: Google Privacy Policy · Privacy and Security in Firebase
Biometric unlock (app lock, added 2026-10-19)
If you turn on the app lock, you can unlock it with your phone's fingerprint or face recognition (USE_BIOMETRIC). The phone's operating system does the recognition and the app only receives success or failure. The app never stores or sends biometric data.
Payments (paid "Remove ads") — added 2026-10-26
- In-app payments are handled by the Google Play billing system. We never receive your card number or other payment details.
- In Google Play Console we can see the order number, product, date, amount and country of a purchase. We use them only to handle refunds and inquiries and to keep the transaction records required by Korean e-commerce law.
- The app stores your purchase status (subscribed / paid once) only on your device and re-checks it with Google Play when it starts.
- Payment steps (opening the payment sheet, result, purchase acknowledgement) and the purchase event Google Play reports (product, amount, currency) are processed by Firebase Analytics (test purchases are excluded).
- If you email us a refund request, we use that email and order number only to process the refund.
- Payment records (Google Play Console order records and refund-request emails) are kept for the periods required by Korean e-commerce law — contract and withdrawal records 5 years, payment and delivery records 5 years, complaint and dispute records 3 years — and then deleted.
- Terms, refunds and cancellation: Terms of Service
International data transfers
The app uses Google LLC services for crash reporting, usage analytics, ads and payments, so the data described above is processed on Google's servers. If you do not want this, you can avoid the feature or uninstall the app.
Updated 2026-10-26: added payments (paid "Remove ads") and payment-record retention.
Updated 2026-10-19: added international transfers, failure details in analytics, app name line.