Heardex

© 2026 Heardex. All rights reserved.

  • Privacy Policy
  • Terms of Service
  • About
  • User Manual
  • Contact

Privacy Policy

Heardex ("we", "our", or "us") explains here what personal data is handled in the current implementation of the service.

Last Updated: 2026-06-02

1. Data We Collect

We collect data through authentication, user profile setup, and in-app activity when you use Heardex.

  • Authentication identifier (UID) issued by Supabase Auth.
  • Google account fields made available via OAuth metadata (for example name-related fields and avatar URL).
  • Email address via authenticated user context from Supabase Auth.
  • Profile preferences and account flags (for example display name and preferred language).
  • User activity data (for example followed artists and attended gigs with optional notes).

2. How Data Is Stored

In the current implementation, data is stored in Supabase Auth and Supabase database tables.

  • Supabase Auth stores account-level data such as UID, email, and provider metadata.
  • The profiles table stores UID-linked fields including username, display name, avatar URL, preferred language, registration status, and plan/developer flags.
  • The user_artists and user_gigs tables store UID-linked usage/activity data, including attendance metadata and optional memo text entered by users.

3. Authentication Providers

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.

4. Third-Party Services

  • Supabase (authentication, database, and session management).
  • Google OAuth (authentication provider).
  • Cloudflare/OpenNext deployment infrastructure (service hosting and delivery).

Heardex does not currently implement a Spotify OAuth flow or Spotify account-linking storage for users in this codebase.

5. Cookies, Local Storage, and Tracking

  • Supabase session cookies are used for authentication/session continuity.
  • A locale cookie is used to persist language preference.
  • An anonymous visitor identifier cookie and local storage entry are used to measure unique active visitors; page URLs are logged server-side for aggregate usage statistics.
  • Browser local storage is used to cache locale preference.
  • Browser session storage is used for post-login return path handling.

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.

6. How We Use Your Information

We collect and use user information solely to operate, maintain, improve, secure, and provide Heardex.

  • We do not sell user information to third parties.
  • We do not use user information for unrelated commercial purposes.
  • We do not use user information outside the scope of providing Heardex, except where required by law or reasonably necessary for service operation.

7. Data Retention, Operational Changes, and Deletion Requests

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.

8. Your Rights and Choices

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.

9. Policy Updates

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.