Privacy Policy

Last updated 19 November 2026

The short version. Vinyl Index stores the collection you build and the account you sign in with. Photos you scan are sent away to be identified and are not kept afterwards. Nothing is sold, and there is no advertising. You can delete your account and everything in it from inside the app at any time.

What we collect, and why

CategoryWhat it isWhy
Account detailsEmail address, a user ID issued by our authentication provider, and the display name you choose. If you sign in with Apple or Google, whatever name that provider returns.To sign you in and tie your collection to you across devices.
Your collectionRecords you save, plus any notes, condition and ownership details you add.This is the product. It syncs so you can reach it from any device you sign in on.
Scan photosPhotographs of record sleeves you choose to scan.To identify the release. See “Photos you scan” below — these are not kept.
Scan usage countsA per-month count of how many scans you have run.To enforce the monthly fair-use scan allowance that comes with a subscription.
Scan historyFor each scan: the text read off the sleeve, the releases we matched against it, and which one was chosen.So a scan can be revisited and corrected. The photograph itself is not part of this — see “Photos you scan”.
Feedback you sendThe message you write, with your account email address, the app version and build, and your platform attached. A copy is emailed to our support inbox.To answer you, and to fix what you reported. Only created when you use the feedback form.
Sharing and friendsFriends and friend requests, the people you blocked or muted, your invite link, your wishlist link, collection-sharing preferences, records you share as a link (the record's title, artist, cover and catalogue details), reports you file about another collector (the reason and anything you write), your friend notification settings, and new-record batches: which records you added by hand and on which day (never the time), which friends they reached, whether those friends have seen them, the reactions friends add, and the records you let a friend know you found (which friend and which record, never where you were).Only created when you use friends, comparison or sharing. Records you add tell the friends who can see your shelf, unless you turn "Records I add" off; an import never does. In Store mode, a friend who wants or owns the record you are looking at is named only while they share that list with you. Anyone you send your wishlist link sees the records on your wishlist and your name, never your notes, prices or the records you own, until you turn the link off or make a new one. A report reaches us as an alert so we can act on it; the collector you report is never told.
Subscription and purchasesWhether you have an active subscription, which product, and the purchase and renewal history behind it. Card details are never sent to us — Apple and Google handle payment.To unlock scanning for subscribers, and to restore a purchase on a new device.
Push tokensA device push notification token.Only stored while you allow notifications and want at least one kind: the daily record, or friend notifications. Turning them off, removing permission or signing out releases the token.
DiagnosticsCrash reports and error traces, including device model and OS version, plus a masked recording of the screens leading up to a crash. Separately, our API keeps a request log for 30 days that includes your IP address. See “Crash recordings” below.To find and fix crashes, and to investigate abuse of the API. Not used to build a profile of you, and never used to work out where you are.

Photos you scan

This is the part worth reading closely, because it is the most sensitive thing the app does.

When you scan a sleeve, the photo is sent to our server, which passes it to the recognition services listed below so they can read the text on the cover and identify the pressing. Once the identification comes back, we discard the photo. We do not store your scan photos, we do not attach them to your account, and we do not use them to train any model of our own.

One qualification, because “discarded” should mean what it says. Recognition normally runs on Google Cloud Vision and on Gemini through Vertex AI, where the image stays inside our own project and is not retained. If Gemini is unavailable we fall back to OpenAI, and OpenAI’s standard API terms let them keep the image for up to 30 days for abuse monitoring before deleting it. That copy is not ours, is not linked to your account, and is not used for training. We are pursuing zero-retention terms for that fallback; until we have them, this is the honest version.

The recognition providers process the image under their own terms as our processors. We do not send them your email address, your name, or your collection alongside the image.

The app asks for camera access purely so you can take these photos, and only at the moment you choose to take one. Picking an existing picture instead uses the system photo picker, which hands us the one image you select — the app never asks for access to your photo library, and cannot see anything else in it.

Importing a collection

When you import a file — a Discogs export, a CLZ or MusicBuddy export, or a spreadsheet — the app reads it on your phone. The file itself is never uploaded. Only the records it adds reach us, stored exactly as records you add yourself are.

When you import by Discogs username, your phone asks Discogs for that public collection directly, and later for the covers of records an export brought without them; Discogs sees your IP address and the username or releases asked about. The username stays on your phone, so it can be offered the next time you import. We do not store it.

Crash recordings

When the app crashes, our crash reporter sends us a short recording of the screens you were on just before it happened. It is the difference between knowing that something broke and knowing what you were doing when it did.

Two things bound it. Only crashes are recorded — we never sample sessions that worked, so if the app has not crashed for you, nothing has been recorded. And all text and images are masked: the recording shows the shape of the screen, with every word and every cover blocked out, so your collection, your notes and your email address are not in it. It carries no account identity either, so we cannot tell you which of our users a given crash came from.

These recordings go to Sentry and are deleted on their rolling retention window, typically 90 days.

Who processes your data

We use the following providers. They act on our instructions and are not permitted to use your data for their own purposes.

ProviderRoleWhat it sees
ClerkAuthenticationEmail address, name, account identifiers, sign-in IP address
SupabaseDatabase and storageAccount, collection, sharing and usage data
Google CloudRuns our API, and stores its logsEvery request the app makes to us, and a log line for each scan carrying your user ID and the IP address the request came from, kept for 30 days
Google Cloud VisionReads text from sleeve photosThe scan photo, transiently
Google Gemini (Vertex AI)Identifies the release from artworkThe scan photo and extracted text, transiently
OpenAIIdentifies the release from artwork, only when Gemini is unavailableThe scan photo and extracted text. Retained by OpenAI for up to 30 days — see “Photos you scan”
RevenueCatSubscription managementYour user ID, and your purchase and renewal history
SentryCrash reportingError traces, device and OS version, masked crash recordings
Google ML KitReads text on your phone before a scan is sentUsage and performance data about the text recognition, sent to Google for its own analytics, not linked to you
ExpoApp updates and push deliveryAn install identifier each time the app launches, and your device push token
Discogs, MusicBrainzMusic metadata lookupSearch terms only — never your identity or photo
Discogs marketplaceLive prices in store modeRequested directly by your device, so Discogs sees your IP address and which record you priced
Discogs collection importReads the public collection you ask to importRequested directly by your device, so Discogs sees your IP address and the username you entered
Discogs release lookupsCovers and genres for records you importRequested directly by your device, so Discogs sees your IP address and which releases were looked up
Cover Art Archive, Discogs image CDNServes cover imagesRequested directly by your device, so they see your IP address and which covers you viewed
SpotifyTrack listings and previewsThe artist and album being looked up
DeezerAlbum links, if you choose to listen on DeezerThe artist, album and track titles being looked up, sent from our server, never your identity
VercelHosts this websiteStandard web server logs for pages you visit here
VimexxHosts our email (info@vinylindex.app)Feedback you send from the app, and any email you send us
Apple, GoogleApp distribution and paymentsHandled under their own privacy policies

Some of these providers operate outside your country, including in the United States. Where data leaves the European Economic Area, it is transferred under the safeguards those providers offer, such as Standard Contractual Clauses.

What we do not do

If you are in the UK or the European Economic Area, we rely on these lawful bases under the GDPR:

How long we keep it

Your rights

You can ask us to give you a copy of your data, correct it, delete it, or restrict how it is used. You can also object to processing based on legitimate interests, and complain to your local data protection authority.

The fastest route for deletion is in the app itself — see the steps here. For anything else, email info@vinylindex.app and we will respond within 30 days.

Children

Vinyl Index is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.

Security

Data is encrypted in transit. Access to the production database is restricted, and our database enforces row-level rules so one account cannot read another’s collection. No service can promise perfect security, but we will notify you and the relevant authority if a breach affects your data.

Changes to this policy

If we change what we collect or who processes it, we will update this page and move the date at the top. Material changes will also be surfaced in the app.

Contact

The data controller is Niky Dieben. Reach us at info@vinylindex.app.