Terms & Privacy | FilterMyDiscogs

Terms of Service

Here's the deal: use this app at your own risk. I'm not a lawyer, but here's what you should know:

This thing is free and comes with zero guarantees. If it breaks, I'll try to fix it, but no promises.
Most of the time the app only reads your Discogs collection. When you add, edit, or clear release notes here, those changes are saved to your Discogs account through the Discogs API. They are not stored in my database. Clearing app data below does not undo note changes you already saved on Discogs.
The app does not add or remove releases from your collection. Note edits apply only to text fields you choose to change on releases you already own.
Keep your Discogs account secure. That's on you, not me.
I use OAuth, so I never see your password. Your Discogs login stays between you and Discogs.
Want to bail? Revoke access anytime in your Discogs settings. No hard feelings.
I might change things up or shut it down. That's just how it goes with free projects.
Right now it's free, but that might change. If I ever add paid features or subscriptions, I'll give you a heads up first.

Privacy Policy

I'm not in the data-selling business. Here's what I actually do with your stuff:

What I Collect

OAuth 1.0a authentication. I never see your Discogs password. That stays between you and Discogs.
OAuth session tokens live in httpOnly cookies on your browser so the server can call Discogs on your behalf. They are not readable by page JavaScript.
Your collection data, including release notes, comes from the Discogs API and is cached in your browser to keep things snappy. After a full load, a copy may be stored in IndexedDB on this device so return visits can skip re-downloading every page; we re-check collection size with Discogs when you sign in and clear the cache if your collection has changed. We may also store your collection size in localStorage (not the releases themselves) to speed up pagination.
When you save notes in the app, that text passes through my server to the Discogs API. I do not store note content in my Postgres database.
Your crates and which releases are in them live in my Postgres database so they stick around between sessions.
When you're logged in, account preferences also live in Postgres: theme (light, dim, sepia, slate, dark, midnight, high contrast, or system), default view (grid or table), whether to remember filter selections, whether to auto-play when adding to an empty queue, your analytics cookie choice (when set), named saved views you create from the Views menu on Releases (search, filters, and sort snapshots), and—when that option is on—your saved filter and sort choices (styles, years, formats, sort order, genre/style, format, and release year match mode, and search text). That lets settings follow you across browsers. I don't store your full collection there.
When you opt in to analytics, I may also store product usage events in Postgres (for example page path, event name, and interaction label). When you're signed in, those events can include your account ID. I use them to understand how the app is used, not to sell data.
I don't sell your data or use it for advertising. Period.

What I Do With It

Your collection data, including notes, is for showing, searching, and filtering your records in the app. That's it.
When you edit release notes, I send your changes to Discogs on your behalf. I don't analyze note text, mine it, or keep a separate copy in my database.
Collection data runs through your browser and hits my API routes, which proxy Discogs. Your crates and account preferences get saved to Postgres so they don't disappear when you close the tab.
Theme, view, filter, playback, and analytics cookie preferences are also kept in your browser for fast loads and continuity on this device. When you're signed in, changes sync to your account.
Want to nuke everything on my side? Hit "Clear All Data" below and I'll wipe your crates and saved preferences from the database and clear local app data on this browser. That does not delete or change your Discogs collection or notes. You'd need to edit or remove those on Discogs itself.

Cookies & Storage

Essential cookies: HttpOnly cookies hold your OAuth session so you stay logged in without exposing tokens to JavaScript. These are required for the app to work and do not need separate consent.
Local storage: Theme, default view, filter and sort selections (when "Remember filter selections" is on), your analytics cookie choice, in-progress playback (current track and upcoming queue), remembered collection size for faster loading, and similar UI state. When you're logged in, the same preferences are also stored on the server (see above). IndexedDB: After your collection finishes loading, a cached copy of those pages may be stored on this device to speed up return visits until your Discogs collection size changes or you clear app data.
Optional analytics: When you opt in, Google Tag Manager may set analytics cookies to measure page views and basic interactions. The app may also store similar interaction events in Postgres (for example page path, event name, and label) to understand product usage, sometimes linked to your account ID when you're signed in. Analytics does not run until you accept. You can change your choice anytime in Settings under Data, or use Essential only on the consent banner.

Third-Party Stuff

The app talks to the Discogs API for your collection and notes. Their rules apply to that relationship.
Google Tag Manager handles third-party analytics cookies when you opt in. Google's privacy policy applies there. First-party product analytics events are stored in my Postgres database under the same consent choice.
Images get proxied for speed, but I don't hoard them. They're cached, not stored.

Data Management

Want to start fresh? Clear everything out. This button wipes:

All your auth tokens and session cookies
Every crate you've created, including which releases are in each crate (deleted from Postgres, gone forever. No takebacks)
Your saved account preferences on our server: theme, default view (grid or table), your analytics cookie choice, named saved views from the Views menu on Releases, filter/sort selections when "Remember filter selections" is enabled in Settings, and playback settings (auto-play on queue add)
Product analytics events linked to your account (when you had analytics enabled), such as page views and interaction labels
Local preferences on this browser: theme, view mode, filters, analytics cookie choice (you will be asked about analytics cookies again), in-progress playback (current track and upcoming queue), remembered collection size (to load large collections faster), cached collection pages in IndexedDB (for faster return visits on this device), and similar UI state
In-memory caches for the current browser session, including your loaded collection
Your Discogs collection and any notes you saved there are not affected. You can still see and edit them on Discogs or after you log in again here

Heads up: This logs you out and you'll need to reconnect with Discogs. Crates and saved preferences are permanently deleted from our database. Logging out without clearing data keeps your crates and preferences—you can sign in again later. Useful on a shared computer or when you want a clean slate on this app. It is not a way to undo note edits on Discogs.

You must be logged in to clear data.

Here's the deal: use this app at your own risk. I'm not a lawyer, but here's what you should know:

This thing is free and comes with zero guarantees. If it breaks, I'll try to fix it, but no promises.

Most of the time the app only reads your Discogs collection. When you add, edit, or clear release notes here, those changes are saved to your Discogs account through the Discogs API. They are not stored in my database. Clearing app data below does not undo note changes you already saved on Discogs.

The app does not add or remove releases from your collection. Note edits apply only to text fields you choose to change on releases you already own.

Keep your Discogs account secure. That's on you, not me.

I use OAuth, so I never see your password. Your Discogs login stays between you and Discogs.

Want to bail? Revoke access anytime in your Discogs settings. No hard feelings.

I might change things up or shut it down. That's just how it goes with free projects.

Right now it's free, but that might change. If I ever add paid features or subscriptions, I'll give you a heads up first.

I'm not in the data-selling business. Here's what I actually do with your stuff:

What I Collect

OAuth 1.0a authentication. I never see your Discogs password. That stays between you and Discogs.

OAuth session tokens live in httpOnly cookies on your browser so the server can call Discogs on your behalf. They are not readable by page JavaScript.

Your collection data, including release notes, comes from the Discogs API and is cached in your browser to keep things snappy. After a full load, a copy may be stored in IndexedDB on this device so return visits can skip re-downloading every page; we re-check collection size with Discogs when you sign in and clear the cache if your collection has changed. We may also store your collection size in localStorage (not the releases themselves) to speed up pagination.

When you save notes in the app, that text passes through my server to the Discogs API. I do not store note content in my Postgres database.

Your crates and which releases are in them live in my Postgres database so they stick around between sessions.

When you're logged in, account preferences also live in Postgres: theme (light, dim, sepia, slate, dark, midnight, high contrast, or system), default view (grid or table), whether to remember filter selections, whether to auto-play when adding to an empty queue, your analytics cookie choice (when set), named saved views you create from the Views menu on Releases (search, filters, and sort snapshots), and—when that option is on—your saved filter and sort choices (styles, years, formats, sort order, genre/style, format, and release year match mode, and search text). That lets settings follow you across browsers. I don't store your full collection there.

When you opt in to analytics, I may also store product usage events in Postgres (for example page path, event name, and interaction label). When you're signed in, those events can include your account ID. I use them to understand how the app is used, not to sell data.

I don't sell your data or use it for advertising. Period.

What I Do With It

Your collection data, including notes, is for showing, searching, and filtering your records in the app. That's it.

When you edit release notes, I send your changes to Discogs on your behalf. I don't analyze note text, mine it, or keep a separate copy in my database.

Collection data runs through your browser and hits my API routes, which proxy Discogs. Your crates and account preferences get saved to Postgres so they don't disappear when you close the tab.

Theme, view, filter, playback, and analytics cookie preferences are also kept in your browser for fast loads and continuity on this device. When you're signed in, changes sync to your account.

Want to nuke everything on my side? Hit "Clear All Data" below and I'll wipe your crates and saved preferences from the database and clear local app data on this browser. That does not delete or change your Discogs collection or notes. You'd need to edit or remove those on Discogs itself.

Cookies & Storage

Essential cookies: HttpOnly cookies hold your OAuth session so you stay logged in without exposing tokens to JavaScript. These are required for the app to work and do not need separate consent.

Local storage: Theme, default view, filter and sort selections (when "Remember filter selections" is on), your analytics cookie choice, in-progress playback (current track and upcoming queue), remembered collection size for faster loading, and similar UI state. When you're logged in, the same preferences are also stored on the server (see above). IndexedDB: After your collection finishes loading, a cached copy of those pages may be stored on this device to speed up return visits until your Discogs collection size changes or you clear app data.

Optional analytics: When you opt in, Google Tag Manager may set analytics cookies to measure page views and basic interactions. The app may also store similar interaction events in Postgres (for example page path, event name, and label) to understand product usage, sometimes linked to your account ID when you're signed in. Analytics does not run until you accept. You can change your choice anytime in Settings under Data, or use Essential only on the consent banner.

Third-Party Stuff

The app talks to the Discogs API for your collection and notes. Their rules apply to that relationship.

Google Tag Manager handles third-party analytics cookies when you opt in. Google's privacy policy applies there. First-party product analytics events are stored in my Postgres database under the same consent choice.

Images get proxied for speed, but I don't hoard them. They're cached, not stored.

Data Management

Want to start fresh? Clear everything out. This button wipes:

All your auth tokens and session cookies

Every crate you've created, including which releases are in each crate (deleted from Postgres, gone forever. No takebacks)

Your saved account preferences on our server: theme, default view (grid or table), your analytics cookie choice, named saved views from the Views menu on Releases, filter/sort selections when "Remember filter selections" is enabled in Settings, and playback settings (auto-play on queue add)

Product analytics events linked to your account (when you had analytics enabled), such as page views and interaction labels

Local preferences on this browser: theme, view mode, filters, analytics cookie choice (you will be asked about analytics cookies again), in-progress playback (current track and upcoming queue), remembered collection size (to load large collections faster), cached collection pages in IndexedDB (for faster return visits on this device), and similar UI state

In-memory caches for the current browser session, including your loaded collection

Your Discogs collection and any notes you saved there are not affected. You can still see and edit them on Discogs or after you log in again here

You must be logged in to clear data.