Skip to content
Skip to content

GROOVECADE / THE DETAILS

Privacy Policy

What GrooveCade uses, what other people can see, and the choices you have.

Last updated

Rooms are social spaces. Your account, shared content, and current presence make them work. Music players and connected services also receive information. Leaving a room ends your live presence; it does not automatically erase your history.

Who handles your data

GrooveCade is operated by Mr.Chippy in Belgium. The operator is responsible for decisions about personal data used to run this community. Base44 provides the app platform and hosting; it is not the contact for GrooveCade account requests.

This notice covers information processed through GrooveCade, including guest visits. External music players, linked services, and donation pages also have their own privacy notices. Contact information and your rights are below.

Information we use

  • Account and profile: your email, account identifier, authentication information, display name, handle, avatar, country code, and profile preferences. If you sign in with Google, information is provided through that sign-in flow.
  • Music and community activity: rooms you create or visit, tracks and crates you save, queue activity, chat, reactions, friends, follows, direct messages, and in-app progress or rewards.
  • Room presence: the room, a user or guest identifier, session information, and timestamps used to show who is currently there. Profile details may appear in a room's audience list.
  • Optional connections: linking Discord provides your Discord identifier, username, display name, and avatar, together with connection status and related logs. Linking Spotify for playlist imports provides your Spotify account identifier, display name, authorization status, OAuth access and refresh tokens, and playlist metadata needed to read playlists you own or collaborate on.
  • YouTube playlist connections: if you choose to link your YouTube account, GrooveCade requests read-only access to your playlists. It stores OAuth access and refresh tokens, the YouTube channel identifier and name, and the video details imported into your private crates. Disconnecting removes the linked credentials and YouTube tracks specifically imported through this account. Manually added tracks are not affected.
  • Safety, support, and staff applications: reports, relevant content, moderation actions, image-check results, information you send when asking for help, and staff-application answers. Staff applications also record the role requested, linked Discord identity, whether that account is a member of the GrooveCade Discord server, review status, and reviewer notes.
  • Technical information: hosting and connected services receive IP addresses, device details and requests. Country flags use saved profile choices or hosting-provided country information. The app build disables optional page-view tracking and browser requests to external country lookup services.

When you donate, PayPal handles the payment. The recipient may receive transaction details such as your name, contact information, donation amount, date, and transaction reference. GrooveCade's support page does not collect payment-card details.

Why it is used

Information is used to run the features you request, keep accounts and rooms working, display activity, respond to questions, and investigate abuse. Where the GDPR applies, the relevant basis depends on the purpose:

  • Providing the service: account access, saved music, messages, and requested account connections are processed as needed to perform the service agreement or take steps you request.
  • Legitimate interests: proportionate room presence, security, troubleshooting, and moderation support a functioning, safe community. These interests must be balanced against your rights.
  • Consent: where required for optional notifications, non-essential device storage, tracking, or other optional processing. A browser notification permission can be revoked in browser settings. This notice itself does not grant consent.
  • Legal obligations: responding to lawful requests and retaining records where applicable law requires it.

Providing account information is necessary to create an account. You can browse available public rooms as a guest, but guest use still involves presence and technical data. Features may not work if the information needed for them is unavailable.

Live room presence

“In rooms” counts recent presence in public rooms, not the number of historical visits. The homepage combines active room sessions and avoids counting the same signed-in account, or the same guest browser identifier, more than once. Separate guest browsers or devices can still appear as separate visitors.

A room session sends regular updates while connected. It stops counting after a recorded departure, or when no update has arrived for about 90 seconds. Connection delays can briefly affect the numbers. “Live now” counts public rooms with an active music playback session.

Guests receive a random identifier saved in their browser. Hashed identifiers are used in presence records. This is pseudonymous information, not a guarantee of anonymity. Clearing browser storage resets the local guest identifier.

Leaving the live count does not delete a visit record. Presence timestamps and room history can remain stored after a session ends. Public room presence information, including profile details and visit timestamps, can be accessible to other users.

Who can receive it

Public profiles, room content, and activity are visible to other people using those features. Direct messages are intended for their participants, but should not be treated as an end-to-end encrypted or confidential storage service. Authorised administrators and service providers may access information as needed for operation, support, or safety.

ServiceHow it is involved
Base44Hosting, database, account infrastructure, files, platform measurement, and integrations used by GrooveCade.
Google / YouTubeOptional Google sign-in, embedded video players, YouTube API Services for video details and search, and optional read-only YouTube playlist connections. Requests can disclose connection and device information.
SoundCloudEmbedded music playback. The player connects your browser to SoundCloud.
DiscordThe community server and optional account linking. Discord handles activity on its own service.
SpotifyOptional account linking for Playlist Bridge. GrooveCade uses Spotify authorization to read playlists that the connected account owns or collaborates on; playback still uses YouTube or SoundCloud.
PayPalOptional donations and associated payment records, under PayPal's own privacy practices.

Custom background uploads and their image safety scans are currently disabled. Any image-check result referenced in older records came from a background uploaded before this change; those records can still be reviewed by staff.

Information may also be disclosed where needed to comply with law or respond to a valid legal request. External providers may process information outside your country, including outside the European Economic Area. Their notices explain their processing locations and transfer arrangements. Contact the operator for information about safeguards applicable to a particular GrooveCade transfer.

YouTube API Services

GrooveCade uses YouTube API Services. Google's Privacy Policy applies to that data.

We store a few details about YouTube videos you add or search for: the video ID, title, channel name, thumbnail link, length, and whether it can be embedded or is made for kids. Shared search results are kept for up to 7 days.

Listening history keeps YouTube titles. After 30 days, they are marked as potentially outdated and refreshed when the track is played or queued again under YouTube API Services data rules. Videos that YouTube reports as removed, private or not embeddable lose their stored details.

Connecting your YouTube account is optional and grants read-only playlist access. GrooveCade uses OAuth tokens to fetch playlists you choose; it does not modify your YouTube playlists. You can disconnect in Crates or revoke access in Google's security settings page. Disconnecting removes the linked credentials and tracks imported through that account. GrooveCade also checks connected authorizations periodically; when Google confirms that access has expired or been revoked, those credentials and linked imports are deleted. Checks are retried if Google is temporarily unavailable. Independently saved tracks remain available.

How we protect Google and other sensitive data

Encrypted connections: GrooveCade uses HTTPS to protect data in transit between your browser, the application and Google's OAuth and YouTube API services. Google authorization codes are exchanged by the backend over HTTPS; Google access and refresh tokens are not returned to your browser.

Restricted storage and access: YouTube OAuth access and refresh tokens are stored in server-side connection records with service-only database permissions. OAuth client credentials are kept in backend secrets, not embedded in the website's frontend. Requests to connect, list playlists or import tracks require a signed-in GrooveCade account and use that account's own connection. Linked-account imports are permitted only into private Crates owned by the user. Authorised operational access remains subject to the hosting provider's and application's access controls.

Limited authorization: GrooveCade requests only the read-only YouTube scope needed for playlist imports. Authorization uses a short-lived, single-use state and PKCE to help prevent request forgery and intercepted-code reuse. The permission does not let GrooveCade edit or delete your YouTube playlists.

Removal and review: Disconnecting YouTube removes stored linked credentials and tracks imported through that connection, while preserving tracks saved independently. Scheduled server-side checks also attempt to detect expired or revoked Google authorization and remove linked data. Temporary Google or hosting failures can delay these checks, which are retried.

Security limitations: GrooveCade relies on Base44 for application hosting and stored-data infrastructure. No online service can guarantee absolute security. Public room content and messages should not be treated as end-to-end encrypted private storage. Do not share passwords or other confidential information in rooms or chats.

Browser storage & players

The app uses browser storage and service cookies for login, preferences such as language, and the guest presence identifier. Language and guest identifiers persist until cleared or replaced; they do not currently have a fixed automatic expiry. Clearing site data can sign you out, reset preferences, and create a new guest identity.

Music playback can connect your browser to YouTube or SoundCloud and their media delivery services. Those providers may receive connection and device information and may use their own cookies or similar technologies. The main YouTube room player uses its privacy-enhanced domain, while some previews use standard embeds. Privacy-enhanced playback does not mean that no information reaches Google.

The current app does not offer a dedicated cookie or analytics preference panel. Browser controls may restrict cookies and site storage, but they do not necessarily stop every network request or usage event. Non-essential tracking requires prior consent where applicable; merely visiting the site or reading this policy is not that consent.

How long data stays

Retention depends on what a record is used for: keeping an account and its saved content available, showing room history, resolving support requests, investigating abuse, or meeting legal requirements. Relevant factors include whether your account remains active, whether the content is still shared, whether a dispute is open, and any required record-keeping period.

Apart from stored YouTube data (see YouTube API Services above), there is no general automatic 30-day deletion rule in the current app. The 90-second presence window only determines whether someone is counted as present. It is not a database deletion schedule. Disconnecting YouTube removes its connection tokens and tracks imported through that linked account. Retention rules for other optional connections may differ.

You can delete your account yourself from your profile (Profile → Delete my account). This removes your profile, crates, friends, follows, connections and owned stages; your room chat, reactions and leaderboard entries stay visible as “Deleted user”, and your side of direct messages shows as [deleted]. To ask for deletion of particular records, contact the operator. A request may need identity verification. Some information may need to remain where a lawful exception applies, and copies in backups or records controlled independently by other providers may be handled separately. The operator should explain any relevant limits when responding.

Your choices & rights

Depending on where you live and the legal basis for processing, you may be able to request access to your data, correction, deletion, a portable copy, or restriction of processing. You may object to processing based on legitimate interests and withdraw consent for future processing where consent is the basis.

Use the contact route below for account or data requests. Under the GDPR, requests normally require a response within one month. The law permits an extension for complex or numerous requests, with notice and reasons within that first month. Identity checks must be proportionate to the request.

You can also raise a concern with your local supervisory authority. In Belgium, see the Data Protection Authority's complaint process. Contacting GrooveCade first is welcome but does not remove your right to complain. Read more about these rights in the GDPR, Articles 12–22.

Younger users

GrooveCade is not intended for children under 13. Higher minimum ages or parental-permission requirements may apply to you or to the services you connect. Do not post your school, home address, or other private details in rooms or public profiles.

We collect birth month and year for account age checks, not the day. Eligible details are stored privately, separately from public profiles, and can be corrected in Control Panel.

Signup uses temporary session storage for the age-check handoff. Handoffs are valid for 30 minutes; details are cleared after processing or logout. The age check uses the last day of the birth month.

If you believe a child below the applicable minimum age has provided personal information, contact the operator so the account and information can be reviewed and handled as required by law.

Policy updates

The revision date appears at the top of this page. Material changes to how personal information is used should be explained through an appropriate service or community notice. Where a new purpose requires consent, that consent must be requested separately. Continued use does not replace it.

The Terms of Service cover conduct and use of the app. This privacy notice explains information handling.

Contact about privacy

Contact Mr.Chippy or the GrooveCade staff through our Discord community and ask for a private conversation. Include your GrooveCade handle and what you need help with. Keep personal details out of public channels; never send your password.

Privacy & copyright requests · Privacy choices

Back to top ↑