Privacy

Effective October 18, 2026. Version: 2026-10-18.1

Public-facing maintainer: MasterFufu🎀 Contact: support@auxroulette.com

What this policy covers

This policy explains how Aux Roulette’s music-discovery website handles information. Our collection and use of information are subject to this policy. The independently hosted Game Room has its own rules and privacy information.

You do not need a visitor account or a connected Spotify account to pick songs, build a set, or assemble a queue.

Visitor analytics

Vercel Web Analytics counts visits and page views on the public Production site. It uses no analytics cookies. Reports include page paths, referring sites, approximate country, and browser/device information. Our integration removes URL query strings and fragments and excludes account, authentication, editor and API page views. For each successful Song Roulette reveal, we also send one Spin completed event with the selected category name and type, or Anything for an unfiltered pick. Failed or cancelled picks and browsing previous picks do not count. We count explicit switches into Create a Queue, Build a Set and Playlists, successful queue-add actions with the number of songs added, and successful nonempty set builds with their song count. Bulk queue additions send one event per action. Restoring saved tools, tour previews, duplicate or full-queue attempts, empty sets and single-song set rerolls do not count as these events. Provider-link clicks record the source tool and provider only; a click does not establish playback. Playlists, Music Explorer and Release Timeline each record the first deliberate discovery action per tool visit, using a fixed action label such as playlist, map, filter or search. Spotify export attempts record confirmed completion with song count, or a fixed failure reason, including partial completion. Export completion counts acknowledged attempts, not unique created playlists. Reliability counters record failed spin/set requests, empty results and collection-loading/action failures using only fixed tool and reason labels. Empty results are reported separately from request failures; cancelled actions and navigation-related request aborts are excluded. Events do not include song identities, provider URLs, playlist names, filter selections, search text, recent-pick history, queue contents, raw errors or Spotify account data. Preview and local builds do not collect these analytics. Vercel provides a 12-month reporting window on our Pro plan. Vercel uses a request-derived hash for visitor counting and discards its visitor-session identifier after 24 hours; this is separate from aggregated reporting retention. Browser blockers may prevent collection. Collection begins only after the integration is deployed; earlier visitor counts cannot be reconstructed.

Information stored in your browser

Browser session storage remembers:

• Up to 20 recent recordings, including their titles, artists, versions, and provider links.
• Your position in that history.
• Your generated set, its filters, and the number of matching recordings.
• Up to 200 queued recordings, their order and selected recording.
• Whether you selected Song Roulette, Create a Queue, Build a Set or Playlists.
• The shuffled pick-button phrase order and current position, to avoid repeats within each cycle.

Session storage normally lasts for the tab’s browsing session. Browser recovery and restoration features may restore it.

Persistent local storage remembers your starred category IDs, whether sound effects are enabled, your selected volume and whether you dismissed the optional welcome. Owner workshop favorite sound directions and submitted artwork rankings are also stored locally in that browser. The application assigns these preferences and rankings no automatic expiry. Older stored Spotify app/web preferences may remain until cleared, but are no longer used.

Remembering your agreement

After you accept the Terms of Use, your browser stores:

• The Terms version accepted.
• The acceptance date and time.
• The agreement-screen version.

The application recognizes this record for up to 12 months. It asks again after that period, if the record is unavailable, or when materially revised Terms require renewed agreement.

This record stays in your browser. The application does not send it to a dedicated server-side acceptance database or collect your name, email address, IP address, or a unique visitor identifier for this purpose.

Ordinary hosting and security processing remains separate, as explained below.

Clearing site data removes the browser’s acceptance record. It does not retroactively undo an agreement already made or delete separately held support correspondence.

Information processed by our server

Pick requests send your selected category and recent recording IDs to select a song and reduce repeats.

Set requests send selected filters, the requested song count, and any recording IDs to exclude.

The application does not write these requests into a personal listening-history profile or save your generated set or queue in its database. Service infrastructure may separately process technical request information.

Queue collection searches and category filtering run in your browser after it requests the public catalog. Collection searches stay in your browser. If you choose Spotify search after connecting, those search words are sent through our server to Spotify. Queue edits are not written to the shared collection. Music Explorer searches and its taste questionnaire run in the browser using the public collection; the app does not save those answers to a server-side visitor profile.

Owner category-playlist synchronization

The site owner can separately authorize automatic maintenance of the public category playlists. This uses permission to manage public playlists and does not connect visitors or grant editor access. An encrypted Spotify refresh token is stored in the site’s private database so approved collection changes can be processed in the background. It is not exposed to visitors or other editors. No Spotify password is stored. The owner can disconnect from the Spotify category-sync page to remove the currently stored token and stop further processing, or revoke the app through Spotify settings. Existing published playlists remain on Spotify.

Optional visitor Spotify connection

Spotify authorization requests permission to create private playlists. The server keeps a short-lived access token inside an encrypted, HttpOnly, same-site cookie scoped to the Spotify connection endpoints, for at most one hour. The authorization state cookie lasts ten minutes. No refresh token or Spotify password is retained. A short-lived encrypted export receipt helps prevent accidental repeated exports. Disconnect clears these cookies; you can revoke the app through Spotify settings. Queue selections remain in your browser session until cleared. Spotify receives the playlist name and exact Spotify track IDs only when you choose to export. SoundCloud-only entries require explicit exclusion before export. Development access may be limited to approved test accounts.

Optional visitor accounts

Guest music tools and guest games remain available without an account. Check Your account for signup availability. Where enabled, email/password accounts use Supabase Auth. Your email is used for verification, sign-in and recovery; it is not a public profile field. Never share passwords or email codes with support.

After verifying your email, choose a unique username and display name. We store those names, your Auth account ID, creation/update times, your public-leaderboard preference and any pending-deletion status. Current account Terms acceptance is stored privately with its version and acceptance time; this is separate from the music tools' browser-only agreement record. Authentication alone never grants editor or host access.

Public leaderboard participation requires both your profile's public-ranking preference and an explicit eligible score-save action in the game. Public entries show your current username/display name, validated best score, exact-year count and rank. Turning off the preference or requesting deletion hides your entry. Your email, Auth/session identifiers and private account consent are not public ranking fields. An account does not yet synchronize browser queues, generated sets or category favorites.

The website and Game Room keep separate host-only HttpOnly sign-in cookies. You may need to sign in on each site. These visitor cookies are separate from editor/host cookies; no account token is placed in a page URL or browser local storage. Sign out on this site clears that site's session; Sign out everywhere revokes the account's sessions. Access tokens can last up to one hour, but protected profile and ranked actions additionally check that the underlying session remains live.

Account/profile records and saved best scores remain until deletion; they have no automatic inactivity expiry. Ranked runs have a 30-minute access deadline, which does not mean physical deletion at 30 minutes. The game retains at most 30 recent runs per account and prunes runs older than 24 hours when that account next starts a run. Deleting the Auth account cascades its profiles, consent, ranked runs and best scores. Ordinary infrastructure/security records and provider recovery copies can have separate retention periods.

Account deletion requires your current password and explicit confirmation. The account is first marked for deletion and hidden from public rankings, then its sessions are revoked and its Auth record is deleted. If completion fails, the profile remains hidden for retry or support. Managed editor/owner/host accounts require a support review. Deleting an account does not clear local browser queues/preferences, delete Spotify playlists or remove separately retained support correspondence. Clear browser data and manage Spotify separately.

Verification and recovery messages use the configured transactional email delivery service, Resend, which processes the recipient address and message/delivery information. We do not add account addresses to marketing lists. The provider's privacy policy applies to its processing.

Editor accounts and cookies

The protected editor uses Supabase authentication. Sign-in details are processed through our server and Supabase. Authentication cookies maintain the editor session.

Account information and editor-access membership are separate from the public collection. Signing in alone does not grant editing permission.

Editor access tokens expire after one hour and can be refreshed. Sessions currently have no configured maximum lifetime or inactivity timeout. Authentication cookies have a renewable lifetime of up to 400 days; this is separate from token validity.

Editor account records remain until manually removed. Revoking editing permission does not itself delete an authentication account.

Hosting and technical information

Vercel hosts Aux Roulette. Hosting and security infrastructure process technical information needed to deliver and protect the service, which can include IP addresses, request URLs, timestamps, browser information, and diagnostics.

Supabase provides the catalog database and account authentication.

The application includes no advertising pixels or session-recording software. Hosting observability and operational logging remain separate from those tools.

Spotify and external services

Our server requests selected recording information from Spotify. Approved editors’ catalog-search terms are also sent to Spotify.

Album artwork loads directly from Spotify’s image infrastructure. Spotify receives those requests and associated connection information, such as IP addresses and browser information. Artwork requests are configured not to send a referring-page header.

Opening a music-service link takes you to that service or its application, where its own terms and privacy policy apply.

You can use the music tools without connecting Spotify. The optional visitor connection requests permission to create private playlists, not to read your existing private library or listening history or control your playback queue. The owner’s public category-playlist connection is separate, as described above.

Fonts and Aux Roulette’s brand images are served with the website.

Retention

Support correspondence uses Google Workspace/Gmail. Incoming support mail is labeled for review. When resolved, the conversation is assigned a resolution date and a cleanup deadline no later than 12 calendar months afterward. A monthly review checks approaching deadlines and any necessary holds. Removal is performed manually; no unattended rule deletes unresolved or unrelated messages. The routine cleanup target removes messages from the active mailbox by that deadline. Deleted messages normally remain recoverable in Gmail Trash for up to 30 additional days; this provider recovery period is separate from active-mailbox retention.

Provider recovery systems, security records, and legally required retention can differ from these operational windows. We do not promise that every provider-held copy disappears at the end of those windows.

The current Supabase Free plan does not include customer-accessible scheduled project backups.

Your choices and requests

You can clear Aux Roulette’s cookies and browser storage through your browser settings. This may remove history, generated sets, your queue, preferences, Terms acceptance, and editor sign-in.

Blocking storage or third-party requests may affect functionality.

Contact support@auxroulette.com with privacy questions or requests to exercise applicable rights. We may need enough information to verify and locate relevant records. Browser-only records can be removed on your device.

Provider information is available in the Vercel Privacy Notice, Supabase Privacy Policy, Google Privacy Policy, and Spotify Privacy Policy.

Spotify is a third-party beneficiary of this policy as required by its Developer Terms.

Changes

We will update this policy and its effective date when our features or information practices change. Acceptance of the Terms does not serve as blanket consent to optional data processing.

Optional Spotify player

Opening Preview loads a player directly from Spotify. Spotify receives connection and device information and may use cookies or similar technologies, subject to browser settings and its policies. Aux Roulette does not receive your Spotify password. You can use the picker without opening the player.

Sound preferences

Interface sounds are generated locally through your browser’s audio capabilities. The enabled setting and volume can be remembered in local storage. These sounds do not upload recordings or require microphone access.

Operational information

Infrastructure log-retention and editor-session settings above were last verified on October 15, 2026. Support routing and the manual resolution/deadline workflow were verified on October 17, 2026. We update this notice when the site’s information practices change. Agreement to the Terms does not serve as blanket consent to optional data processing.