Privacy
Last updated 21 August 2026.
SpindlShare turns the playlists you already have into one shareable page. It needs very little to do that, and this page says exactly what.
What SpindlShare stores about you
When you sign in, SpindlShare stores the name, email address and profile picture your sign-in provider gives it, plus the username you choose and anything you type into your profile — a display name and a short bio. That is the whole account.
Google user data
Connecting YouTube asks for one scope, https://www.googleapis.com/auth/youtube.readonly. It is read-only: SpindlShare cannot create, change or delete anything in your YouTube account, and never asks for permission to.
From your playlists, SpindlShare reads and stores only:
- the playlist's title and description
- its cover image URL
- how many items it contains
- its public link and its YouTube id
It does not read the tracks inside a playlist, your watch or search history, your subscriptions, your comments, or anything else in your Google Account. Signing in with Google is separate and narrower again — it asks only for openid, email and profile, which is your name, email address and picture.
SpindlShare's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. That data is used only to show your playlists on your own SpindlShare page. It is never sold, never used for advertising, never used to train any model, and never shared with anyone else — except where you have published it yourself, which is the point of the page.
Spotify
Connecting Spotify works the same way and reads the same handful of fields about your playlists. Signing in with Spotify asks only for your email address.
Access tokens
Connecting a service gives SpindlShare a token so it can re-read your playlists later. Those tokens are encrypted before they are written to the database, with AES-256-GCM, and are used for nothing but fetching your playlists.
Visits
SpindlShare counts how many visits it gets each day, as a single number per day. It is not tied to accounts, does not identify anyone, and cannot be traced back to a visitor or a page.
What you can remove, and how
- Disconnect a service from the Connections page. This deletes the stored token and every playlist that was imported through it.
- Hide a playlist from your page at any time without disconnecting anything.
- Revoke SpindlShare's access from the provider's side at Google Account permissions or Spotify apps. SpindlShare stops being able to read anything the moment you do.
- Delete your account entirely by emailing saurabhc0301@gmail.com. Self-serve deletion is not built yet, so this is currently done by hand — and honestly, that is the reason it is written here rather than dressed up as a feature.
Where it is kept
SpindlShare runs on Vercel and stores its data in a Postgres database hosted by Neon. Sign-in is handled by Google, Spotify or an emailed link, depending on which you use. Nobody else receives your data.
Changes
If this policy changes in a way that affects what SpindlShare does with your data, the date at the top changes with it.
Contact
Questions, or a deletion request: saurabhc0301@gmail.com.