Privacy Notice

1. Who controls your data

Oberil LLC is the operator of Hand Karaoke and the service data controller. Its mailing address is 30 N Gould St, Ste N, Sheridan, WY 82801, United States. Privacy questions and rights requests may be sent to help@oberil.com. Identity verification may be required before a request is completed.

2. Data we process

Account

Google/Supabase user identifier, email address, display name, avatar, session and CSRF security data.

Saved activity

For signed-in accounts, bookmarks, voice-effect identifiers, remix drafts, published harmonic arrangements, reports, moderation decisions, and revision history. Guest remix experiments remain in browser memory for the current panel session and are not saved or uploaded unless you sign in and explicitly save or publish.

Search, range matching, and discovery signals

The live static-guide library is delivered with the application, and its search and singer-range matching run in your browser. Community-arrangement discovery requests are sent through Cloudflare to Supabase using bounded guide identifiers rather than raw search text. Hand Karaoke does not intentionally write raw search text or range filters to its application database, interaction records, paywall records, or allowance records. Infrastructure providers may process request fields for delivery and security under their own retention practices. For signed-in accounts only, Hand Karaoke stores daily-deduplicated song interactions that are used after a minimum audience threshold.

Free performance allowance

For guests, the current UTC-day balance and bounded same-song deduplication timestamps are stored only in browser local storage and are never sent to Hand Karaoke servers. For signed-in Free accounts, a UTC-day total of active performance seconds and meaningful song starts is server-authoritative. A bounded canonical song key and server timestamp are temporarily used to avoid counting the same song again within 30 minutes. Short-lived opaque meter identifiers use server timestamps to measure active playing. No camera video, microphone audio, chord, preset, query, IP address, user agent, referrer, timezone, or arbitrary metadata is stored in these allowance records.

Local processed voice loops

When you explicitly press the processed-voice record control, the selected wet voice-effect output is captured as mono audio in volatile browser memory for local loop playback. Raw or dry microphone input is excluded from the capture path. Voice-loop audio is not uploaded, synchronized, cached, exported, or written to local storage, and disappears when cleared, replaced, or the page closes.

Billing

Current Stripe Sandbox customer, Checkout Session, test-subscription, price, status, cancellation, webhook, and versioned legal-acceptance records. Sandbox Checkout makes no real charge. If live billing launches, equivalent live subscription, renewal, tax, dispute, and payment records will be processed as disclosed at that time. Complete payment-card details stay with Stripe.

Device preferences

Settings such as volume, color and pad controls, focus mode, singer-range choice and setup completion, panel positions, and login preference may be stored locally in your browser.

Security and delivery

Cloudflare, Supabase, and other infrastructure providers may process IP address, request timing, URL and request fields, and technical request data to deliver and secure the service. Hand Karaoke does not add IP addresses, user agents, referrers, or arbitrary metadata to popularity, paywall, or allowance measurement records.

3. Why and on what basis

Provide the service

To authenticate accounts, synchronize settings, save arrangements, provide test-mode Pro access, and, if live billing launches, manage paid subscriptions. For UK/EEA users, the basis is performance of a contract.

Security and integrity

To prevent abuse, protect accounts, enforce limits, review community reports, remove arrangements that violate service rules, preserve billing records, and diagnose failures. The basis is legitimate interests and, where applicable, legal obligation.

Test billing, future payments, and law

To operate the current Stripe Sandbox flow and preserve its security records. If live billing launches, to process subscriptions, taxes, disputes, refunds, accounting, and lawful requests. The basis is contract, legitimate interests in securing the test flow, and legal obligation where applicable.

Consent

Where law requires consent, such as non-essential browser storage or a particular optional feature, consent is requested separately and may be withdrawn.

4. Sharing and processors

Data is shared only as needed with service providers acting for or with Hand Karaoke: Google for sign-in; Supabase for authentication and database services; Cloudflare for hosting, caching, security, and delivery; Stripe for current Sandbox Checkout and, if live billing launches, subscriptions, billing management, fraud prevention, and payment processing; and professional advisers or authorities where legally required.

Published community arrangements and aggregated discovery ordering are public. Public arrangements use generic attribution and may remain available after account deletion with ownership removed. Reports and moderation decisions are not public; authorized operators use them to dismiss reports or remove public arrangements.

5. International transfers

Providers may process data in the United States and other countries. Where UK, EEA, or other law requires transfer safeguards, the relevant provider terms and lawful transfer mechanisms apply. Consult Google, Supabase, Cloudflare, and Stripe privacy materials for their processing locations and safeguards.

6. Retention

• Account data and private saved activity are kept while your account is active. A deletion request immediately restricts the account and starts a 30-day pending-deletion period. During that period, this data is retained for recovery. You must explicitly reactivate before the stated deadline, and only after Stripe Checkout and subscription cleanup has been verified. Signing in alone does not reactivate the account. Reactivation never restarts or creates a subscription; a new subscription requires a separate Checkout and consent.
• Published arrangements may remain available after account deletion with ownership removed.
• Reports, moderation decisions, and associated revision history are retained as reasonably necessary to enforce service rules, handle repeat reports, and document removal decisions.
• After the recovery deadline, account data and private saved activity are permanently purged once Stripe cleanup is verified, subject to the published-arrangement and moderation exceptions above and the minimal archive below. Cleanup failures remain pending for retry and do not extend the recovery deadline.
• While needed to operate billing and complete deletion cleanup, webhook event identifiers and current subscription projections prevent replay and maintain authoritative billing state. At final deletion, only minimal billing identifiers, billing state and period information, and versioned consent records are retained in a restricted archive for seven years from final deletion, then purged. This is our retention policy for billing accountability and evidence of consent, not a claim that every jurisdiction requires seven years. The archive excludes full profiles, authentication or session tokens, and audio. Access is limited to authorized personnel for these retention purposes.
• Prior-day guest allowance data is ignored and replaced on the next app use after UTC midnight, and can be removed by clearing browser storage. A signed-in daily allowance total remains until the account next records allowance activity on a later UTC day, when prior daily totals are deleted, or until account deletion. Song dedupe keys expire after the 30-minute counting window and active-meter leases expire after 30 seconds without a checkpoint; expired records are removed opportunistically during allowance use.
• Processed voice-loop audio remains only in volatile browser memory until you clear or replace the loop, close or reload the page, or the browser ends the session.
• Local browser preferences remain until you clear them or browser storage.

7. Your choices and rights

You may review account information, manage billing, sign out, and request account deletion through the Account panel. A request immediately restricts your account and gives you 30 days to explicitly reactivate through Account, after Stripe cleanup has been verified. Signing in alone does not cancel deletion, and reactivation does not resubscribe you. After the stated deadline, recovery is unavailable and permanent deletion proceeds once cleanup is verified. Failed cleanup remains pending for retry without extending that deadline. Published harmonic arrangements may remain available with ownership removed; the restricted seven-year archive described above is retained after final deletion. Depending on where you live, you may also have rights to access, correct, delete, restrict, object to, or receive a copy of personal data, and to complain to a privacy regulator. Submit requests privately using the contact method above. Identity verification may be required.

UK users may complain to the Information Commissioner's Office. California residents may review the California Attorney General's privacy information. Hand Karaoke does not sell or share personal information for cross-context behavioral advertising and does not discriminate for exercising privacy rights.

8. Cookies, local storage, and browser signals

Hand Karaoke uses security/session cookies and local browser storage needed for sign-in, CSRF protection, settings, and continuity. It does not currently use advertising cookies or third-party behavioral analytics. Because no cross-site behavioral tracking is performed by Hand Karaoke, browser Do Not Track signals do not change service behavior. Legally recognized opt-out preference signals are honored where applicable to processing covered by those signals.

9. Children

Hand Karaoke is not directed to children under 13 and does not knowingly create accounts for them. A parent or guardian should contact us privately if they believe a child provided account information.

10. Changes

Material changes will be posted with a new effective date and presented for renewed acceptance where required. Earlier versioned acceptance records may be kept to document the terms governing a transaction, subject to the retention period in section 6.