Privacy notice

Free beta · 18 October 2026. Features described here apply when available. Paid credit purchases are currently closed.

Controller and contact

The controller responsible for Karaoke AI's processing of personal data is:

Data we handle and why

• Your requests: audio, source links, titles or filenames, supplied lyrics, generated audio and timed lyrics, and job status. These are processed to provide the service you request (GDPR Article 6(1)(b)). Do not upload sensitive personal information you do not want processed.
• Accounts and purchases, when enabled: Clerk handles sign-in details, including email and session information. Our application stores a linked account identifier, library, credit ledger and order/payment references. Stripe handles checkout details, including payment and tax/billing information; card details are entered on Stripe. Account and order handling supports the contract; legally required accounting records are processed under Article 6(1)(c).
• Service records: job identifiers, timestamps, errors, processing usage, browser/device categories and job-linked use/download events help operate, troubleshoot and protect the service. Hosting providers also receive connection information such as IP addresses. Security and abuse prevention rely on legitimate interests (Article 6(1)(f)). These records are separate from optional analytics.

Cookies, browser storage and optional analytics

Browser storage remembers consent and, in the older account-free experience, a device identifier for limits and a local track history. Sign-in services use session storage and cookies when enabled. Clearing browser history does not erase server records.

Where enabled, Google Analytics loads only after you allow analytics. It can receive cookie identifiers, connection/device information, page categories, traffic attribution, actions and job/track/attempt identifiers. Our event code excludes audio, lyrics, titles, filenames and email fields; that does not make the analytics anonymous.

Google Analytics event and user data retention is set to 14 months. The user-data period resets on new activity. These settings do not limit how long Google keeps aggregate reports.

Separately, optional first-party usage counts store daily page/action totals without visitor identifiers in that counter table. Their requests still pass through hosting infrastructure. These counts also require analytics consent and are kept for 90 days.

Consent is the basis for optional analytics (Article 6(1)(a)). Use Cookie settings in the footer to allow or reject it where available. Your choice is remembered for 180 days; withdrawing consent stops future optional collection and may reload the page. It does not undo earlier processing or disable sign-in, payments or service records.

Providers and access

The service uses Netlify for the website, Railway for the application/storage, Replicate for audio separation and Deepgram for transcription. Processing sends audio to the relevant AI provider. YouTube receives import requests when that feature is used. Clerk, Stripe and Google receive data for their respective features when enabled. YouTube imports may use DataImpulse for proxy routing. An optional external feedback form is governed by the form's own notice.

Account result pages require the owning account; short-lived audio links can be used by anyone who possesses a valid link. Older account-free result links may be accessible without sign-in. Matching requests may reuse cached media. Access controls reduce risk, but we cannot promise absolute security.

Providers may process data outside the EEA and keep their own service records beyond our media-access deadline. Contact us for information about the providers and transfer arrangements applicable to your request. We do not promise EEA-only processing or simultaneous deletion of every provider-held copy.

Retention and deletion

Account trial media access lasts 7 days and paid-result access 6 calendar months, measured from completion. Shared cached media may remain while another valid result still needs it. Result expiry is not deletion of all account or transaction records.

Removing a track from My tracks hides it and revokes that account's access; it does not immediately erase the underlying files. Contact us for account closure or erasure. Identity deletion revokes access when its notification is processed; local erasure requires a separate operator step. Limited disabled-account, credit and payment records may remain for abuse prevention, legal obligations or claims.

Technical ledgers do not currently have automatic expiry. Account and credit records support access to your library and unexpired credits; limited records may also be needed for accounting, abuse prevention or legal claims. Retention is reviewed by the operator when handling closure or erasure requests. Backups and provider-held copies are separate; you can ask which records remain and why.

Your rights

Subject to applicable conditions, you may request access, correction, erasure, restriction or portability, object to legitimate-interest processing, and withdraw consent. Contact info@karaoke-ai.com; we may need to verify your identity. You may complain to Poland's supervisory authority, UODO, or another competent authority. Data needed to fulfil a request or verify an account is necessary for that feature; optional analytics is not. We do not use these data to make solely automated decisions with legal or similarly significant effects.