Privacy Policy

Version: 2026-07-23 · Last updated: 23 July 2026

Draft — under legal review. This document is published in draft so it can be read alongside the alpha. It has not yet been reviewed by our lawyers, and will be finalised before Kollekta opens beyond the invite-only alpha.

The short version

• We never sell your data. Not to advertisers, not to data brokers, not to anyone. There is no version of Kollekta where that changes.
• We collect what we need to run the app for you, and not much else.
• The Kollekta app sets no cookies, and does no analytics or advertising tracking. Our marketing website uses Google Analytics — but only if you accept its cookie banner. If anything changes in the app, we'll tell you and ask first.
• Your collection is visible only to you (and our administrators) today. If sharing features arrive, you'll choose what others see.
• We use aggregated, de-identified data — combined across accounts so it identifies no one — to power comparisons and community features.
• Your Discogs data is yours. We only touch it because you told us to, and we never hand it to anyone else.

The rest of this page is the detail. It describes how Kollekta actually works as at the version date above — not how we hope it might work.

1. Who we are

Kain Tietzel trading as FNRBLR, a sole trader in New South Wales, Australia, of FNRBLR at Workit Spaces, Unit A1/35–39 Bourke Road, Alexandria NSW 2015, operates Kollekta. Kollekta is a product of FNRBLR. We are the entity responsible for the personal information described here.

This policy covers the Kollekta app (alpha.kollekta.app) and website (kollekta.app). It sits alongside our Terms of Use.

Questions, requests, or complaints: legal@fnrblr.com.

2. What we collect, and why

2.1 When you join the waitlist

Before you have an account, the waitlist form collects:

• Email address — to send your confirmation and, later, your invitation
• Country — to pace invitation waves
• Approximate collection size — to decide which wave suits you
• Format mix (vinyl / CD / cassette / digital / other, as percentages) — same
• How you manage your collection today — same
• Which streaming services you use — same

We use this only to run the waitlist and decide who to invite. We don't send marketing to it. To stop the process at any point, or to have your application deleted, email us — see section 7.

2.2 When you have an account

• Email address — sign-in, account email, and to contact you about the Service
• First and last name — to address you properly; first name is required at signup
• Username — identifies your account
• Password — sign-in. Handled by our authentication provider (Supabase) — it is hashed, and we never see or store your plain password
• Avatar image, if you upload one — displayed in your profile
• Your streaming service preferences — to show the right listen-on buttons

2.3 Your collection data

The substance of the product: the albums in your Collection, Up Next and Want List; the pressings and formats you record; any notes or custom labels you add; your cover-art and pressing preferences; and your play history — which album you played, in what format, and when.

We use this to provide the Service to you and to build the Insights in your own account. Your play history and collection are shown to you, and are not shown to other users in any identifiable form. We also use data in aggregated or de-identified form — combined across accounts so it doesn't identify anyone — to power comparative and community features (for example: how your collection compares with other Kollekta users, how many users own an album, or year-in-review summaries) and to understand and improve the Service. Aggregated data never includes your name, username or anything that identifies you, and we never sell it.

2.4 If you connect Discogs

Connecting is optional, and only happens if you choose it.

• Your Discogs username — Identifies the connected account
• Discogs access tokens — Encrypted at rest using AES-256-GCM. The encryption key is held as a server-side secret, separate from the database
• Your Discogs collection and wantlist — Retrieved on your authorisation, stored so the app works, and kept in sync
• A cached snapshot of your Discogs collection and wantlist — Held on your account record so we can compute what has changed since the last sync, without re-downloading everything

We treat this as your data, held on your behalf. Under Discogs' own terms this is Restricted Data, and we take the resulting obligations seriously:

• we never transfer it to any third party;
• we never use it for advertising or marketing, and we never feed it to any advertising or marketing platform. This is an absolute rule at Kollekta, not a current preference — see section 5;
• we never make it public (see section 6);
• we don't aggregate it into anything we sell.

You can disconnect Discogs at any time from your profile.

2.5 Technical and activity data

• Activity events — Significant actions: signing in, signing up, running a Discogs sync. Each record includes your IP address and browser user-agent. We use these to operate the Service, investigate problems, and detect abuse
• Search performance measurements — When you search, your browser reports timings: how long the request took, its size, whether the connection was cold, and the number of characters you typed (not what you typed). The measurement itself contains no identifier and no search text; it is emitted to our hosting provider's logging. The request carrying it is authenticated, so it is not anonymous to us in the strictest sense — we're telling you rather than claiming otherwise. We use it only to make search faster
• Server logs — Our hosting provider (Cloudflare) records requests, including IP addresses, as part of running the service and protecting it from abuse

2.6 If you contact us

Feedback sent from inside the app includes your message, the page you were on, and an automatically-captured technical context blob: the app version, your browser user-agent, your screen size, and any recent errors your browser logged. You can attach a screenshot. Support messages sent from the website include the name, email and message you provide.

Please note: feedback and support messages are kept as an operational record and are not automatically deleted when an account is deleted — the link to your account is removed, but the message, its technical context and any screenshot remain. See section 7.

2.7 What we do NOT collect

• No payment details today. Kollekta is currently free. If we introduce paid features, payments will be handled by a specialist payment provider — we'd receive confirmation of payment, not your full card details — and we'll update this policy first.
• No advertising identifiers. There is no advertising ID, tracking pixel or cross-site profile in the Kollekta app, and your personal information is never sent to advertising platforms — not for anyone's advertising, including our own. Our marketing website uses Google Analytics (loaded only if you accept its cookie banner) and may add advertising measurement in future, with consent where required (section 3). We may also add product analytics inside the app to understand how features are used and improve them — never for advertising — and we'll update this policy first.
• No precise location. We don't ask for or track your location. You may in future be able to set a city or timezone in your profile so features like insights and comparisons work properly — that's information you choose to give us.
• No contacts. We will never ask for your contacts.
• Camera — only if you scan, and the pictures never leave your device. Kollekta can use your device camera to read a barcode off a record sleeve so you don't have to type the number. Access is requested only when you start a scan, is entirely optional, and is controlled in your browser and device settings. The camera picture is read on your device — we never upload, store or transmit any image, video or frame from it. The only thing that reaches us is the barcode number itself, handled exactly like a number you typed into the search box. A future Kollekta mobile app may also offer optional microphone access (recognising what you're playing) on the same terms.
• We don't buy personal information about you from anyone.

3. Cookies and storage on your device

The Kollekta app sets no cookies — not for analytics, not for advertising, not even for sign-in. Our marketing website (kollekta.app) uses Google Analytics, which sets one analytics cookie — but only if you accept its cookie banner. Decline it, or simply ignore it, and nothing is stored.

Inside the app, what we use instead is your browser's local storage, for these purposes:

• Your sign-in session (a token from our authentication provider) — keeps you signed in. Essential — the app can't work without it
• Interface preferences: sidebar state, view mode, artwork size, panel width, expanded sections, dismissed notices, filters — remembers how you like the app. Functional
• The last album you logged a play for — prevents accidental double-logging. Functional

None of this tracks you across other websites. None of it is shared with anyone. You can clear it via your browser at any time; you'll be signed out and your preferences will reset.

How we handle cookies and consent

The Google Analytics cookie on our marketing website is the only cookie we set today, and only with your consent. As Kollekta grows we may introduce others — particularly on the marketing website. We group cookies into these categories and handle each accordingly:

• Essential — sign-in and security, the basics the Service can't run without. No consent needed (they're strictly necessary).
• Functional — remembering your preferences and choices. Used to improve your experience; described here.
• Analytics — understanding how people find and use Kollekta. Only where you've agreed, where consent is required.
• Advertising measurement — measuring our own marketing, on the marketing site only, never inside the app. Only where you've agreed, where consent is required.

Before any non-essential cookie or similar technology goes live, we will publish a consent notice and ask you — and where consent is required (for example under the GDPR/ePrivacy rules for visitors in the EU/UK), we will not load it unless you agree. We'll update this policy, and its version date, first. Any such tooling will be walled off from your Discogs collection and wantlist data, permanently and by design. See section 5.

4. Who we share it with

We never sell your personal information, and we never hand it to advertising platforms — not for anyone's advertising, including our own.

We use a small number of service providers who process data on our instructions in order to run Kollekta:

• Supabase — Authentication and our database — this is where your account and collection live. Australia (Sydney region)
• Cloudflare — Hosting and application processing, caching, file storage (avatars, artwork, feedback screenshots), bot protection (Turnstile), image resizing, and request logging. Global network
• Resend — Sending transactional email — your confirmation, invitation, sync notifications and account emails. They receive your email address and the content of those emails
• Discogs — Only if you connect a Discogs account, and only to sync your own data with your own Discogs account

…and other providers we may engage to help run the Service, under contractual protections equivalent to these. We keep this list current in substance rather than listing every vendor.

If you accept analytics on our marketing website, Google (Google Analytics) receives that site's usage data — never your account or collection data.

We also share information:

• when you tell us to — for example, connecting Discogs, or following a link to Apple Music or Spotify;
• when the law requires it — a court order, or a lawful request from an authority. We'll tell you where we're allowed to;
• to protect people — to investigate fraud, abuse, security incidents, or threats to someone's safety;
• in a business transfer — if the Kollekta business is transferred (including a transfer to a company, such as FNRBLR Pty Ltd), your information moves with it, subject to this policy. We'll tell you.

Within FNRBLR

Kollekta is a product of FNRBLR. Your data may be used within FNRBLR to operate and improve Kollekta and to build closely-related FNRBLR products and services, always under this policy. It is never sold, and your Discogs-synced data never leaves the wall in section 5.

A note about album artwork

Album cover images are usually linked directly from their source — the Cover Art Archive or Discogs' image servers — rather than copied onto our servers. That means your browser fetches those images from those hosts directly, so they can see your IP address and which images you requested. We don't send them anything that identifies you, but we'd rather explain that than let you assume otherwise.

Who at Kollekta can see your data

Kollekta is a small operation. Administrators — and, as the community grows, a small number of moderators — can see account data, collections and feedback in order to run the Service and help you; moderators see only what they need for that role. Some maintenance tools, run by us, can decrypt Discogs tokens in order to repair sync problems. Administrative actions are recorded in an audit log.

5. The Discogs advertising wall — a commitment

Because it matters and it's easy to erode, we're stating it separately:

Your Discogs-synchronised collection and wantlist will never be sent to, or used by, any advertising, marketing or analytics platform.

This is required by Discogs' API terms, and it's also simply what we think is right. It applies to any analytics or advertising technology we adopt in future (section 3): such tools will be architecturally separated from Discogs-sourced data, not merely configured to ignore it.

6. What others can see

As at the version date of this policy, no part of your account or collection is visible to anyone but you and our administrators (and moderators, as described in section 4). Every part of the app requires you to be signed in. There are no public profiles, no public collections, no feeds, and no follower lists.

We're building features that will let you share parts of your profile or collection — they may appear during the alpha. If and when they do, you'll be able to choose whether your profile is public, we'll explain exactly what becomes visible before the feature reaches you, and your Discogs-synced collection will only ever appear publicly on your explicit opt-in. We'll update this policy at ship time.

Separately, the aggregated, de-identified statistics described in section 2.3 may appear across the app — comparisons and community features that never identify you.

7. How long we keep it, and how to get rid of it

We keep personal information for as long as we need it to provide the Service, and afterwards where we have a legal reason to.

Deleting your account

During the alpha there is no self-serve delete button. To delete your account, email legal@fnrblr.com from your account's email address and we'll action it. We aim to do so within 30 days, and usually much faster.

Being straight with you about how it works today:

• We first disable the account. You're signed out and can't sign back in. Your data still exists at this point, so that an accidental or disputed deletion can be reversed.
• A full deletion removes your account and your collection, Up Next, Want List and play history.
• A disabled account is purged automatically after 30 days. A daily job permanently deletes accounts whose 30-day window has passed — so a disabled account doesn't sit around indefinitely, and you don't have to chase us. Ask us to delete sooner and we'll action it straight away rather than wait for the window.
• What we keep afterwards is listed immediately below — it's deliberately narrow.

What survives a deletion

• Feedback and support messages you sent, and the full conversation that followed — the link to your account is removed, but the messages, their technical context and any screenshots remain, as an operational record.
• A record of the deletion itself. When an account is deleted we keep a narrow history row: the email address, the username, when the account was created and when it was deleted, and the reason. We keep it so we can recognise a returning applicant, honour a re-invite, and stop a removed account being immediately recreated. It holds no names, no collection content and no counts.
• Administrative audit records of the deletion itself, which include the email address and username of the deleted account.
• Your waitlist application, if you joined via the waitlist — this is currently retained. Ask us and we'll delete it.
• Backups, which cycle out over time.

Other retention

• Support conversations (your ticket, our replies, yours, and any screenshots) — Retained as an operational record, including after you remove a ticket from your list or delete your account. Ask us and we'll delete it
• Deleted-account history (email, username, dates, reason) — Retained after the account is gone, so we can recognise a returning applicant and honour a re-invite
• Waitlist applications — Retained until you ask us to delete them
• Activity events (incl. IP, user-agent) — Retained for the life of the account; deleted with it. We have not yet set a shorter limit — we intend to
• Search performance measurements — Held in our hosting provider's logs under their retention settings; contain no identifier
• Server/request logs — Per Cloudflare's retention

8. Your rights

Under the Australian Privacy Principles — and, if you're in the EU or UK, under the GDPR — you can:

• ask what we hold about you, and get a copy;
• correct anything that's wrong (much of it you can edit yourself in your profile);
• ask us to delete your account and data (section 7);
• withdraw consent — disconnect Discogs, or stop using the Service;
• object to, or ask us to restrict, certain processing;
• ask for portability of data you gave us, in a machine-readable form;
• complain if you think we've mishandled your information.

Email legal@fnrblr.com. We'll respond within 30 days. We'll need to be satisfied of your identity before acting on a request — usually, that you can send from the account's email address.

If we get it wrong: tell us first and we'll try to fix it. If you're not satisfied, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au). In the EU/UK, you can complain to your local supervisory authority.

Legal bases (EU/UK visitors). We process your data to perform our contract with you (running your account and collection), on our legitimate interests (securing the Service, preventing abuse, making it faster), with your consent (connecting Discogs; any future analytics), and to meet legal obligations.

9. Where your data is, and international transfers

Your account and collection are stored in Australia (our database and authentication provider run in the Sydney region).

Kollekta is served worldwide through Cloudflare's global network, so requests and cached content may be processed at a location near you, and our email provider may process email outside Australia. Where information is transferred overseas, we take reasonable steps to ensure it is handled consistently with the Australian Privacy Principles, and we use providers who offer appropriate contractual protections.

10. Security

• Discogs tokens are encrypted at rest with AES-256-GCM; the key is a server-side secret held separately from the database.
• Passwords are hashed by our authentication provider; we never see them.
• Everything is served over HTTPS.
• Data endpoints require authentication; administrative endpoints require an administrator account and are audit-logged.
• Public forms are rate-limited and protected by Cloudflare Turnstile.

No system is perfectly secure. If there's a data breach that's likely to cause you serious harm, we'll notify you and the OAIC as the Notifiable Data Breaches scheme requires.

Found a security problem? Please tell us at legal@fnrblr.com rather than disclosing it publicly. We won't pursue anyone who reports a genuine issue in good faith.

11. Children

Kollekta is intended for people aged 13 or over, or older where the law of your country sets a higher minimum age for consenting to the processing of your data. If you're under 18, you should have a parent or guardian's permission. We don't knowingly collect information from anyone below the applicable age; if you believe a child has given us personal information, email us and we'll delete it. Note that third-party services you can connect to Kollekta (like Discogs) set their own age rules under their own terms.

12. Changes to this policy

If we change this policy we'll update the version and date at the top. Routine changes take effect when we post the updated policy. For material changes — particularly before we introduce any analytics or advertising technology — we'll tell you by email or in the app, and where consent is required we'll ask for it before anything loads.

13. Contact

• Privacy, legal, copyright / takedown, security reports — legal@fnrblr.com
• General and support — help@kollekta.app
• Post — FNRBLR, Workit Spaces, Unit A1/35–39 Bourke Road, Alexandria NSW 2015

Kollekta is a product of FNRBLR. Album and artist data from MusicBrainz and Discogs. Kollekta is not affiliated with, sponsored or endorsed by MusicBrainz or the MetaBrainz Foundation. This application uses Discogs' API but is not affiliated with, sponsored or endorsed by Discogs. 'Discogs' is a trademark of Zink Media, LLC.