SmartPlaylists

Privacy

SmartPlaylists is a small, invite-only app that builds Spotify playlists from your listening history. This page says what it stores, who else sees it, and how to get it removed.

Effective

Who can use it

You sign in with your email address and a password, or with your Google account, and only email addresses on the owner's allowlist get in. A password account needs its email address confirmed through a link the app emails you before it can sign in, and an account still unconfirmed after 14 days is deleted. Anyone not on the allowlist is refused or signed out straight away, and no account is created for them. There are no public sign-ups. Using the app also means agreeing to the Terms, which you accept when you create an account or the first time you sign in.

What is stored

Everything below lives in one PostgreSQL database on the app's server, except the server logs and the cache, which stay on that same server.

  • Your account. Your email address; a salted hash of your password if you have one, never the password itself; whether the address is confirmed; when the account was created and when you last signed in; which version of the Terms you accepted and when; and failed sign-in attempts, which lock the account for 15 minutes after 5 in a row. If you sign in with Google, the link between your account and your Google account is stored too; the app reads only your email address from Google, and your name and profile picture are not read or stored.
  • Your handle. The name other members see on playlists you share or make public. It is made from the part of your email address before the @ when your account is created, and you can change it on your Profile page.
  • Spotify and Last.fm connections. For Spotify: the access token, refresh token, granted scopes and expiry. For Last.fm: the session key and your Last.fm username. These are encrypted with ASP.NET Core Data Protection before they are written to the database. The name of each connected account (your Spotify display name, or your Spotify user ID if you have no display name, and your Last.fm username) is also stored unencrypted, so the app can show which account is connected.
  • Your music library. Songs, artists, albums and genres; play counts, last-played and date-added times; tracks from your Spotify Liked Songs and source playlists; your Last.fm scrobbles (track, artist, album and time); plays from a Spotify listening history you upload (track, artist, album, when it started and how long it played); how closely each Spotify and Last.fm track matches a library song, and Claude's suggested match for uncertain ones with its reason; your smart playlist rules; your library settings; and identifiers that files you import supply (ISRC, MusicBrainz recording id and Spotify track id). Each user has their own library and their own Spotify and Last.fm connections; other users cannot see or change yours, except the playlists you share. Artist names, genre tags and the details of a Spotify or Last.fm track (its name, artists and album) are stored once and shared by every library that has them; those shared rows hold nothing about who has them.
  • Spotify recently played. If your Spotify connection allows it, the app reads the last 50 tracks you played on Spotify every 30 minutes and before each Last.fm sync, and stores each one's Spotify track ID, name, artists, length and the time you played it. It uses them only to tell which Spotify track a new Last.fm scrobble was, and deletes each one 48 hours after you played it, or straight away when you disconnect Spotify.
  • Playlist sharing. Each smart playlist is private unless you share it with members you pick or make it public to every signed-in member; it is never shown to anyone who is not signed in. Shared and public playlists are reached through a random link id, never the playlist's own number. Members who can see one see its name, description and rules, when it last changed, your handle as its owner, never your email address, and the name, artists and album of each song in it, taken from your library as of your last refresh. They do not see your play counts, dates or genres, or any other song or playlist of yours. They can copy it into their own library, where it runs against their songs and is private to them. If it has synced to Spotify they also get a link to it there, which opens only if the playlist is public on Spotify. Before a playlist is first shared or made public, and before a shared playlist is made public, you are shown exactly this and asked to confirm; the app records who confirmed, when, for which audience and which wording. Making a playlist private again needs no confirmation.
  • Member list. When you share a playlist with members you pick, the list to pick from shows only the handles of other members whose email address is confirmed. No member sees another member's email address anywhere in the app.
  • What the owner sees. The owner runs the app and is its only admin. On the admin pages the owner sees every account's email address, handle, when it was created and last signed in, whether its address is confirmed, whether Spotify and Last.fm are connected (not the account names or tokens), how many songs its library has, and whether AI is on for it with the consent version it agreed to, and can resend a confirmation email, sign an account out everywhere, block its sign-in, or delete it with everything listed here. The allowlist keeps each invited address with the owner's note, who added it and when, and an optional expiry. Every admin action is recorded with the time, the admin's account and the affected address or handle, and these records are kept until the owner deletes them; when an account is deleted, its record names only its handle and internal ID.
  • Your AI setting. Whether AI is on for your account, which version of the AI consent wording you agreed to, when you turned it on and when you last turned it off. AI is off until you turn it on.
  • Assistant chats. Each conversation, every message you send and every reply, the processing runs behind them and their event history, including the Spotify matches and smart playlists the assistant proposed. A proposal shows as a card in the chat and changes nothing until you click it: a playlist created from a card is private to you, like one you make yourself, and syncs to Spotify like any other smart playlist. These rows are tagged with your account's internal ID, and nobody else, the owner included, can read them in the app. You can delete one conversation, or all of them, from the Chat page.
  • Bug reports. When you report a bug, from the Report a bug form or by asking the assistant, the app stores what you write, the page you were on (its path only, never the rest of the address), the app build, your browser's name and version, a trace id that links the report to the server's diagnostics, the assistant conversation it came from, and your account's internal user id. The owner can read every report in the app and is emailed each one with your user id, not your email address. Reports are kept until the owner deletes them; you can list yours under Report a bug, My reports.
  • Activity log. Audit events such as "scrobble detected" or "track not found on Spotify". They hold song and artist names and your account's internal ID, so you see only your own; a daily job deletes any older than 3 months.
  • Imports. When you import a CSV file on the Import and export page, the file itself is kept only until the import has run. When you import a Spotify playlist, the app reads its tracks once with your Spotify connection (each track's title, artists, album, Spotify track ID, ISRC and the date it was added to the playlist) and keeps them the same way, only until the import has run; the import record keeps the playlist's name and Spotify ID for the link back to Spotify; a file you upload but never confirm is deleted after 24 hours. The songs it adds or updates become part of your library like any other. A record of each import stays: the file name, when it ran, how many songs it added, updated or skipped, any error, and which songs it added or matched, so you can undo it. Undo deletes the songs that import added unless something else now uses them (another import, another playlist, or a Last.fm play), and the page says which stay and why; Remove from list deletes the record and leaves the songs. A Spotify track id from your file is kept on the song until the next Spotify sync looks the track up and links the song to it; an ISRC or MusicBrainz recording id from your file stays with the song. The songs and these ids stay if you disconnect Spotify or Last.fm, because they came from your own file and are your library, not the connection's; a Spotify link made from an id is removed with your other Spotify links. Disconnecting Spotify also deletes any Spotify playlist import not yet applied, and removes the playlist ID and any stored tracks from finished ones. When you import your Spotify listening history (the streaming history files from Spotify's Download your data), the app keeps the files you upload only until the import has run or for 24 hours if you never confirm it, reads only the music history files in them (not your profile, searches, payments, podcasts or video history), and stores each play of at least 30 seconds: track, artist, album, when it started and how long it played, linked to a song in your library; a Spotify track ID in the files is kept on the song as above. A play already stored from Last.fm or an earlier import is skipped, and a Last.fm scrobble of the same listen that arrives later replaces it. These plays are your own data: they stay if you disconnect Spotify or Last.fm, and Undo deletes them.
  • Exports. Export library (CSV) on the Import and export page, or Export CSV on the Library page, downloads every song in your library to your device: titles, artists, album, genres, play counts, dates, the exclude flag and any ISRC, MusicBrainz or Spotify ids. The app keeps no copy of the file.
  • Background jobs. A record of each Last.fm refresh, playlist refresh or import job: its status, progress, any error, and the internal ID of whoever started it. These are not deleted automatically.
  • Server logs. Application log files on the server, rotated daily, with the last 7 files kept. They identify users by internal ID and can include song, playlist and Last.fm account names; an email address appears in them only encrypted.
  • Cache. Spotify search results used for matching are cached for up to 7 days after their last use.
  • Recording codes. A Spotify track's ISRC, the public industry code for the recording, is stored with the shared track details above. A song exactly matched to a Spotify track also keeps that ISRC, so it can be matched again without guessing; it is public catalog data, holds nothing about you, and stays with the song if you disconnect Spotify.

Who else processes it

AI is optional and off by default, so Anthropic receives your data only if you turn AI on. Turning it on means agreeing, on a screen that says so, that your song and play details and your questions are sent to Anthropic, and that the assistant and its suggestions can be wrong and change nothing until you confirm. The app records that agreement (see Your AI setting above) and asks again if that wording changes. While AI is off nothing is sent to Anthropic for you: no assistant, no match checks after syncs and no Check with AI on the Review page. You can turn it off any time on your Profile.

  • Anthropic (Claude) answers the assistant and checks uncertain song matches. Each time you ask the assistant something, the app sends Claude its fixed instructions (which topics it may help with, and today's date), the last 20 messages of that conversation with the lookups behind earlier replies, your new message, and the results of any lookups Claude asks for: your top songs, artists and genres with play counts, all-time or for a date range; your scrobbles with play times (including plays from a Spotify listening history you imported, whose titles, artists and albums come from your Spotify export, as do the names of songs added from Spotify); your plays of artists you name with their top tracks, and of songs you name with when you first and last played them; your play counts by year, month, week, day, hour or weekday; your busiest days, listening streaks and songs you played many times in one day; songs in the order you first played them; artists you started playing, and songs and artists you stopped playing; your genre mix by year or month; your most played songs that are on none of your playlists, and library songs you have never played; a summary of one year's listening; your newest songs with the date added; your genre tags and the songs that carry them; your total song count; a song's stored Spotify and Last.fm matches with their scores; and Spotify catalogue search results. If Claude proposes a smart playlist, it gets back the rules in plain words, how many songs match and the title, artists and play count of up to 5 of them. If you ask it to file or add to a bug report, Claude gets back only the report's reference. After each scheduled sync, the app also sends Claude the title, artists, album, length and release year of songs whose match is uncertain, with up to 10 candidate tracks each; when you click Check with AI on a Review row, it sends the same details for that one row straight away. Your email address, name, handle and account ID are not sent.
  • Spotify, through its Web API and with your authorisation: the app reads your Liked Songs, the playlists you choose as sources, your recently played tracks (if you allowed that when connecting), the list of your playlists and the tracks of a playlist you choose to import once, searches Spotify's catalogue to match tracks (including searches the assistant runs), and creates and updates your smart playlists. It asks Spotify to create them as public playlists, so anyone on Spotify can find them on your Spotify profile unless you make them private in Spotify. Only if you turn it on in Library settings does it then remove the imported tracks from Liked Songs and those source playlists; it is off by default. It reads your Spotify profile to own those playlists, and stores only its display name (or user ID) to label the connection.
  • Last.fm, through its API: the app reads your scrobbles, track details and genre tags for your Last.fm username.
  • Google, if you sign in with it, handles that sign-in and tells the app your email address.
  • Amazon Simple Email Service sends the app's emails: the link to confirm your address and the link to reset your password go to your email address, and each bug report goes to the owner.
  • Amazon Web Services hosts the app and its database on an EC2 server. A daily backup of the database is copied to Amazon S3, and backups older than 30 days are deleted.

Telemetry

When telemetry is switched on, the app exports traces, metrics and logs through OpenTelemetry to a collector configured by the owner, to diagnose errors and slow requests. Database traces include the SQL text with placeholders but never the parameter values, so tokens and email addresses in queries are not exported. Exported logs and traces identify users by internal ID; an email address appears in them only encrypted. There are no third-party analytics, tracking pixels or advertising scripts; every script and stylesheet is served by the app itself.

Cookies and browser storage

Every cookie is strictly necessary, and none is used for tracking.

Cookies
CookiePurpose
.AspNetCore.Identity.ApplicationKeeps you signed in. With "Keep me signed in", or after Google sign-in, it lasts 14 days from your last visit; otherwise it ends when you close the browser.
Identity.External, .AspNetCore.Correlation.*Short-lived, during the Google sign-in round trip.
.AspNetCore.Antiforgery.*Protects forms against cross-site request forgery.
.AspNetCore.Mvc.CookieTempDataProviderCarries a one-time message to the next page, such as "Spotify connected".
spotify_oauth_stateChecks the Spotify connection request. Expires after 10 minutes.

The app also keeps a few interface preferences in your browser's local storage. They never leave your device.

Local storage keys
Local storage keyPurpose
ssp.themeLight or dark theme.
ssp.sideWhether the navigation sidebar is open.
ssp.dockWhether the assistant panel is open.
ssp.dock.conversationWhich conversation the assistant panel shows.
ssp.setup.dismissedThat you hid the setup checklist.

No ads, no selling

Your data is used only to run the app for you. It is never sold, rented or used for advertising, and nobody except the processors above, and the members who can see a playlist you share, receives it.

Disconnecting Spotify or Last.fm

When you are signed in, the sidebar's Sources block shows which Spotify and Last.fm account is connected, with a Disconnect link for each. Your library belongs to you, not to either service, so disconnecting keeps it: songs with their names, artists, albums and play counts, and smart playlists with their rules. Disconnecting asks you to confirm, then deletes straight away, for your account only, the stored token and what the app took from that service for you:

  • Spotify: the stored tokens and account name, your stored recently played tracks, each song's link to its Spotify track and its match scores, your smart playlists' links to their Spotify playlists, your Spotify match suggestions and your Spotify activity entries. Playlists already in your Spotify account stay there, but the app stops updating them. Connecting again (you can pick a different Spotify account) links each smart playlist to the playlist with the same name in that account, or creates one when there is none, and matches songs to Spotify again as playlists sync.
  • Last.fm: the stored session key and username, your stored play-by-play history, each song's link to its Last.fm track and its match scores, your Last.fm match suggestions and your Last.fm activity entries. Connecting again imports the play history from whichever Last.fm account you connect; connecting a different Last.fm account also deletes the stored play history first. Plays you imported from a Spotify listening history stay.

Track details Spotify and Last.fm publish for everyone (a track's name, artists and album) are kept once for all users and hold nothing about you. A daily check deletes the same data again for anyone with no connection to that service, which catches anything a sync running at the moment you disconnected wrote afterwards.

Neither service lets the app revoke its own access, so the app's permission also stays listed at the service until you remove it there:

Last.fm connects whichever account your browser is signed in to at last.fm, so sign out there first to connect a different one.

Getting your data deleted

To see or delete what the app holds about you, including your account, connections, library, import records, playlists, chats, bug reports and job records, email the owner at support@goom.life. Deleted data also drops out of the database backups within 30 days.

Changes

If this page changes, the effective date at the top changes with it.