Who we are

Artize (“we”, “us”) provides branded live-DJ submission portals where DJs run a live request queue and fans submit tracks, send gifts, and chat. This policy explains what we collect and how we use it.

Information we collect

DJ accounts: name, email, and profile details you provide.
Fan submissions: the name, email, track title/genre, and any audio file a fan chooses to submit.
Payments: processed by Stripe. We never see or store full card numbers; we store only payment metadata (amounts, status, identifiers).
Connected platforms (YouTube, Twitch): when a DJ connects a channel, we store an encrypted access/refresh token and the public channel identity (channel/user id, display name).
Usage data: queue activity, viewer heartbeats, and audit logs needed to run the show.

Google / YouTube data

Artize uses YouTube API Services. By connecting YouTube you agree to the YouTube Terms of Service, and our use of your Google data is governed by the Google Privacy Policy and the Google API Services User Data Policy, including the Limited Use requirements.

Scope we request (only one, read-only): https://www.googleapis.com/auth/youtube.readonly.

What we access & why: solely to (1) detect when the connecting DJ’s own channel is currently live, using liveBroadcasts.list, and (2) display the DJ’s public channel identity (channel id, title, URL) on their portal. We do not read comments, videos, playlists, analytics, or subscriber data.

How we store it: access and refresh tokens are encrypted at rest (AES-256-GCM) and isolated per DJ portal. We store only the public channel id/title/URL alongside them.

Limited Use commitment. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we:

only use the data to provide and improve the live-detection and channel-identity features above;
do not transfer the data to others except as necessary to provide the feature, to comply with law, or as part of a merger/acquisition with your consent;
do not use or transfer the data for serving advertisements; and
do not allow humans to read the data unless we have your consent, it is necessary for security or to comply with law, or the data is aggregated/anonymized. We do not use it to train generalized AI/ML models.

Revoking access: a DJ can disconnect YouTube at any time from their portal (which deletes the stored tokens), and can also revoke access anytime via Google Account → Third-party access.

Twitch data

When a DJ connects Twitch, we request no additional scopes; we use the channel identity and public live status (via Helix Get Streams and EventSub) solely to show when the DJ is live. Tokens are encrypted at rest and removed on disconnect.

How we use information

Operate the live queue, payments, gifts, and chat.
Detect and display live status on connected platforms.
Send transactional emails (receipts, play/skip updates).
Prevent abuse and keep audit records.

Data security & retention

Third-party tokens and sensitive secrets are encrypted at rest (AES-256-GCM). We keep data only as long as needed to run the service or as required by law, and purge ephemeral data (e.g., viewer pings) automatically.

Your choices

DJs can disconnect any platform or delete their portal. Fans can request removal of a submission by contacting the DJ or us. To exercise any right, email the address below.

Contact

Questions about privacy: beatkitbuilder@gmail.com.