Last updated: September 28, 2026
PressCheck for Discogs (“PressCheck,” “we,” “us,” or “our”) is developed and operated by Hadrien Patin, France, who is responsible for the personal data processing described here.
Pre-release notice: PressCheck is being prepared for release. For support and privacy requests, contact [email protected]. RevenueCat, Mixpanel, and Sentry diagnostics are integrated, as described below.
This policy explains the information processed through the app and its backend, the reasons for processing, our service providers, retention, and your choices.
PressCheck helps you compare record editions, check your connected Discogs library, and keep your own shopping records. Searches and Discogs library actions use our backend and Discogs. Personal visits, purchase details, buying criteria, and recently viewed references are stored on your device as described below.
We do not sell personal data or use it for cross-company behavioral advertising. PressCheck does not ask for your Discogs password or receive your full payment-card details.
Camera images used for barcode recognition are processed on your device. The recognized barcode or search text is sent to our backend and Discogs to find releases.
You can save visits, selected release references, decisions, asking prices, budgets, currencies, and notes. You can also save the date, price, shop, condition observations, and notes for a specific collection copy, and buying criteria for a release or album. These records are kept in protected files, separated by PressCheck account. They do not contain a saved copy of Discogs catalogue descriptions or artwork. PressCheck does not upload these personal-record files to its backend or synchronize them between devices. Device backups may include them, depending on your Apple and device settings.
The recent-history feature stores up to 50 release references and the time you viewed each one. Entries older than 30 days are excluded from display and export, and removed from the file when the app runs its cleanup. Turning off Save recent editions in Account → Preferences clears the history and stops recording new entries. Your default currency is a local preference for new entries; it does not convert existing amounts. General preferences and onboarding progress are also stored locally. The app provides separate JSON exports and deletion controls for visits, purchase history, buying criteria, and recently viewed editions. Exports include the relevant account and record references and your entered information. Deletion in PressCheck does not remove earlier exports or device backups. Personal notes in these files are distinct from Discogs collection fields and wantlist notes, which are sent to our backend and Discogs when you explicitly edit them.
You can refuse camera access and enter a barcode manually. Change camera permission in iOS Settings. PressCheck does not upload the camera feed or photographs for barcode scanning, and does not require contacts, microphone, or location access for this feature. Session credentials are stored in the iOS Keychain. A separate journal records requested Discogs changes to recover from interrupted responses without silently creating duplicates; it can contain release or copy references, fields, notes, and purchase details needed to finish an acquisition locally. The Keychain also holds a receipt used to resume account-deletion cleanup. Removing the app does not necessarily remove Keychain entries. Catalogue responses, collection and wantlist views, and artwork are temporarily cached in memory, not kept as a permanent offline library.
Connecting Discogs creates a PressCheck account record linked to your verified Discogs account ID and username; this flow does not request your full profile or email address. We create a separate internal PressCheck account identifier. Depending on the features you use, the backend processes collection copies, release IDs, folders, conditions, ratings and notes; wantlist entries and notes; search terms and barcodes; and changes you ask the app to make.
You sign in on Discogs through its authorization flow. Our backend receives the authorization credentials needed to access the account you connect. Discogs tokens and token secrets are encrypted on the server; your device stores separate PressCheck session credentials. We do not receive your Discogs password.
Our backend reads, temporarily caches, and synchronizes relevant Discogs data, and sends additions, changes, or deletions you request. Discogs processes those requests and retains the resulting content under its own terms, privacy policy, and account visibility settings. Artwork requests also disclose technical connection information to the image host.
Signing out revokes the current device session and clears the app's active private views. It is not the same as deleting your PressCheck account or revoking authorization on Discogs. You can revoke access in Discogs connected applications. Section 12 explains account deletion.
This application uses Discogs’ API but is not affiliated with, sponsored or endorsed by Discogs. ‘Discogs’ is a trademark of Zink Media, LLC. Data provided by Discogs. See Discogs Privacy Policy and Discogs API Terms of Use.
Vercel hosts the PressCheck backend and Neon provides its PostgreSQL database. They process account information, encrypted authorization credentials, cached responses, synchronization state, pending operations, subscription state, guided-match allowances, and optional analytics described below. Application logs record a request identifier, route pattern, method, status, and duration rather than request bodies or raw search queries.