Privacy Policy

What we collect

• Camera images — scanned vinyl label photos are sent to Threshold's Firebase Cloud Functions proxy and then to Anthropic's Claude Vision API for text recognition. Captured images are also stored in Threshold's private app folder on your device. Threshold does not intentionally retain those images in Firebase after the request is processed.
• Track ID audio — when you use Track ID, Threshold records a short audio sample from your microphone and sends it through the Firebase Cloud Functions proxy to ACRCloud for identification. The temporary audio file is deleted from the device after the identification attempt. Threshold does not intentionally retain the audio in Firebase.
• Collection data — records, crates, playlists, listen history, custom artwork, tags, notes, places you've added, and related metadata are stored locally in Threshold's private app storage on your device. Dig locations and visits stay on-device, the same as the rest of your collection. Your collection is not currently synchronized to a Firebase account.
• Backups — Threshold creates rotating local backup files on your device. A manual export leaves the app only when you choose a destination using the system share sheet.
• Account and service identity — Threshold creates an anonymous Firebase identity so proxied services can enforce usage limits. If you choose to sign in, your email address (or the name/email associated with your Google or Apple account) is used to create and identify your account through Firebase Authentication.
• Connections & Recommendations — this is the one feature where data is shared between accounts, and it is the only exception to "your collection stays on this device" described above. If you choose to connect with another collector (by scanning a QR code or exchanging a short, single-use code directly with them), Threshold stores which two accounts are connected and the display name you've chosen for yourself, so the other person knows who they're connected with. If you send someone a recommendation, the record's artist, title, catalog number, and label are stored so they can find it — nothing else about your collection is shared. A display name is never unique, never searchable, and never publicly listed; it exists only to be legible to someone you've directly connected with.
• BETA diagnostics — scan and Track ID outcomes, extracted artist/title/catalog text, candidate-match details, feedback, and failure diagnostics are stored in Firestore with your Firebase user identifier to help evaluate matching quality.
• Crash reports — release builds send crash and diagnostic information to Firebase Crashlytics.

What we do NOT collect

• We do not sell your data.
• We do not serve ads or use ad identifiers.
• We do not track you across other apps or websites.
• We do not use microphone access outside an active Track ID session.
• We do not currently synchronize your collection database to Firebase, other than the specific Connections & Recommendations data described above.
• We do not build a searchable directory, contact list, or public profile of any kind — there is no way to look someone up by name, and a display name cannot be claimed or reserved.
• We do not tell the sender of a recommendation whether, when, or if you opened it or added it to your collection.

Third-party services

This application uses the Discogs API but is not affiliated with, sponsored, or endorsed by Discogs. "Discogs" is a trademark of Zink Media, LLC. Data provided by Discogs is used to match scanned records and displayed record/track information — only extracted text is sent to Discogs, no personal data.

• Firebase (Google) — optional account sign-in, cloud functions, anonymous service identity, BETA diagnostics, usage accounting, operational caching, and crash reporting. Subject to Google's Privacy Policy.
• Google Sign-In / Sign in with Apple — if you choose to sign in with Google or Apple, those providers share basic profile information (name, email) with us to create your account. Subject to Google's and Apple's respective privacy policies.
• Anthropic (Claude) — scanned label images are processed by Anthropic's Vision API to extract artist/title/catalog text. Subject to Anthropic's Privacy Policy.
• ACRCloud — audio fingerprinting service used by the Track ID feature. A short audio sample is transmitted to identify the playing track. Subject to ACRCloud's Privacy Policy.
• Deezer — track preview audio is streamed directly from Deezer when you tap play on a track. Subject to Deezer's Privacy Policy.
• MusicBrainz and Cover Art Archive — release metadata and cover art may be requested as a fallback when Discogs does not return a confident match.
• Resend — delivers BETA feedback submitted through this website (see "Website feedback" below) as an email. Subject to Resend's Privacy Policy.

Website feedback

The BETA feedback form on this website (threshold.static-channel.com/beta/feedback) is separate from data the app itself collects, described above. Submitting the form sends an email — the moment you selected (a find, a set, or something that got in the way) and any note you wrote — directly to Threshold's operator. It is not stored in a database; the email itself is the only record.

An email address is only collected if you explicitly check "May we follow up about this?" and provide one — the field does not appear otherwise. If given, it's used only to reply about that specific note.

Retention and deletion follow the same informal model as any other email sent to Threshold: it stays in the operator's inbox until deleted, the same as a message sent through Contact or the app's own Settings → Send Feedback. Contact us to request deletion of a specific submission.

The feedback form does not use cookies, analytics, or tracking of any kind, and does not require signing in.

Your rights

You can delete your Firebase Authentication account and the server-side user data handled by the in-app deletion flow from Settings → Delete Account. BETA diagnostic and feedback records may require a separate deletion request. Because the collection is stored locally, deleting the Firebase account does not delete collection files or backups from your device.

Deleting your account also removes your Connections and any recommendations you sent that haven't yet been added to the recipient's collection. A recommendation the recipient has already added is, from that point on, part of their own collection history rather than something tied to your account — deleting your account does not remove it from theirs, the same way giving someone a physical record isn't undone by anything that happens to you afterward.

EU/UK residents have additional rights under GDPR including data access, deletion, and portability. Contact us to exercise these rights or to request deletion of BETA diagnostic data.

Data retention

Local collection data, captured scan images, and automatic backups remain on your device until Threshold rotates or replaces them, app data is cleared, or Threshold is uninstalled. Manual backup copies remain wherever you chose to save them. This app repository does not enforce a fixed retention period for server-side BETA diagnostics or service-usage records. Contact us to request deletion. Firebase and the third-party services above apply their own retention policies to data they process.

A record of a sent recommendation is kept even after the recipient has claimed it, so that resolving a display name in connection with it continues to work correctly later — this record is never readable directly and exists only to support that one feature.