Privacy policy

Updated October 26, 2026

This notice explains the account, sign-in and project data used by Karaoke Maker 3000 at karaokemaker3000.art. For privacy questions or requests concerning your account data, contact support@karaokemaker3000.art.

Data used by the service

The service uses your account identifier, display name and available verified email address to identify your workspace. If you use Telegram, it also uses your Telegram account identifier. Your uploaded audio, lyrics, project settings, generated files, processing status and balance records are associated with that workspace.

Google sign-in

When you choose Google sign-in, Google supplies a stable account identifier, email address, email verification status and basic profile information such as your name. We use the identifier to recognize your account and the name to display it. A Google-hosted verified email may also identify an existing account. For other email providers, Google sign-in alone does not establish current ownership of an existing email account.

The requested permissions are openid, email and profile. The sign-in integration does not request permission to read Gmail messages, Google Drive files, contacts or calendars. Your Google password is entered on Google's pages, not on this service.

Google authorization tokens are used during the sign-in exchange and are not retained by this integration after it completes. The service stores the Google account identifier associated with your account. Connecting Google to an existing account keeps that account's projects and balance together; it does not automatically merge separate accounts.

How data is used and processed

Account data supports authentication, access to your projects, account linking and support. Audio, lyrics and project settings support processing and export. Transaction records support balances and payments. Depending on the features you use, the service relies on hosting and storage providers, audio and text processing providers, email delivery services, Google or Telegram for authentication, and payment providers for checkout. These providers receive data needed to perform their part of the service.

Operational logs and, when enabled, usage analytics help diagnose errors and understand use of the service. Google authorization codes and tokens are excluded from sign-in error messages and logs.

Optional analytics and diagnostics

If you accept analytics, we use Google Analytics 4 to understand traffic sources and how visitors sign in, upload audio, use the editor, export videos and top up their balance. Google receives browser and device information, an analytics browser identifier, coarse page names, campaign tags and selected product events. A confirmed top-up can be linked to that browser and recorded with the USD value of service credit added to the balance. This value is not a statement of payment-provider fees or cash revenue.

Google Analytics does not load until you accept. Advertising storage, Google signals and ad personalization are disabled. We do not send email addresses, account names, Telegram identifiers, song titles, lyrics, uploaded files, authentication tokens or complete private URLs. Existing first-party operational and Umami telemetry uses a separate minimized event pipeline.

Better Stack receives minimized operational events and, after analytics consent, browser errors and web performance measurements. Error messages, request contents, private URLs, media and form values are removed before forwarding. Session replays, console capture, automatic interaction capture and browser fingerprinting are disabled. Telemetry is stored in the United States; operational events currently have a three-day retention period. This monitoring is best effort and is not a financial audit ledger.

Use the Analytics preferences button on this website to decline or withdraw your choice at any time. Withdrawing stops subsequent optional Google Analytics and Better Stack browser events, removes this site's analytics cookies and requests removal of analytics attribution from your pending top-ups. It does not delete events already delivered to Google. Do Not Track and Global Privacy Control are respected. See how Google uses information from sites and apps.

Cookies and storage

The website uses an HTTP-only authentication cookie and a temporary OAuth cookie. Website sign-in sessions expire after 30 days unless revoked earlier; pending OAuth state expires after 10 minutes. Logging out revokes the current website session. Account, project and transaction records are stored separately from the browser session.

Your optional analytics choice is stored in this browser for up to 180 days. After acceptance, first-party Google Analytics and Better Stack cookies identify the browser and session. These optional identifiers are separate from sign-in cookies and can be removed by withdrawing analytics consent.

Your choices and requests

You can choose whether to use Google sign-in, cancel the Google consent flow, log out, and delete projects using the account interface. You can review the service's connection in your Google Account settings. To request access to or deletion of account data, or to resolve an account-linking issue, contact the address above and identify your account. Do not send passwords or sign-in codes.