HABITMUSE · BY JEWELTRONS
Privacy policy
How Jeweltrons handles information when you use HabitMuse and this website.
Last updated: 29 September 2026
Your private habits are stored locally. Google sign-in and Drive backup are optional. Public feedback is public. Analytics, crash reporting, and replay are opt-in. Ads have separate privacy choices.
Who we are and how to contact us
Jeweltrons is the publisher of HabitMuse and operates this website. For privacy questions or requests, email jeweltrons@gmail.com. This policy covers the app and the Jeweltrons website; the sections below explain which services apply to each.
Private information on your device
HabitMuse stores habits, progress, history, reflections, reminder schedules, coaching records, and preferences locally on your device. Private habit records are not uploaded to Firebase Firestore. Removing the app or clearing its storage can remove local data. Exports you create or share are under your control and may be stored by the destination you choose.
Notification and alarm permissions support on-device reminders. HabitMuse does not need to publish your habits for core tracking to work.
Optional Google account and backup
If you sign in, Google and Firebase Authentication provide an account identifier, display name, email address, and profile image. Authentication tokens enable the optional services you request.
When you choose backup, HabitMuse writes a backup to your Google Drive app-data folder. Backups may include habits, progress, reflections, groups, preferences, coaching records, and locally stored feature-access records. HabitMuse requests access to its own app-data folder, not general access to browse your Drive files. Backup data is used to provide backup and restore, not to target advertising.
Community and recovery feedback
Community feedback in Firestore includes submitted text, account identifiers, timestamps, and votes. Community posts can be read publicly; do not include private habit details or sensitive information. Moderation reports privately include reporter and author identifiers, a copy of the reported public post, the reason, and review status. Blocked-author preferences are stored on your device.
Recovery feedback is different: when you submit it, your message is sent to Sentry and is not posted publicly. Error details are linked only when crash reporting is enabled. If you also enabled session replay, a masked replay may accompany feedback. Do not put secrets or sensitive information in feedback.
Optional analytics, crash reports, and replay
Usage analytics and crash reporting are independently off until you opt in. Firebase Analytics measures feature use, app activity, and retention, including interactions with Pro offers, rewarded ads, reward recovery, and unlocked features. Events exclude habit names, notes, history, and payment details. Firebase receives app/device metadata and installation identifiers and can derive approximate location from the network address.
Sentry receives sanitized errors, native crashes, supported hangs, app/device metadata, and installation identifiers when crash reporting is enabled. Automatic reports exclude habit content and account details. HabitMuse does not attach advertising identifiers or your Firebase account ID to telemetry. Standalone error screenshots, console capture, tracing, and profiling are disabled.
Session replay is separately off until enabled. It may send sampled recordings around errors, with text, images, and vectors configured to be masked and network bodies excluded. Turning off crash reporting also turns off replay.
Change choices in Settings under usage analytics / Help improve HabitMuse. Consent stays on this device and is excluded from Drive and operating-system backups. Turning sharing off disables collection and retires queued crash reports. It cannot recall reports already sent.
Optional rewarded ads
HabitMuse integrates Google AdMob and requests non-personalized ads. Habit names, progress, reflections, and account details are not added to ad requests. Google’s ad SDK may process IP addresses, approximate location, device identifiers, ad interactions, and diagnostics for delivery, measurement, and fraud prevention, subject to applicable consent choices.
Ads may be prepared once Google’s consent system permits requests. Watching a rewarded ad is optional. Where available, Settings → Ad privacy choices lets you review your choice. Advertising consent is separate from analytics and crash-reporting choices. Non-personalized does not mean no data is processed.
This website and support email
This informational website does not set application cookies, use visitor analytics, embed ads, or include tracking scripts. Hostinger hosts the pages and may process technical request information, such as IP address, requested URL, browser information, and request time, for delivery, security, and service operations.
If you contact us by email, we receive your email address, message, and any attachments you choose to send. We use them to respond, troubleshoot, or handle your request. Email links open your email service; they do not submit a message automatically.
Providers, sharing, and security
Google/Firebase provide authentication, Drive backup, community storage, analytics, and advertising as described above. Sentry provides optional diagnostics and recovery-feedback delivery. Hostinger provides website hosting; Google’s email service processes email sent to our support address. Providers may process data in countries other than yours.
We do not sell your private habit records. Information may be disclosed when required by law or needed to protect users and investigate misuse. No storage or transmission method is completely risk-free. Protect your device and Google account.
Provider information: Google Privacy Policy, Firebase privacy information, Sentry Privacy Policy, and Hostinger Privacy Policy.
Retention and deletion
Local records remain until you remove them or clear the app’s local data. Your Drive backup remains until you remove the hidden app data. Online account and community records remain until deletion or moderation removes them. Account deletion removes associated account and vote records, removes reports you submitted, and anonymizes authored feedback while removing its text.
Reports by other users and moderation restrictions may be retained while needed for abuse review and prevention. Service logs and previously sent analytics/diagnostics follow the configured provider retention settings; account deletion does not automatically erase telemetry that is not linked to your account. Support correspondence is kept while needed to address the request and for legitimate security or legal requirements.
To request access, correction, or deletion, email us. We may need to verify ownership; we cannot directly access local-only habits or erase files from your device or your Google Drive on your behalf. For steps and an external request option, visit Account & data deletion.
Changes to this policy
We will update this page and its date when our data practices change. Please review it when using new optional features. Contact jeweltrons@gmail.com if anything is unclear.