ActionHabit Privacy Policy

Last updated: 2026-04-15

1. Controller and Contact

The formal provider details for the public ActionHabit website are not yet fully stored in the current repository.

Until the final provider details are published, privacy questions can be directed through the contact paths listed below.

Current contact path

  • Privacy: privacy@actionhabit.app
  • General support: support@actionhabit.app

2. Overview

ActionHabit is described as an action-oriented, login-based, and local-first app.

We process only the data required for core functionality, account assignment, synchronization, sharing, and the documented premium path.

We do not sell personal data.

We do not include advertising SDKs.

We do not track users across apps or websites for advertising purposes.

3. What data is processed

Depending on usage, the following categories of data may be processed

  • Actions, habits, goals, notes, and categories
  • Completion states, timestamps, and app-related history data
  • Shared contexts, people, or workspace references
  • Account data such as email address and technical account ID
  • Session- and sync-related technical data

4. Authentication and Accounts

In the current product state, normal app usage is tied to login.

Authentication is handled through Supabase. Only the data required for account identity, sign-in, and session handling is processed for that purpose.

When you delete your account, associated Supabase data is removed through the dedicated delete-account path.

5. Sync, Sharing, and Involved Services

ActionHabit intentionally separates its local product base from the sync or sharing paths that extend it.

Apple infrastructure

  • CloudKit and iCloud are used for Apple-near sync and sharing contexts.
  • In-app purchases and subscription handling run through Apple.

Supabase

  • Supabase is used for authentication, session state, private sync paths, and Shared or People contexts.

Local persistence

  • According to the product architecture, the local data base remains anchored in SwiftData.
  • Sync and sharing extend that base, but do not replace it as the local working foundation.

6. NFC-based Habits

When NFC-based habits are used, ActionHabit processes relevant tag data locally on the device.

The current privacy baseline describes NFC identifiers or payloads as being used in cryptographically derived form rather than stored as raw NFC content.

NFC is used to confirm physical action, not for general tracking purposes.

7. Analytics and Diagnostics

According to the current product state, ActionHabit does not use ad or third-party tracking SDKs for cross-app advertising.

Local analytics and status data may be used to make action behavior visible inside the product, for example through action rate or time-to-action.

Crash diagnostics and diagnostic analytics are currently described in the app text as disabled by default and manageable in Settings.

8. Premium and Payments

Premium functionality is provided through Apple In-App Purchases.

ActionHabit does not receive payment data from Apple.

Premium state is determined through StoreKit-based product and entitlement checks.

9. Retention, Deletion, and Backups

Local data remains on the device until it is deleted by the user or removed through an app reset.

When an account is deleted, associated Supabase data is removed through the dedicated product path.

Data stored in iCloud or CloudKit remains governed by Apple and the settings of the relevant iCloud account.

Depending on device or backup settings, local data may also be contained in system backups.

10. Your Rights

Questions about access, correction, deletion, or privacy in general can be sent to privacy@actionhabit.app.

If you want to remove your account, the app provides a direct deletion path.

11. Children

ActionHabit is not intended for children under 13.

No data is knowingly collected from children for targeted use.

12. Security

We rely on encrypted connections, platform-near security mechanisms, and a minimum-data-processing approach.

No system is absolutely secure, but the current product state is designed to use only the data paths required for the documented functionality.

13. Changes to this Policy

This Privacy Policy may be updated when product functionality, infrastructure, or regulatory requirements change.

The date shown on this page is the relevant version marker.