GravityMixx Hub

DJ Johnny DiJoe · GravityMixx Entertainment

Privacy Policy

Updated October 21, 2026

This policy explains how GravityMixx Entertainment, operated by DJ Johnny DiJoe, handles information through GravityMixx Hub and its connected song request, music, overlay and Control Center tools.

Information you provide

Song requests can include your name, song, artist, message and, for country requests, dance preferences and notes. Please do not include sensitive personal information in request messages. Event inquiries include contact information, event date, optional times, location and planning details. They are saved in a private owner queue, with acknowledgment and owner notification emails sent through our connected email service. Submitting an inquiry does not subscribe you to marketing updates.

Sign-in and community access

If you sign in with Twitch, we receive your Twitch account ID, username, display name and subscription information needed to determine request access. We store your community access level, any moderator permissions and authorization tokens needed to maintain the connection. We do not receive your Twitch password. Country request forms do not require Twitch sign-in. The Hub can recognize the same Twitch connection used by song requests. Its secure browser session lasts up to 30 days and is renewed with active Hub use; signing out revokes that browser session. Twitch’s embedded video player maintains a separate Twitch login and controls subscriber viewing benefits. The Hub does not pass your authorization token into the video player or guarantee that its login is recognized.

Connected creator accounts

The owner can authorize supported platform connections to show public profile information, follower or subscriber totals, broadcast status and live viewer counts. These connections may include Twitch, Kick, YouTube, Facebook, Instagram and TikTok. Data availability depends on the platform and granted permissions. Private authorization credentials are stored encrypted on the server and are not included in public audience responses.

The TikTok connection is for the creator account authorized by the owner. It requests basic profile information, username and account statistics to identify the correct account and display its follower count. Visitors do not need to connect TikTok to view the Hub. This connection does not post content, send messages or take payments through TikTok.

Listening, cookies and technical information

The music and embedded Twitch players send a random anonymous playback-session identifier, playback source, timestamps and duration while playing. Active video playback sessions and music listeners are shown separately on the Hub. Counts estimate sessions rather than unique people; multiple tabs or devices may count separately. These listening records are used for active listener totals and listening reports. The listener table does not link those records to an account or IP address. Records older than 90 days are removed when new listener activity is processed.

Cookies maintain sign-in sessions, protect authorization flows and help enforce request limits. Request endpoints may use a hashed browser identifier or an IP-derived hash for limits and abuse prevention. Hosting and connected services also process technical information such as IP addresses and browser details to deliver their services.

Payments and request alerts

PayPal or StreamElements handles payments, depending on the option used. The Hub can store payment references, transaction status, amounts and related request details to verify tips and produce reports or broadcast alerts. The Hub does not collect card numbers or PayPal passwords. A submitted name, song request or confirmed tip may appear in a broadcast alert.

How information is used and shared

Information is used to operate the Hub, manage song queues and community access, verify payments, display platform counts, report listening activity, prevent abuse and respond to support requests. The owner and moderators with the relevant permissions can view request information. Payment settings and private connections are restricted to the owner.

Service providers process information needed for hosting, storage, sign-in, payment processing and request email delivery. Request notifications may be delivered through FormSubmit and email services. Embedded Twitch players and links to social, booking, merchandise or tipping services are subject to those providers’ policies. Loading an external player may send your IP address and browser information to that provider.

Free email following

If you request email updates, we store your email address, the topics you selected, confirmation and update times, consent version and subscription status. You must confirm your address before becoming a follower. Brevo processes your address and confirmation email for delivery. Signing up does not create a paid subscription or a Twitch account, and we do not notify the owner by email about each signup. Unconfirmed requests expire after 24 hours and are removed after a further seven days when new signup requests are processed. Confirmation and preference link tokens are stored as hashes. Temporary abuse-prevention counters include an IP-derived hash and expire after their rate-limit period.

Only the owner can view email addresses or configure delivery. Use the preferences link from your confirmation email to change topics or unsubscribe. Unsubscribed addresses and consent history may be retained to honor your choice; you can contact us to request deletion. Followers are not automatically subscribed to unrelated topics. Confirmed followers receive announcements matching their chosen topics. Event and livestream announcements can be automatic; account holders can additionally opt into music, reminder and merchandise emails. Messages include an unsubscribe link.

Hub visitor reporting

The Hub stores a random anonymous browser identifier locally and records visible page loads with a New York calendar date and approximate country, state or region, and city supplied by the hosting network. It does not request GPS or precise device location. Reports estimate unique browsers and views by day, week, month and year. Visit records are retained for yearly reporting. This feature does not collect names, account IDs, IP addresses or browsing history. You can clear the identifier through your browser storage settings.

Sharing reports

Sharing tools record popup opens, successful link copies, browser share handoffs, QR download clicks and opens of the tracked QR link, using the anonymous browser identifier and event date and time. Reports estimate browsers rather than people. They do not collect recipients, messages or proof that a share was delivered. The Hub browser exclusion also excludes these actions. Records are retained for yearly reporting and are visible only to the owner.

Free Hub accounts

Email sign-in uses a one-use link that expires after 15 minutes. After verification, we store your email, display name, follower status and optional notification choices. Google sign-in uses your Google account identifier and verified email; it does not give us your Google password. Hub sessions use secure browser cookies and expire after 30 days. Logging in creates a free Hub follower account but does not opt you into announcement emails or grant moderator access. You can change email choices or stop following in your Hub account. Confirmed legacy email-update followers are included in Hub follower reports without creating a login session.

Mobile accounts and phone notifications

In the iPhone app, email sign-in uses a six-digit code that expires in ten minutes, with a limit on attempts. The app stores a random session proof in the device’s secure storage. Sessions last up to thirty days. Connecting an email to Twitch requires both an authenticated Twitch app session and verification of that email. Email sign-in alone does not grant owner or moderator permissions.

If you turn on phone push notifications, we store an encrypted Expo push token, a hashed random device identifier, your selected topics, and delivery status. Expo and Apple or Google process the token and notification content for delivery. Public event, stream, music, reminder and merch alerts contain published Hub information. Push choices are separate from email choices. Turn push off in Accounts & alerts or your phone settings. Invalid device tokens are disabled when reported by the provider. Notification delivery depends on credentials, internet access and phone settings.

Optional browser notifications

When you enable notifications on a device, we store its browser push subscription and origin encrypted on the server. The browser’s push provider processes encrypted notifications for delivery. Hub alerts can include events, schedule changes, event reminders, live streams, music starts and merchandise drops, according to your choices; private owner alerts say that an inquiry arrived without including customer details. Approved moderators can separately enable song request alerts. John controls each moderator’s permissions for public announcements and the Hub calendar. Notification read status and the device’s selected notification setting are stored locally. You can disable notifications using the button on the same device or your browser settings. Expired subscriptions are removed when the push provider reports them invalid. Delivery depends on browser and operating system support and settings.

Delete your app and Hub account

In the app, open My Account and choose Delete my account. After confirmation, the service removes your Hub profile, linked email preferences, Hub sessions, associated Twitch request-account credentials and identified song requests. Registered phone notification tokens are removed for linked devices and the phone making the request. Local event reminders are cancelled on that phone. Unlinked browser notification subscriptions and reminders on other phones are device-based; turn them off on those devices or in browser settings. Payment transaction records remain for accounting, with the deleted request-account identifier removed. Separate booking inquiries and business integrations are not part of the follower account. This does not delete your Google or Twitch account, cancel subscriptions with those services, or remove your business’s published events and integrations. You can create a new account later; deleted data is not restored.

Retention and your choices

Request history, community settings and transaction records remain available for queue management, reporting, support and accounting until removed; archiving a queue does not delete its records. Connection credentials are retained while the connection is configured. You may sign out, stop audio playback, revoke app access in the relevant platform or contact us to request access, correction or deletion of information associated with you. Revoking access does not automatically delete historical request or payment records.

For privacy requests, email gravitymixx@gmail.com with the relevant username and request details. Do not send passwords, access tokens or card information. We may need to verify your identity and may retain records needed for accounting, security or legal obligations.

Updates

Changes to these practices will be reflected on this page with an updated date.