Privacy Policy

Last updated: August 10, 2026

In brief

We collect only what we need: for DJs, account and event data; for event visitors, song requests and timestamps (no account required). We do not sell your data. Payments are handled by Stripe—we never see or store your card details. Correct account details in DJ Admin. Pro includes a convenient CSV export of your events and song requests; that is a product feature, not a limit on privacy rights. For access, a copy of your data, account closure (email only today), or other privacy requests (any plan), email PlayThisLive@Gmail.com with the subject line "Privacy request"; we aim to respond within 30 days and within the time required by applicable law. Analytics stay off until you change .

Who We Are

PlayThis.Live is operated by Katazui. For privacy questions or requests, contact us at PlayThisLive@Gmail.com.

Our Commitment to Your Privacy

Welcome to PlayThis.Live! We value your privacy and are committed to being transparent about the data we collect and how we use it.

How We Use Information (Purposes)

We use personal information for these purposes:

  • Account and service operation – Create and manage DJ accounts, events, song-request queues, playlists, and related features.
  • Billing – Manage subscriptions through Stripe (we store Stripe IDs only).
  • Security – Authenticate users, verify email, optional 2FA, rate limiting, and abuse prevention (including reCAPTCHA where configured).
  • Communications – Transactional email (verification, password reset, billing, security). Optional product and marketing email if you opt in.
  • Product improvement – Page-view and usage analytics (when you accept cookies) that do not include your name or email.
  • Optional companions – Mac menu bar app, web push, and Even Hub / G2 glasses HUD when you choose to use them.

What Information We Collect

We collect only what is necessary to run the service. We split this into groups:

Data we collect for DJ accounts

When you sign up and use the app as a DJ, we collect:

  • Account details – Name, email, and username.
  • Profile – Display name, bio, profile image, banner color, social links, timezone, public/private profile settings, and tip-jar handles (e.g. Venmo or Cash App) if you set them.
  • Consent records – When you accept the Terms, marketing opt-in or opt-out, and related preference timestamps.
  • Google sign-in (optional) – If you sign in with Google or link your Google account in DJ Admin → Settings → Account & Security, we receive from Google your email, name, and profile picture (if provided). We store a secure link between your PlayThis.Live account and your Google account so you can sign in with either method. We do not receive or store your Google password. See Google's Privacy Policy.
  • Events you create – Event names, descriptions, locations, dates, settings, and any event-level password or profile password you set (e.g. for private DJ profiles). Event and profile passwords are stored in recoverable form so you can re-share them with guests and so we can send you event reminders that include the password—they are not hashed like your login password. Do not reuse personal account passwords for event or profile gates.
  • Subscription linkage – We store only the Stripe customer and subscription IDs so we can manage your plan. We do not store or see your payment card details; Stripe handles all payment data.
  • 2FA settings – If you enable two-factor authentication, we store what is needed to verify your login (e.g. TOTP secret); backup codes are shown once for you to save.
  • Web push (optional) – If you enable browser notifications, we store a push subscription endpoint, encryption keys, and optionally your browser user agent so we can alert you when new song requests arrive. You can disable notifications in your browser or DJ settings.

Data we collect when someone uses an event (attendees / song requests)

When someone submits a song request at an event:

  • Song request data – Song title, artist, and related metadata; we record when the request was made to manage the queue. Attendees do not need to create an account. We do not collect attendee name or email to submit a request.

Even Hub / G2 glasses

If you use PlayThis.Live on Even Realities G2 glasses via Even Hub, we handle data as follows:

  • Sign-in handoff – You authenticate in a browser (or complete the glasses auth flow). We create a short-lived server-side auth session to complete the handoff.
  • Device token – After sign-in, a glasses access token (JWT) is stored on the device (browser or Even Hub local storage) so you stay signed in. Sign out or clear app storage to remove it.
  • Account data – The glasses HUD loads your DJ events and song requests from PlayThis.Live. It does not create a separate store of attendee personal information.

Even Hub and the glasses runtime are provided by Even Realities. See Even Realities' Privacy Policy (Device & App).

Mac menu bar app

If you use the optional PlayThis.Live Mac menu bar companion app, we handle data as follows:

  • Sign-in – You log in through your web browser; the Mac app never receives or stores your password.
  • Local token – After sign-in, a secure access token is stored in the macOS Keychain on your device so you can stay signed in. Sign out in the app to remove it.
  • Account data – The app loads your DJ events and song requests from PlayThis.Live so you can view and moderate the queue from the menu bar.
  • Notifications (optional) – If you allow macOS notifications, the app can alert you when new song requests arrive. You can disable this in System Settings at any time.

Emails

We send transactional email (account verification, password reset, billing, security notices) through Resend. If you opt in to product updates or marketing at signup or in settings, we may send those emails and sync your contact to our Resend audience. You can change marketing and policy-update preferences anytime in DJ Admin → Settings → Email preferences, or use unsubscribe links in emails.

reCAPTCHA

On registration and password-reset (and on login when enforcement is enabled), we use Google reCAPTCHA v3 to help prevent abuse. Google may receive device and IP-related signals for that check. See Google's Privacy Policy.

Technical data, logs, and IP addresses

To operate, secure, and troubleshoot the Service, we and our infrastructure providers may process:

  • IP addresses and request metadata – Used for rate limiting, abuse prevention, reCAPTCHA verification, and security audit logging (for example around 2FA events).
  • Browser or device signals – Such as user agent, when needed for push subscriptions, security, or compatibility.
  • Server and platform logs – Hosting (Vercel) and database (Neon) systems generate operational logs in the normal course of running the Service. We use these for reliability, debugging, and security—not for advertising.

We retain technical and security logs only as long as needed for those purposes or as required by our providers' standard practices, then they age out or are deleted in the ordinary course.

Usage data

When you accept analytics cookies, we collect usage metrics such as page views, navigation paths, and general interaction patterns (e.g. which pages are visited) via Vercel Analytics. This does not include your name or email. We use it to improve the product, fix issues, and understand how features are used. You can opt out via our ; your choice stays on this device until you change it.

Important note

We limit collection to what is needed to run the Service. We do not sell your data to third parties.

What We Do Not Do

  • We do not sell your data to third parties.
  • We do not use your song requests or account data for advertising or cross-site tracking.
  • We do not store your payment card details; Stripe handles all payment data.
  • We do not require attendees to create an account or provide name or email to submit a song request.

Data Retention

Song requests are stored for as long as the event exists and for the DJ who owns the event to manage the queue and history. We may retain aggregated or de-identified insights to improve the product. DJ account login and profile data is retained until an account deletion request is fulfilled (see below).

Account deletion (email only)

There is no self-serve "delete account" button today. To close your DJ account, email PlayThisLive@Gmail.com with the subject line "Privacy request" or "Account deletion." After we verify your identity and process the request:

  • Removed or closed – Your account credentials and personal profile details (such as email, name, bio, profile image, and similar account fields), and event fields such as location and description.
  • May be retained – Event name, event date/time, and the songs / song requests associated with those events (for history, integrity of shared catalogs, and product improvement in non-identifying form where feasible). These retained records are no longer tied to your active login.

We process deletion requests as soon as practicable and within the time required by applicable law (we aim for about 30 days). Billing records held by Stripe remain subject to Stripe's retention practices.

Third-Party Services We Use

We use the following third-party services to operate PlayThis.Live:

When you search or request a song, we may send the query (e.g. song title or artist) to music metadata services to return results. We do not share your account or personal contact details with them for advertising.

Internal operations alerts (for example Discord webhooks used by our team) may include a signup email for abuse prevention and ops—not for advertising, and we do not sell that data.

Analytics

We use Vercel Analytics to understand how our site is used. This service collects page-view and navigation metrics that do not include your name or email. This information helps us improve our application.

You can opt out of analytics through . Your preference is saved on this device until you change it.

Data Security

We protect your data with concrete measures:

  • Account safety – You can sign in with email and password (hashed with bcrypt) or, optionally, with Google. We support email verification for new accounts and optional two-factor authentication (2FA) via DJ Admin → Settings. If you link Google, you can sign in with either method.
  • Event and profile passwords – Shared gate passwords for private events or private DJ profiles are stored in recoverable form so you can re-share them and receive reminders. They are not protected the same way as login passwords. Choose unique gate passwords and do not reuse your account password.
  • Sessions and API – We use secure, httpOnly cookies and industry-standard session handling; we apply rate limiting and access controls on DJ data.
  • Payments – Billing is handled by Stripe. We do not store or see your card details; only Stripe customer/subscription identifiers are stored so we can manage your plan.
  • Infrastructure – We use HTTPS and set security headers (e.g. X-Frame-Options, X-Content-Type-Options) to protect against common web risks.

Song request information is accessible only to the event DJ and our administrators as needed to operate the service.

Your Rights

Depending on where you live, privacy laws (for example in Virginia, California, or the EU/UK) may give you additional rights. We describe below how to exercise common requests with us.

You have the right to:

  • Know / access – Ask what personal data we hold about you by emailing us with the subject line "Privacy request."
  • Correction – Update most account and profile details yourself in DJ Admin → Profile and Settings (including email change flows). Contact us if you cannot fix something in the app.
  • Deletion – There is no in-app account delete today. Email us with "Privacy request" or "Account deletion" to close your DJ account. We remove account and profile personal data and clear event location and description; we may retain event name, date/time, and associated songs / song requests as described under Data Retention. We process requests as soon as practicable and within the time required by applicable law (we aim for about 30 days). Attendees who did not create an account can contact us about request data; we will handle requests in line with applicable law.
  • Copy of your data / portability – Independent of your plan, you may email a Privacy request for a copy of personal data we hold about you, subject to applicable law and identity verification. Separately, Pro (or higher) includes a self-serve CSV export of events and song requests from DJ Admin → Settings → Data as a product convenience.
  • Marketing opt-out – Manage marketing and policy-update email preferences in DJ Admin → Settings → Email preferences, or use unsubscribe links.
  • Analytics opt-out – Use . Your choice persists on this device until you change it.

Children

PlayThis.Live is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, contact us at PlayThisLive@Gmail.com and we will take steps to delete it.

Contact Us

If you have questions about this privacy policy or our data practices, please contact us at:

Email: PlayThisLive@Gmail.com

For privacy-related requests (access, correction, deletion, or a copy of your data), email us with the subject line "Privacy request" and a short description. We will respond as soon as practicable and within the time required by applicable law (we aim to respond within 30 days). We may need to verify your identity for account-related requests.

Changes to This Policy

We may update our privacy policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the "Last updated" date.