Privacy Policy
Limen is an independent app for digging Discogs catalogues by ear. This policy says what we collect, why, who processes it, how long it stays and what you can do about it. It is written to be read, not to hide. Last updated 12 November 2026.
What we collect
- Your account. Your email address, if you give one — it is optional with a Discogs sign-in. It comes from the sign-in link you requested, from the box on the Home page, from Settings, or from the address you type at Stripe Checkout. Only an address you have verified receives sign-in links. If you set no DJ name and have no Discogs username, a neutral name such as “digger-x7k2qa” is shown as your name on public pages, never one made from your email address. Accounts created before November 2026 were given the part of their address before the @ as their name; we have replaced those names wherever they still matched the address, and you can change yours at any time in Settings. Also: your Discogs user id, username and avatar link if you connect Discogs; your DJ name and curator address; your plan and subscription status mirrored from Stripe; your email and notification settings; and, if your first visit arrived with campaign parameters or from another site, that source.
- Connections. Your Discogs access token, encrypted (AES-256-GCM) in our database with a key that exists only on the worker; your Spotify tokens, encrypted the same way, if you connect Spotify.
- Your listening. Every audition you start is recorded against your account. That record enforces the daily cap, builds your listening history and dig history, shapes the personalised playlists and discoveries, and is included in your data export. Guests are not recorded on our servers: a guest’s cap uses the signed cookie below and a guest’s history stays in the browser.
- What you make. Playlists and their records, dig history, the artists, labels, sellers and curators you follow, price watches, bundle checklists and wantlist-match notices, Gem Hunt searches, BPM taps, comments, reports you file (with a keyed code for the network you reported from, so two reports from one connection count once; never the address itself), label or artist page claims (evidence links and the Stripe Identity result), your public profile, push notification subscriptions, and feedback you send (with the page you were on).
- Your Discogs collection and wantlist. If you connect Discogs we mirror them so you can listen through them. The mirror is keyed by your Discogs user id, not your Limen account.
- Technical. Request logs with truncated IP addresses, which we also use for rate limits. No advertising or analytics trackers run on Limen.
Who processes it
Every recipient, and why:
We never sell your data. We never host, proxy or rehost Discogs images or YouTube media.
AI features
Three things call Google’s Gemini API, each only with catalogue data (titles, artists, styles, years) and the words you typed — never your email, ids or tokens.
- Search in your own words, the onboarding questions and prompt discoveries send your free text to turn it into catalogue filters. These run only where that feature is switched on. The translation of each phrase is cached indefinitely, without your account id.
- Describing a past dig (a Pro feature) sends your query and your local date.
- The titles, descriptions and curation of your discovery playlists use Gemini whenever the feature is configured. Up to four records from your library and up to 24 candidates are sent, with the name of an artist or label you follow. There is no separate opt-in for this.
Emails we send
- Sign-in, sign-up and email verification links, when you ask for them.
- The Daily Dig, the digest of announcements from people you follow and new wantlist matches from sellers you follow. One switch in Settings › Notifications turns all three on or off; wantlist matches also have their own email and push switches under Settings › Notifications › Sellers.
- Price alerts for watches you set. They are sent even when that switch is off, and only to a verified address.
- An acknowledgement when you report content, and a statement when we act on a comment or a report.
We do not send payment receipts ourselves; Stripe handles payment emails.
Your rights and controls
Export my data (JSON), in Settings › Account › Privacy & data, gives you everything we hold that is linked to your account: your account details, subscription, playlists and their records, public profile, comments, reports you filed, follows, price watches, dig history, discovery playlists, Gem Hunt searches, BPM taps, claims, feedback, notification settings, the devices you get push notifications on, your Discogs collection and wantlist mirror, and your most recent 5,000 listening events. Secrets are never in the file: no tokens, no push keys. Where a list is very long the file keeps the newest entries and says so.
Delete my account, in the same place. At once: your Discogs and Spotify tokens are deleted, every session is signed out, any Pro subscription is cancelled, push notifications stop, unused sign-in links are deleted, and sign-in is refused. Your public pages, playlists, comments and announcements are hidden from everyone straight away. After 30 days a daily job permanently deletes your account and everything linked to it, including the mirror of your Discogs collection and wantlist. Two things outlive the deletion: reports and moderation records that contain your email address, which we keep as evidence for content decisions, and the anonymised cache of AI search phrases. Stripe keeps its own payment records for as long as accounting law requires. You must also revoke Limen at discogs.com/settings/applications — we cannot do that for you.
If you are in the EU, EEA or UK you have the rights the GDPR gives you: access, rectification, erasure, portability and objection. Exercise access and portability with Export my data, erasure with Delete my account, and rectification by editing your DJ name and email in Settings.
Cookies and storage
Every cookie we set is HttpOnly and SameSite=Lax; none is used for tracking.
Your browser also keeps, on this device only: your YouTube consent, theme, playback preferences, the Covers or List view of Gem Hunt results and of a seller’s stock, dismissed tips, a guest’s dig history, your last Gem Hunt criteria, a short buffer of listening events waiting to be sent, and the app shell for offline use. No YouTube player exists before you consent; YouTube, Instagram and SoundCloud set their own cookies under their own policies once you load one of their players.
How long we keep it
Until you delete your account, then the 30-day window above. On top of that, a daily job deletes listening events after 24 months (Discogs wantlist and collection write records after six years, as evidence of what we did with your account), rate-limit records after 2 to 31 days, and used or expired sign-in links after a day. We do not currently purge dig history, reports, moderation records or the AI phrase cache on a schedule. A comment you delete disappears from Limen but its text stays in our records until your account is deleted.
Changes
When this policy changes we update the date at the top.