The public walkthrough uses fictional tracks, runs locally, contacts no service, and stores nothing.
Privacy & safe use
Nothing hidden.
Nothing retained.
Playlist Tidy is a static, open-source browser application. It has no application server, database, analytics, advertising, or user account system.
Effective 25 October 2026
The plain-language version
Your Spotify identity and owned playlists only after you provide your app's Client ID and authorize access.
Track order inside a playlist you own, only after preview and explicit confirmation.
A one-time login verifier during Spotify's redirect, plus your own public Client ID if you choose to supply one. Both use this tab's session storage.
No analytics, advertising identifiers, cookies, form submissions, or application database records.
Spotify authorization
Connection uses Spotify Authorization Code with PKCE. Playlist Tidy requests permission to read private and collaborative playlists and to reorder public and private playlists. It refuses to sort a playlist not owned by the authenticated account.
The access token exists only in this page's memory. It is not written to local storage, a cookie, a URL, the page, or an application server. Reloading or closing the page removes it. If Spotify returns a refresh token to the public website, the website discards it.
The public website does not provide a shared Spotify application. Real Spotify use requires the public Client ID from your own Development Mode app. The website stores that non-secret identifier in this tab's session storage so it survives the authorization redirect, sends it only to Spotify as part of OAuth, and removes it when you select the forget action or close the tab. It never requests a Client Secret. Your app must register the exact redirect URI shown by the website, and Spotify requires its owner to have Premium.
Playlist data
Playlist names, item identities, addition dates, ownership, and snapshot identifiers travel directly between your browser and Spotify. They are processed in memory to calculate and verify an ordering plan. The public website does not transmit that data to the project owner.
Sorting uses Spotify's reorder operation only. It does not add, remove, replace, create, or delete playlist items. A final read verifies both membership and order before success is reported.
Infrastructure and third parties
GitHub Pages serves the static files and may process ordinary network information under GitHub's own policies. Spotify processes authorization and API requests under Spotify's policies. Playlist Tidy includes no third-party scripts, analytics, session replay, advertising, or social embeds.
The self-hosted scheduled workflow described in the repository is separate from this public browser session. Its credentials remain in the repository owner's encrypted GitHub Actions secrets.
Your control
You can end the browser access-token session by reloading, closing the page, or selecting Disconnect. A supplied Client ID remains available within the same tab after reload so a Spotify redirect can complete; select the forget action or close the tab to remove it. You can also remove Playlist Tidy from the connected-apps area of your Spotify account. Because the public website keeps no account or database, it has no retained profile or playlist record to export, correct, or delete.
Safe use and limitations
Preview the proposed move count before sorting. For an early build, begin with a playlist you can restore. Keep the tab open until verification finishes, and avoid editing the same playlist elsewhere during a sort.
The software is provided under the GPL-3.0-only license without a service warranty. The project is independent and is not affiliated with or endorsed by Spotify.
Questions and security reports
For a privacy question, open a repository discussion or contact AlbiDR through GitHub. Report a vulnerability privately through GitHub's security advisory form. Never include Spotify tokens, authorization codes, playlist identifiers, or private playlist contents in a public report.