Privacy policy
I don’t sell your personal data, run ads, or build advertising profiles.
I don’t keep a copy of your music library on my servers. Here’s what tunefuse does handle.
This policy covers the tunefuse website and Mac app.
Who’s behind tunefuse?
I’m Daniel Arden, the maker of tunefuse. My company, Daniel Arden s.r.o. (IČO 22078495, VAT ID CZ22078495), is responsible for your data. Its address is Táboritská 880/14, Žižkov, 130 00 Praha 3, Czech Republic. You can reach me at hello@tunefuse.app .
The Mac app
tunefuse keeps library data and caches on your Mac. Searches, playback, and library actions connect to Apple Music under Apple’s privacy policy. When looking up lyrics through LRCLIB, the app sends track metadata such as title, artist, album, and duration to that service.
You sign in with Apple. tunefuse keeps the cookies and credentials needed to stay signed in on your Mac. Your Apple password isn’t sent to my servers.
When the app crashes, Firebase Crashlytics receives technical reports to help me fix bugs. They include what went wrong, app and device details, and IDs for your installation and session. Reports are not completely anonymous, and you can’t turn them off in the app.
Sentry receives diagnostic warning and error records to help me investigate reliability problems. These contain generic event text, severity, timestamp, app version and build, distribution, and code-location or approved diagnostic categories. Raw log messages and details, music metadata or catalog IDs, library contents, email addresses, licence keys, credentials, and artwork are excluded. Technical diagnostic identifiers can still make these records pseudonymous rather than completely anonymous.
Sparkle checks for updates. The update servers see your IP address and request details. You can change automatic checks in settings.
The retired Beta activity collector is no longer used by the new backend. Crash reporting and diagnostic logs are separate.
The website
I count pageviews, broad source categories (such as search, social, email or campaign), and countries in daily aggregates. Only approved campaign labels are retained; arbitrary referrer names and campaign labels are not. Cloudflare derives the country from the connection; my analytics records contain no IP addresses, masked network prefixes, visitor IDs, exact request times, or full URLs. Your browser keeps the UTC day and a short list of visited pages locally to count each page once per day across tabs. These daily flags are replaced on your next visit on a later UTC day; no visitor identifier is created or sent. If storage or tab coordination is unavailable, only ordinary pageviews are counted. Daily unique pageviews are not unique people. There are no analytics cookies or Google Analytics; collection is skipped with Do Not Track or Global Privacy Control.
The hosting service handles IP addresses and request details. To protect the service against misuse, rate limits use short-lived hashes of network addresses made with a secret key. These are separate from visitor counts.
Your browser stores whether the intro has played and your appearance choice. These preferences stay on your device and are not sent as analytics identifiers.
Purchases and licences
For purchases through Paddle, Paddle handles checkout, payment details, taxes, receipts, and refunds as merchant of record. Its privacy policy explains its own processing. I don’t receive your full payment-card details.
My licensing service uses your purchase email, order references, licence status, and registered-installation records to deliver keys, activate up to 2 Macs, recover purchases, and handle refunds or misuse. An installation uses a random identifier and secret stored in Keychain; no hardware serial number is needed.
Resend delivers licence keys, recovery instructions, and related transactional messages on my behalf. It processes the recipient email address, message content (which can include a licence key), and delivery records. These messages are part of providing your licence; they do not enrol you in a newsletter. Open and click tracking are not used for these messages.
I process licence information to provide and support your purchase, meet legal duties, and protect the service against fraud and abuse.
I keep licence and purchase records for as long as needed to manage your licence, resolve disputes, prevent fraud, and meet applicable record-keeping duties. Contact me to ask about access or deletion. I may need to keep some records where the law requires it.
When you contact me
I receive your message, email address, and attachments. Logs you attach to a support request are separate from the app’s automatic diagnostic reporting. Review attachments before sending them.
The services I use
Apple handles music and sign-in, Namecheap hosts the website; Cloudflare hosts the private admin, aggregate website statistics, production licensing, licence records, and app downloads; Paddle handles purchases; and Google Firebase handles crash reports. Sentry handles app diagnostic logs, Resend delivers transactional emails, and LRCLIB provides lyrics lookups.
Sentry diagnostic logs are stored in its EU region in Frankfurt, Germany, along with backups of that diagnostic data. Some Sentry account and organisation metadata may still be stored in the US. Resend stores email data in the United States even when messages are sent from another region. Other providers may also process data outside the European Economic Area under their applicable safeguards, such as EU Standard Contractual Clauses or an applicable adequacy framework.
Provider privacy information:
How long I keep data
Daily pageview, source-category and country aggregates are retained indefinitely. Older records without country information remain Unknown. These aggregates contain no IP addresses or individual request times. Temporary abuse-prevention hashes are scheduled for deletion within seven minutes during normal operation; they are never used to identify visitors in analytics.
Legacy Beta installation, signup and download datasets are retired in the backend migration. Resend contacts and unsubscribe preferences remain in Resend. Production trial and licence records are separate.
Support messages: normally 12 months after I’ve helped resolve the issue. The app removes local troubleshooting logs older than seven days during cleanup.
Firebase begins deleting crash data and identifiers after 90 days. Sentry diagnostic logs and associated backups follow the retention settings for the Sentry project and service. Resend email and delivery-log retention depends on its plan and configured retention; its published standard retention for Free, Pro, and Scale is 30 days, with backup and deletion periods described in its security information. I retain only what is needed to deliver messages, troubleshoot delivery, and meet applicable duties.
Your rights
I process purchase and licence data to provide the software and meet legal obligations. Support, security, and diagnostic processing help me respond to problems and keep tunefuse reliable, based on legitimate interests where applicable. If processing requires your consent, you can withdraw it without affecting earlier lawful processing.
Where applicable, you can ask to access, correct, erase, restrict, or receive a portable copy of your data, and object to processing based on legitimate interests. You may withdraw consent without affecting earlier lawful processing and complain to a data-protection authority, including the Czech Office for Personal Data Protection.
If something seems wrong or you have a privacy concern, email hello@tunefuse.app and I’ll help.
Security and changes
I protect data with encrypted connections, limited access, and safeguards for licence credentials and service records. No system is completely secure. Before using data in new ways, I’ll review the changes, update this page, and let you know or ask permission where needed.