Terms of Service

FilterMyDiscogs is a free tool for browsing and organizing your Discogs collection. It stays in continuous beta: features change often and bugs are expected. These terms describe how the app works and what to expect.

• The app is provided as-is. I do my best to keep it running smoothly, but I can't guarantee it will always be available or error-free.
• Found a bug? Open a GitHub issue with steps to reproduce when you can. Ideas and feedback belong in GitHub Discussions, or email noise@filtermydisco.gs.
• 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.
• Please keep your Discogs account credentials secure. You are responsible for activity on your Discogs account.
• Sign-in uses OAuth, so I never see your Discogs password. Your login stays between you and Discogs.
• You can revoke the app's access anytime in your Discogs account settings.
• Features may change over time, and I may need to take the service offline for maintenance or other reasons.
• The app is free today. If that ever changes (for example, paid features or subscriptions), I'll explain the change before it applies to you.

Privacy Policy

I don't sell your data or run ads against it. This section describes what the app stores, where it lives, and why.

What I Collect

• Sign-in: OAuth 1.0a with Discogs. I never see your password. Session tokens are stored in httpOnly cookies so the server can call Discogs on your behalf; page JavaScript cannot read them.
• Your collection: Release data, including notes, comes from the Discogs API. It is cached in your browser to keep the app responsive. After a full load, a copy may live in IndexedDB on this device so return visits can skip re-downloading every page; on sign-in we re-check collection size with Discogs 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.
• Notes you edit: When you save notes in the app, that text passes through my server to the Discogs API. I do not store note content in Postgres.
• Crates: Crate names and which releases belong in each crate are stored in Postgres so they persist between sessions.
• In-app playback: Per-track play and listen counts (plus basic track labels) are stored in Postgres. On repeat on the dashboard shows both; release tracklists show listen counts only. Counts increment when playback actually starts or you resume from pause, not when a paused session reopens after a page refresh. This is separate from optional product analytics below.
• Account preferences (when you're signed in): theme, default view (grid or table), whether to remember filter selections, whether to auto-play when adding to an empty queue, whether to extend the playback queue with similar releases from your collection when up next runs low (opt-in; default off), your analytics cookie choice (when set), named saved views from the Views menu on Releases, and, when enabled, saved filter and sort choices (styles, years, formats, sort order, genre/style, format, and release year match mode, and search text). These sync across browsers; your full collection is not stored in Postgres.
• Optional analytics (only if you opt in): product usage events in Postgres (for example page path, event name, and interaction label). When you're signed in, events may include your account ID. I use this to improve the app, not to sell data.

What I Do With It

• Collection data powers browsing, search, and filters in the app.
• Note edits are sent to Discogs on your behalf. I don't analyze note text or keep a separate copy in my database.
• Collection pages flow through your browser and my API routes, which proxy Discogs. Crates and account preferences are saved to Postgres so they survive when you close the tab.
• Theme, view, filter, playback, and analytics cookie preferences are also kept in your browser for fast loads on this device. When you're signed in, changes sync to your account.
• You can remove everything stored on my side with "Clear All Data" below. That wipes crates, in-app playback stats, and saved preferences from the database and clears local app data in this browser. It does not delete or change your Discogs collection or notes. You'd manage 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 parties

• The app uses the Discogs API for your collection and notes. Discogs' own terms and privacy policy apply to that relationship.
• If you opt in to analytics, Google Tag Manager may set cookies; Google's privacy policy applies there. First-party product analytics events are stored in my Postgres database under the same consent choice.
• Cover images are proxied for performance and cached briefly; they are not permanently stored on my servers.