Skip to content
TUNEKINBack to TuneKin

LAST UPDATED 10 AUGUST 2026

Privacy notice

This notice explains what TuneKin collects, why it is used, who receives it, and the choices available to you.

Beta notice

This is TuneKin's working policy for the private beta. Final legal review and confirmation of the privacy contact mailbox are required before public launch.

Who is responsible

TuneKin is the controller of personal data used to run the service. Contact us through Feedback while signed in. The intended privacy address is privacy@tunekin.com; that mailbox and the controller's full legal identity must be confirmed before public launch.

What we collect

  • Account data such as email address, authentication records, handle, display name, profile text, location, avatar, and privacy choices.
  • Activity you choose to create, including follows, blocks, posts, comments, reactions, lists, shelves, recommendations, saves, reports, and feedback.
  • Safety and technical records, including hashed network identifiers, moderation decisions, security events, error digests, page paths, device and performance information.
  • Music metadata and identifiers returned by Spotify when you search or share music. TuneKin does not receive your Spotify password and currently does not import your Spotify listening history.

Why we use it

  • To provide your account and the social features you request, relying on performance of our agreement with you.
  • To secure, moderate, debug, measure, and improve TuneKin, relying on our legitimate interests in operating a safe and reliable service.
  • To meet legal duties, respond to valid requests, and protect people from serious harm where the law requires or permits it.
  • For optional uses that require consent, where we ask for it. You can withdraw consent without affecting earlier lawful use.

Who receives it

We use service providers to operate TuneKin: Neon for authentication and Postgres data, Vercel for hosting, analytics, performance monitoring, and avatar storage, Spotify and MusicBrainz for music search and outbound links, Cover Art Archive for release artwork, and OpenAI for contextual moderation when that layer is enabled. Music search terms are sent to the catalogue providers needed to answer the search. They receive only the information needed to provide those services under their own contracts and safeguards.

Some providers may process data outside the UK. Before public launch, TuneKin must document the relevant transfer mechanism and provider terms. We may also disclose information where required by law or urgently needed to protect someone from serious harm.

Visibility

Your handle, display name, avatar, bio, follower counts, and content can be visible to other TuneKin users. If public-profile visibility is enabled in Profile settings, the selected profile information can also appear on the public web. Blocking limits interaction and discovery between accounts, but it does not erase copies already lawfully retained for safety or compliance.

Retention

Account and content data is kept while your account exists. Account deletion removes your profile, posts, lists, saves, recommendations, and authentication account. Limited safety, moderation, backup, transaction, or legal records may be retained only as long as reasonably needed for those purposes. Exact production retention periods and backup deletion timing must be approved before public launch.

Your rights

Depending on the law that applies, you may ask for access, correction, deletion, restriction, portability, or object to certain uses. Account settings already provide a JSON export and account deletion. Use Feedback or the intended privacy address for other requests. You may complain to the UK Information Commissioner's Office at ico.org.uk.

Children and automated decisions

The current private beta is not offered to people under 18. TuneKin does not use solely automated decisions that produce legal or similarly significant effects. Automated moderation can flag or block high-risk text, with human review and an appeal route through Feedback.

Changes

We will update the date above and explain material changes in the product. We will ask for consent again where a new use legally requires it.

TermsPrivacyCommunity rules