Effective date: 29 October 2026 Who we are: Many Library Minus is made by Jack Davidson, an independent developer ("I", "me"). Contact: jack.davidson38@gmail.com
This policy covers the Many Library Minus app on Android, iOS, macOS, Windows and Linux, and its command-line tool.
The app works on your DJ library on your own device and your own USB drive. Your library is not uploaded anywhere as part of normal use.
There are no analytics, no advertising, no tracking, and no crash reporting that sends itself. The app has no install id, device id or advertising id.
There is no Many Library Minus account for paying customers. You prove a subscription with the receipt your store or payment processor already gave you — see Accounts, purchases and proof of ownership.
Data leaves your device in exactly four situations. Three are started by you:
The fourth is automatic, on the computer apps that update themselves (macOS, Windows, and the Linux AppImage): each time the app starts, and when you press Check for updates (on any computer app), it asks my update server whether a newer version exists — see App updates. That request carries nothing about you or your library.
I do not sell your data and I do not share it with anyone for their own purposes. The only other companies that touch it are the infrastructure providers listed under Service providers, who carry it on my behalf.
This is the one place the app can send me a meaningful amount of your data, so it is described in full.
A bug report is sent only when you press Bug report (which packs a report file on your device) and then press Send report. If the app hits an error it may save a small interaction trace on your device so that a later report is more useful; that file stays on your device unless you send a report yourself.
A report is a single compressed file of at most 15 MB. It can contain:
masterDbId), its file path, the file size
it records and the analysis file it names). For the tracks sharing the title of a file an error
names, it also includes the files those rows name: each audio file's beginning, up to 2 MB as
below, and each row's three analysis files. Together with the files an error names, only files on
the drive itself are included, at most 64 of them.A report made where no drive is open (for example when the app fails on its list of drives or in Setup) holds no library databases and no files from a drive. It still holds the device and app information, the trace of recent activity, folder paths on this device (including the names of its offline copies), the output of the commands the app ran since it was opened (which can include track titles, artists and file paths from a drive or copy you opened earlier), your SoundCloud username if SoundCloud is connected, and, when you send it, the email and note you typed and the tester token described above.
If a report cannot be sent from the app and it is kept in the app's own storage on a phone, the app offers Write the email: it opens your own email app with a draft addressed to me, naming the report's file, the folder on your device where it is kept, and why it could not be sent. The app sends nothing itself; only what you choose to send from your email app reaches me, and it is handled and kept like a report.
A report never contains your SoundCloud access or refresh tokens, or any password. The app redacts URLs and credentials from its own activity trace before it is packed.
I do not use bug reports for marketing, profiling, advertising, or training machine-learning models.
Only me. Reports are not sold, published, or passed to any other person or company for their own use. To reach me, a report travels through the two service providers described below.
Reports are delivered to my email inbox and are deleted within 12 months of receipt. You can ask me to delete a report you sent at any time — see Your choices and rights.
The copy of the report on your own drive and device stays there until you delete it.
Connecting SoundCloud is optional.
You can disconnect SoundCloud in the app at any time, which deletes the tokens from your device, and you can revoke the app's access in your SoundCloud account settings.
The following never leaves your device unless you include it in a bug report: your library and any
offline copies of a drive you make in the app, app settings, SoundCloud tokens, logs, backups, and
performance timings. Removing the app (and deleting the .many-library-minus folder on a drive)
removes them.
Before the app changes a library on your drive it writes a backup of the affected library files to
the .many-library-minus folder on that same drive, so a change can be undone. Backups hold the
same library data as the originals. They stay on your drive, are never uploaded, and are yours to
delete. Anyone you hand the drive to can read them, exactly as they can read the library itself.
On Android the app asks for access to files on external storage. It uses this only to read and write the DJ library and music files on the USB drive or folder you choose.
The macOS and Windows apps and the Linux AppImage check for a newer version each time they start,
and again when you press Check for updates in Setup. A Linux app installed from a .deb or
.rpm package checks only when you press Check for updates. The check is a plain web request to
my update server (hosted by Cloudflare) for a small file listing the newest version. Like any web
request it reveals your IP address; it also names the update library it was made by, and it
carries a fixed code built into the app that lets the server answer only copies of this app (the
same code in every copy of the same build: it identifies the app, not you). The address asked for is the
same for every copy of the app on the same update channel (every copy uses the public channel,
except test copies I or a tester deliberately switch to the test channel), so the check does not say
which version, operating system or processor you have, and it carries no account, no device id and
no library data. Downloading an
update or an installer does reveal which operating system and processor type it is for (the
file's name says so).
If an update is available, nothing is downloaded until you press Install and restart; then the
app downloads the new version from the same server, checks its digital signature, installs it and
restarts. It never installs or restarts on its own. A .deb/.rpm copy instead saves the checked
package into your Downloads folder for you to install. There is no public download page: the
update server answers nothing to anyone but the app, except the speech model files (below) and a personal download link I send a tester
(valid for at most 7 days): opening it downloads the installer from the same Cloudflare-hosted server,
which, like any web request, reveals your IP address and your browser's user agent to Cloudflare. The iOS and Android apps do not check: their
stores update them.
On a Mac, the Lyrics screen's Download the speech model button (or the command
many-library-minus lyrics model install) downloads the speech model that listens for lyrics, about
78 MB, from the same Cloudflare-hosted update server, only when you ask for it. Like any web request
it reveals your IP address and the name of the program that asked; it carries no app code, no
account, no device id and no library data, and the model then runs on your computer: nothing it
hears is sent anywhere.
The update server stores nothing about you; its only trace is the request log described under Server logs and IP addresses.
When the app (or anyone else) contacts my update server, the request is logged — time, path, status, IP address and the name of the program that asked — in Cloudflare's request log for my account. Cloudflare deletes those logs after its own retention period; I do not copy them anywhere, and the update server keeps no counters and no other records.
When the app contacts my sign-in, bug-report and subscription service, the service:
These companies process data on my behalf, solely to run the service:
| Provider | What it does | What it handles |
|---|---|---|
| Cloudflare | Hosts the sign-in, bug-report and subscription service and stores its records; hosts the app update server | Requests in transit, IP address, short-lived rate-limit counters, request logs, licence keys, account records; for update checks and downloads (the speech model download included), the IP address, request logs, and (for a download) which platform's file was fetched |
| GitHub | Stores the synthetic Test Mode library my service downloads for reviewers | Nothing about you — my service fetches it with my own credential |
| Google (Gmail) | Delivers and stores bug reports in my inbox, and sends the licence-key email | Bug report files, your note, your email address if given; a licence key and the email address on your Stripe customer record |
| Stripe | Takes payment on the web (macOS, Windows, Linux) and runs the page where you cancel or change your card | Your payment details, name, email and billing country — handled by Stripe. I can see your name, email and billing country in my Stripe account and use them only for billing and support; my service itself reads the subscription identifier, its status and renewal date, and — to send a lost licence key or open the manage page — your Stripe customer id and email |
| Google Play | Takes payment inside the Android app, and tells my service whether a subscription is live | The purchase token your device holds, and the app's package name. Play tells me the subscription's state and expiry, and nothing about you |
| Apple (App Store) | Takes payment inside the iOS and Mac App Store app, and tells my service whether a subscription is live | The original transaction identifier your device holds. Apple tells me the subscription's status and renewal date, and nothing about you |
All connections are encrypted in transit (HTTPS/TLS). Reports are not end-to-end encrypted; they are stored in my mailbox under Google's standard protections.
There is no Many Library Minus login for paying customers, and no password for you to remember. You subscribe through a store or payment processor, and your device keeps the receipt that purchase gave it. To check the subscription, the app sends that receipt — and nothing else about you — to my service, which asks the processor whether it is paid and sends back a short signed permission slip the app stores until it next checks.
Payments. Payment is handled by the store or processor you buy through: Google Play in the Android app, the Apple App Store on iOS and macOS, and Stripe for downloads from my site. No card, bank or billing detail ever reaches me or my service. Stripe's payment page offers cards and the wallets Stripe supports (Apple Pay, Google Pay, Link and, where enabled, PayPal); what you type there goes to Stripe, under Stripe's own privacy policy. Each processor is listed in Service providers.
What is sent, and what I keep. The receipt is a Play purchase token, an App Store transaction identifier, or a licence key of mine — an identifier for the purchase, never a name, an address or a card number. My service stores, in Cloudflare:
I do not store your purchase token or transaction identifier; they are checked with the processor and discarded. The signed permission slip is kept on your device, not by me. Licence-key mappings are kept while the subscription may still be used; account records until the account is removed.
Manual accounts. There is one username-and-password sign-in, the "Comped & Test Login" button on the activation screen, used only for app-store reviewers, for free accounts I hand out personally, and for test accounts I use to test the app myself. Such an account holds a username, a password stored only as a salted PBKDF2 hash (I cannot read your password back), whether it is enabled, when it expires, and a short note I write for myself. No email address is required and none is collected. Changing or deleting the account signs every device out immediately.
Test Mode. A reviewer or test account can download a synthetic test library I built (a test account may instead unpack one built into the app, which sends nothing). It contains no real DJ's music, titles or files. The download is fetched by my service from my own private code repository at GitHub, using my credential and not yours: nothing identifying you or your device is sent to GitHub.
If you lose your licence key. You can ask the app to email it to you. I look your address up against the customer records Stripe holds and send the key to the address on that record — never to the address typed into the app — so the feature cannot be used to send mail to anyone else, and it answers the same way whether or not it found a customer, so it cannot be used to find out who subscribes. The email is sent from my Gmail account (see Service providers) and contains the licence key and nothing else. I keep a count of the emails actually sent, against a keyed hash of the address (an HMAC under a secret only my service holds, so the count cannot be matched back to an address by anyone who sees it) rather than the address itself, for up to 48 hours, to cap them at five a day.
Your rights here. You can ask me to delete a licence-key mapping or a manual account by emailing jack.davidson38@gmail.com. Cancelling or refunding a subscription is done with the processor you bought it from — Stripe's cancel page is reachable from inside the app, and Google and Apple manage their own subscriptions in their stores.
The app is not directed at children under 13 (or the equivalent minimum age where you live), and I do not knowingly collect their data.
Because my providers operate globally, your data may be processed outside your country.
If this policy changes, the new version will be posted at this address with a new effective date. Material changes — in particular anything that adds a new kind of data collection — will also be noted in the app's release notes.