Habitly Logo Habitly
GitHub
View on GitHub v1.0.0

Habitly Privacy Policy

Effective Date: September 23, 2026 • Application: Habitly (com.smsram.habitly) • Developer: SMSRam
Summary of Privacy Principles: Habitly is built local-first. Your habits, logs, and routines are stored on your device in an encrypted local database. Habitly has no third-party tracking, sells no data, and requests only the minimal, non-sensitive Google Drive scope necessary to manage its own backup file when you explicitly choose to enable cloud backups.

1. Introduction

This Privacy Policy explains how Habitly ("the Application", "we", "us", or "our"), published by SMSRam, handles user information. Habitly is an Android mobile habit and routine tracking application built with Flutter, Dart, and native Android components.

We believe personal routines and self-improvement data should belong solely to the individual. By default, Habitly operates entirely offline and requires no account creation, email registration, or third-party login.

2. Information Stored Locally by Habitly

When you use Habitly, the following data is created and saved strictly within your device's local application storage sandbox (SQLite database habitly.db and Android SharedPreferences):

  • Habit Definitions: Habit titles, descriptions, tracking types (Done/Not Done, Count, Duration, Quantity, Rating, Checklist), target numbers, units of measurement, icons, and color preferences.
  • Schedules & Alarms: Configured days of the week, scheduled reminder times, and optional custom notification messages.
  • Completion History: Historical completion statuses, numeric values logged, streak calculations, and completion timestamps.
  • Application Preferences: Theme selection (Light, Dark, System), sound effects toggle, vibration settings, and reminder frequencies.

This data never leaves your device unless you explicitly initiate an export or connect your Google Drive account for backup synchronization.

3. Google Drive Cloud Backup & Google User Data

Habitly offers an optional cloud backup and restore feature via Google Drive. Using this feature is entirely voluntary.

3.1 Authorized Google OAuth Scope

Habitly connects to Google Drive using strictly the non-sensitive, restricted scope:

https://www.googleapis.com/auth/drive.file

What this means: This scope grants Habitly access only to the files that Habitly creates itself (specifically, habitly_backup.json). Habitly cannot view, read, search, list, modify, or delete any other files, spreadsheets, photos, documents, or folders in your Google Drive.

3.2 What Data is Transferred

When you trigger a manual backup or enable automatic backups, Habitly packages your local habit records, schedules, completions, and settings into an encrypted JSON payload (habitly_backup.json) and uploads it directly to your Google Drive via official Google APIs over HTTPS.

3.3 Use, Transfer, and Disclosure of Google User Data

We comply strictly with the Google API Services User Data Policy, including the Limited Use requirements:

  • Habitly uses your Google Drive access solely to provide user-requested backup and restore functionality.
  • Habitly does not transfer, sell, lease, or disclose Google user data to third parties, advertising brokers, data aggregators, or analytics services.
  • Habitly does not use Google user data for serving advertisements, training artificial intelligence or machine learning models, or tracking user behavior across other apps or websites.
  • Habitly does not maintain a private server or intermediary backend. All communication occurs directly between your mobile device and Google Drive servers.

4. Device Permissions

Habitly requests only permissions that are directly necessary to deliver its core features:

  • Notifications (POST_NOTIFICATIONS): Required on Android 13+ to deliver scheduled habit reminders, snoozed reminders, and incomplete habit follow-ups.
  • Exact Alarms (SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM): Required to trigger your daily habit reminders at the exact minute specified in your schedule.
  • Vibration (VIBRATE): Used to provide tactile haptic feedback when you mark a habit complete and to vibrate during reminder notifications if enabled.

5. Third-Party Services & Advertising

Habitly contains zero third-party advertising SDKs, zero tracking beacons, and zero telemetry frameworks. The only external service integration is the official Google Sign-In and Google Drive API libraries used exclusively for the optional cloud backup feature.

6. Data Retention & Deletion

6.1 Local Data Deletion

You can delete any habit, routine, or completion record at any time from within the app. You can erase all local data immediately by clearing the application storage in Android Settings or uninstalling the app.

6.2 Cloud Backup Deletion

You have full control over your cloud backups:

  • You can delete your cloud backup file at any time using the "Delete Backup" button within Habitly's Settings screen.
  • You can delete the habitly_backup.json file directly from your Google Drive storage management portal.
  • You can revoke Habitly's access to your Google account at any time via your Google Account Security Permissions.

Deleting a cloud backup does not delete your local habits, and deleting local habits does not delete cloud backups unless you perform a new sync.

7. Security

We prioritize the security of your data:

  • Local data resides within the private Android application sandbox, inaccessible to other apps without root permissions.
  • Cloud backups are transmitted directly to Google Drive over transport-layer encrypted channels (HTTPS/TLS).
  • Habitly does not collect, transmit, or store your Google account password. Authentication is performed via standard OAuth 2.0 authorization tokens managed securely by Google Play Services.

8. Children's Privacy

Habitly is a general utility application intended for personal routine tracking. We do not knowingly collect, solicit, or store personal information from children under the age of 13. If you believe a child has provided us with personal information, please contact us so we can assist in removing it.

9. Changes to this Privacy Policy

We may update this Privacy Policy from time to time to reflect improvements to Habitly or changes in legal regulations. When updates occur, the revised policy will be posted on this page with an updated Effective Date. We encourage you to review this page periodically.

10. Contact Information

If you have any questions, feedback, or concerns regarding this Privacy Policy or your data, please contact the developer: