Privacy, without the fine print.

Who’s behind TuneFuse?

I’m Daniel Arden, the maker of TuneFuse. My company, Daniel Arden s.r.o. (IČO 22078495), 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.

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.

Sparkle checks for updates. The update servers see your IP address and request details. You can change automatic checks in settings.

The website

I count page visits and which websites people arrive from, not individual visitors. There are no tracking cookies, and counting is skipped if your browser sends Do Not Track or Global Privacy Control.

The hosting service handles IP addresses and request details. To prevent signup spam, the site uses a scrambled version of your IP address, made with a secret key. This is separate from visitor counts.

The beta list

Three emails: confirmation, the beta download, and the full-release announcement. You join only after confirming. Requesting another confirmation may send another email.

I keep your address and when you signed up and confirmed. Resend sends the emails and handles failed deliveries and unsubscribes. I don’t track email opens or marketing clicks.

Unsubscribe from either announcement, or email hello@tunefuse.app. Joining is optional.

When you contact me

I receive your message, email address, and attachments. The App’s troubleshooting logs stay on your Mac unless you choose to email them. Take a look before sending.

The services I use

Apple handles music and sign-in, Namecheap hosts the website, Resend handles email, and Google Firebase handles crash reports.

These services may handle data outside the European Economic Area; Resend stores it in the US. Protections include EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. I’m happy to explain more if you ask.

Provider privacy information:

• Apple
• Namecheap
• Resend
• Firebase

How long I keep data

Beta list: I delete it from my systems and Resend within seven days of the full-release announcement.

Signup records: links expire after 24 hours. Unconfirmed records are due for deletion seven days later; confirmation records after 90 days. They’re removed when the signup service next handles a request.

Visitor totals: 30 days. Older counts are removed when there’s new activity or I open the dashboard.

Support messages: normally 12 months after I’ve helped resolve the issue. The App removes local troubleshooting logs older than seven days during cleanup.

Resend’s standard delivery logs: 30 days; backups: seven days. Firebase begins deleting crash data and identifiers after 90 days. List deletion doesn’t instantly erase provider logs or backups.

Your rights

I send beta emails with your permission. You can change your mind; that doesn’t undo earlier lawful use.

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 confirmation codes stored as hashes rather than readable codes. 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.