Heardex ("we", "our", or "us") explains here what personal data is handled in the current implementation of the service.
Last Updated: 2026-06-02
We collect data through authentication, user profile setup, and in-app activity when you use Heardex.
In the current implementation, data is stored in Supabase Auth and Supabase database tables.
Heardex currently uses Google Sign-In via Supabase OAuth. We receive provider-derived user information as supplied by Supabase user metadata.
This may include account name variants (for example display_name, full_name, name, username, user_name) and avatar fields (for example avatar_url or picture), depending on provider response.
Heardex does not currently implement a Spotify OAuth flow or Spotify account-linking storage for users in this codebase.
We do not use third-party ad-tech or behavioral analytics SDKs. First-party page access logs are stored in our database for operational metrics such as unique active visitor counts.
We collect and use user information solely to operate, maintain, improve, secure, and provide Heardex.
Account-linked data is retained while your account remains active unless deletion or legal obligations require otherwise.
Heardex is operated and maintained by an individual developer. When reasonably necessary for service operation, maintenance, security, legal compliance, migration, bug fixes, infrastructure changes, or service discontinuation, user data, generated statistics, stored records, settings, and related service information may be modified, reset, archived, or deleted.
We make reasonable efforts to avoid unnecessary data loss, but we cannot guarantee permanent retention of user data.
To request deletion of your account-related data, contact us at example@gmail.com with your account UID and request details.
Subject to applicable law, you may request access, correction, or deletion of personal data we store about you by contacting us at example@gmail.com.
We may update this Privacy Policy from time to time. Updates become effective when posted on this page, with the Last Updated date revised accordingly.