Backing up and exporting your data

Go to Settings → Data and click Export database (.db). You get a single file containing your complete library: every play with its timestamp and source, your pending rows, the MusicBrainz matches for your tracks, and the album-art references for your albums. The file is a standard SQLite database, a deliberately boring, universally-readable format. Any SQLite tool on any platform can open it, which means your export is useful even entirely outside Stick: query it, chart it, archive it, feed it to your own scripts.

The export is scoped to your data, it's your library, not a dump of the service. Download one whenever you like; a quarterly backup into the same folder as your streaming-service exports is a nice habit.

Restore: replace or merge

On the Import page, alongside the file importers, you can upload a previously-exported .db backup. Stick validates it and shows what's inside, how many plays, covering what date range, before anything happens. Then you choose:

• Integrate into current DB, merge the backup's plays into what's already there. Existing plays are kept; the backup fills the gaps.
• Restore from backup, replace your current library with the backup wholesale. This is the destructive one, clearly labelled, and it asks you to confirm before touching anything.

Undoing an import

Backups are for disasters; most day-to-day "undo" needs are smaller, a CSV imported with the wrong column mapping, a file that turned out to be the wrong export. For that, Settings → Import History lists every file import as its own unit with its play count and date range. Deleting one removes exactly the listens that import added and nothing else, and it deliberately keeps the MusicBrainz matching work, so re-importing the corrected file is fast and clean. The full flow is covered in the import guide.

Smaller deletions

You can also delete at any granularity: a single play, all plays of a track, an album, an artist, or everything from one source. Deletions of individual listens are remembered so a later re-import of the same file doesn't silently resurrect them, they show up in a "Previously deleted" tab during the pre-import scan instead, where restoring them is a deliberate choice.

Deleting your account

The full exit is in Settings → Data too: delete your account and every play with it, immediately. No retention period, no "deactivation", the data is gone from the database when the confirmation completes, as described in the privacy policy. Export a backup first if there's any chance you'll want the history later; a fresh account can restore it and be exactly where you left off.