Privacy Policy for HabitBalance

Effective Date: April 8, 2026

Thank you for choosing to be part of our community at HabitBalance (“we”, “us”, or “our”). We are committed to protecting your personal information and your right to privacy.

1. Information We Collect

We do not collect, store, or share any of your personal data on our servers. HabitBalance is designed with privacy in mind. All of your data—including your habits, gym performance metrics, history, and settings—is stored entirely locally on your device.

2. API Keys and Third-Party Services (Anthropic)

To power the AI-assisted history and progress commentary features, HabitBalance allows you to enter an API key for Anthropic’s Claude API.

  • Security: Your API key is encrypted and stored locally on your device. It is never transmitted to us or any servers other than Anthropic’s secure endpoints.
  • Data Transmission: When you request an AI summary, the app sends a snapshot of your local habit and gym timeline data directly to Anthropic’s API to generate a response.
  • Third-Party Privacy: By using this feature, you agree that your submitted prompts and timeline data are subject to Anthropic’s Privacy Policy. We strongly recommend reviewing Anthropic’s Privacy Policy to understand how they handle data sent to their API.

3. Local Storage Management

Because all data is stored locally on your device:

  • If you uninstall the application without a backup, your habit and system data will be permanently deleted.
  • When you interact with the app, the local database (Room) and preferences (DataStore) are updated purely on your hardware.

4. Changes to This Privacy Policy

We may update our Privacy Policy occasionally. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted on this page.

5. Contact Us

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at the repository’s GitHub Issues page.