Mobile MA

Privacy Policy

1. Controller

Sven Hanold Falkenweg 27 89129 Langenau Germany Email: info@hanold.info

2. General information on data processing

This website is predominantly a static information page. No cookies are set and no data is transmitted to advertising networks. All content, including fonts, is served from my own server; no content is loaded from third-party servers. To anonymously count page views, a self-operated, non-personal counting mechanism is used — see section 4 for details. No analysis of user behaviour, no cross-page tracking and no profiling takes place.

3. Hosting

This website is hosted on a virtual server that we rent from STRATO GmbH (Berlin) and operate ourselves; the data centres are located in Germany. STRATO processes data as a processor solely on our behalf; a data processing agreement pursuant to Art. 28 GDPR is in place with STRATO. The data processing agreement is available at strato.de/agb/avv.

When you visit the site, the web server processes the technical information required to deliver it, in particular your IP address. Access is not recorded in log files; this data is only processed for the duration of the connection. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in secure and stable operation).

4. Anonymous page-view counter

To see how often individual pages are viewed, this website counts page views. Only the site name, the requested page path, the language version and the date are processed — aggregated into a daily counter per page. In the same way, the site counts how often the App Store link is clicked (with its placement on the page) and how often the support form is submitted successfully — again only as a daily counter, with no link to a person or to the content of a message.

No IP addresses, cookies, device or browser identifiers, or any other personal data are stored. Individual visits cannot be traced back to a person or device afterwards. The counting runs on infrastructure we operate ourselves; no third parties are involved. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in measuring the reach of our own offering).

5. Support form

You can contact us directly through the form on our support page. The data you enter (name, email address, topic, message and, optionally, an attached file — image or text file) is sent from your browser directly to an automation we operate ourselves (n8n). This creates a support ticket in our internal ticketing system and triggers a notification to us.

For short-term abuse detection (rate limiting), your IP address is stored for a maximum of 5 minutes and then automatically overwritten. In addition, the IP address is contained, together with the form data, in the technical logs of the automation, which are used solely for troubleshooting and are automatically deleted after 7 days; it is not analysed.

To protect against automated abuse (spam bots), the form contains an invisible control field and a self-hosted verification mechanism (ALTCHA). While you fill in the form, your browser solves a small computational task that it has previously fetched from our automation; in addition, the time between loading the page and submitting the form is transmitted. For this check, no cookies are set, no third parties are involved and no characteristics of your device or browser are collected; the required script is served from our own server. When the task is fetched, your IP address is processed only for the duration of the connection for technical reasons and is not stored. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in preventing abuse).

After submitting, you will receive an automatic confirmation with a reference number at the email address you entered; in addition, your request is forwarded by email to our support mailbox. To send and store these emails, we use an email service provider that processes the data as a processor solely on our behalf.

An attached file is stored together with your request in our ticketing system and forwarded by email to our support mailbox. It is not transmitted to the AI service named below. Please do not upload files containing passwords, access credentials or other confidential information.

To answer more quickly, we have a draft reply for support requests prepared by the AI service Claude from Anthropic PBC (USA), which we review and edit ourselves before sending. Transmitted for this purpose are the app, the topic and the message text, but not your name, your email address or an attached file. Email addresses within the message text are removed automatically before transmission. Anthropic processes the data as a processor on the basis of a data processing agreement. The transfer to the USA is safeguarded by the EU standard contractual clauses. The data is not used to train AI models. If the service is unavailable, the draft is created on our own infrastructure. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in the prompt handling of support requests).

The submitted form data is used exclusively to process your request. It is not passed on to any recipients other than those named here. After the request has been dealt with, the data is deleted unless statutory retention obligations apply. The legal basis is Art. 6 (1) (b) GDPR (processing your request) or Art. 6 (1) (f) GDPR (legitimate interest in preventing abuse).

6. The Mobile MA app

Mobile MA is a client for self-hosted Music Assistant servers. The app connects exclusively to the servers you configure yourself. Your music, library and playback data stays entirely between the app and your own server. No third-party analytics, tracking or advertising services are embedded, and no crash reports are sent to third parties. Credentials are stored exclusively locally on your device in the iOS Keychain. The only data transmitted to the developer is the anonymous usage statistics described in full below — which you can switch off at any time.

Anonymous usage statistics (from version 3.2)

To understand how well setup, the free trial and the purchase flow work in the app — and to base improvements and pricing decisions on that — Mobile MA collects a small, fixed set of events from version 3.2 onwards and transmits them TLS-encrypted to a server we operate ourselves in Germany (telemetry.hanold.online). It is exclusively these events; there are no others (as of version 3.9):

  1. First launch of the app after installation
  2. First successful connection to a Music Assistant server
  3. Start of the free trial (with the context of where in the app the trial was started)
  4. Display of the purchase screen (with the context of where in the app it was shown)
  5. Completed purchase of the Unlimited unlock (with the context of where in the app the purchase was triggered)
  6. App opened (days since installation)
  7. Playback started (whether it was the first playback, days since installation — not what is being played)
  8. Result of the automatic server discovery on the local network (found yes/no)
  9. Failed connection attempt (error class and connection type, no server name)
  10. Version of the connected Music Assistant server (version number only, once per change)
  11. Theme selected in Settings (theme name and whether it belongs to Unlimited)
  12. A notice or offer on the app’s Home screen being shown, tapped or dismissed, and “Redeem code” being tapped on the purchase screen (from version 3.7; only the notice’s identifier, e.g. “welcome20”, and the place in the app — not whether or which code was redeemed). Which notices you see is decided by the app on your device; nothing is transmitted for that.
  13. Duration of the connection setup when the app starts (from version 3.9; only the connection type – home network or remote access –, the time in milliseconds and whether the saved connection type failed and the other one took over – no server name, no address)
  14. A “Did you know…” tip being shown in the app (from version 3.9; only the tip’s identifier, e.g. “themes” – which tips you see is decided by the app on your device; nothing is transmitted for that)

Each event technically contains exactly these fields: a randomly generated installation ID (a UUID rolled on first launch — it contains no reference whatsoever to your device, account or person, and is deleted along with the app when you uninstall it), a timestamp, the app version, the coarse operating-system version (e.g. “iOS 26”), the platform (iPhone, iPad, Mac, Apple TV or Apple Watch), and, where applicable, a short context hint (e.g. at which point in the app the purchase screen was shown, or how many days passed between installation and purchase).

What is explicitly not collected and not stored: IP addresses (the receiving endpoint deliberately writes no access log), device or advertising identifiers (no IDFA, no IDFV), the name or address of your Music Assistant server, the contents or size of your music library, your listening behaviour, and any other personal data. The events can neither be linked across devices nor traced back to a person afterwards.

Processing runs entirely on our own infrastructure in Germany (received by a self-operated automation, stored in a self-operated database); no third parties are involved at any point. Evaluation is exclusively aggregated — for example: “How many of the installations from a given month started the trial, and how many of those later purchased?”

You can switch the usage statistics off at any time in the app settings under “Privacy”; transmission then stops immediately. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in improving our own offering). As the data is anonymous, there is no personal reference — we offer the opt-out switch regardless, because it is what we would expect ourselves.

Purchases via the App Store

The app is distributed via the Apple App Store. Any purchases or unlocks within the app are processed exclusively through the App Store; the developer does not receive any payment data, only anonymized, aggregated statistics from Apple. Apple’s privacy policy applies in addition.

Mobile MA for Apple TV

Mobile MA is also available as a standalone app for Apple TV (tvOS). The same principles apply as for the iPhone and iPad app: it connects exclusively to the Music Assistant server you configure yourself, credentials are stored exclusively locally on the Apple TV device, and the anonymous usage statistics described above apply unchanged (the platform is recorded as “Apple TV”; the opt-out switch is available there as well).

To make setup easier, you can hand your server connection details over from your iPhone to the Apple TV app — either by selecting the device from a list, or by entering a temporary six-digit code. This handoff happens directly between your own devices on your local network; no server operated by the developer or any other third party is involved. The code is valid only for the duration of the pairing and does not allow any conclusions to be drawn about your identity.

7. Your rights

You have the right to access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR), data portability (Art. 20 GDPR), and objection (Art. 21 GDPR). You also have the right to lodge a complaint with a data protection supervisory authority; the competent authority is the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg, Germany.

Note on the usage statistics: as the events processed there are anonymous and we cannot attribute them to any person, we are unable to apply access, rectification or erasure requests to individual events (Art. 11 GDPR). The most effective remedy is the opt-out switch in the app.

8. Last updated

September 2026. This policy will be updated as necessary.