Privacy policy

Controller

Hilmar Saller
Straßlacher Str. 4
81479 München
Deutschland

Contact for privacy enquiries: datenschutz@myccu-app.de

Basic principle

MyCCU is designed for local use with your own Homematic CCU3/OpenCCU. The app connects directly to the hub configured by the user through the XML-API add-on.

Data stored locally

The app can store the following data locally on the device:

• IP address or hostname of the CCU3/OpenCCU
• XML-API token
• favourites and display settings
• tile rules
• backup/import settings
• weather configuration, if enabled

XML-API token

The XML-API token is required to communicate with the CCU3/OpenCCU. It is masked in the app and is not exported in backups. The token should not be shared in screenshots, support emails or public posts.

Network access

MyCCU uses network access to reach the CCU3/OpenCCU configured by the user. Depending on the configuration, the local CCU connection may be unencrypted within the local network.

Weather data and coordinates

The weather feature is optional. MyCCU does not request GPS or device-location permission and does not determine the current location automatically. When weather is enabled, or when the user starts a weather test, latitude and longitude or a weather URL can be entered manually. The current default provider is Open-Meteo; the entered coordinates are sent to Open-Meteo over HTTPS for the weather request. Custom weather URLs and their redirects must also use HTTPS.

Google Play and subscriptions

Subscriptions are offered and managed exclusively through Google Play. Google processes the Google Play account used, purchase and payment information, and subscription status under Google’s privacy terms. MyCCU receives technical product and purchase information from Google Play to display available offers and restore subscription status. Payment data such as complete credit-card or bank details is not sent to MyCCU.

To verify entitlement securely, the app sends the purchase token supplied by Google Play and the product ID over HTTPS to MyCCU’s own verification service hosted through Cloudflare. The service checks subscription status through the Google Play Developer API. The CCU address, XML-API token, and device, room, program or weather data are not sent. The raw purchase token is not stored persistently. A non-reversible SHA-256 verification key may be stored together with product ID, status, expiry, the latest order ID supplied by Google, and the check time.

A pending or not yet trustworthily verified purchase does not automatically unlock paid functionality. Demo mode remains available without a subscription.

Support ID and temporary support access

MyCCU creates a random support/installation ID and stores it locally in an app directory excluded from Android backup. Over HTTPS, the app checks whether temporary EXPERT/DEVELOPER diagnostic access is available for this installation. This check may run automatically when the app starts, when it returns to the foreground and approximately once per minute while the app is active.

Only the Support ID is sent to the MyCCU support service. The CCU address, XML-API token, SID, device information, diagnostic report and billing data are not included. The Support ID is not a MyCCU user account and contains neither a name nor an email address. A grant does not enable a diagnostic level automatically; the user selects it in the app. Support grants last no longer than seven days, expire automatically and can be revoked earlier.

Backup and import

A manual JSON export contains no access tokens, SID, purchase tokens or Support ID. It may, however, contain private configuration details such as the local CCU address, weather coordinates, custom names and assignments, and parts of the smart-home configuration. Backup files should therefore be treated as private configuration files and should not be shared publicly by mistake.

Diagnostic report

A diagnostic report is created only when requested by the user and is not sent to MyCCU automatically. In particular, EXPERT/DEVELOPER reports may contain custom device, favourite, channel or tile names and technical IDs. Common access-token patterns are filtered. The user decides whether to share the report and should review it beforehand where appropriate.

No advertising / no tracking

MyCCU currently contains no advertising, user tracking or analytics SDKs. MyCCU has no user-account system.

Email support and retention

When users request support, they may voluntarily send information such as their email address, app version, error description, screenshots or diagnostic reports. This information is used solely to handle the support request. Support emails and diagnostic reports submitted voluntarily are generally deleted 90 days after a support case is closed. Exceptions apply where required by law or where a longer period is justified and specifically documented. Retention of Cloudflare access and platform logs also depends on the product and account configuration in use.

Request data deletion

Details of the deletion process and how to contact us are available on the MyCCU data deletion page. No user account or sign-in is required.

Hosting / email provider

The website is provided through Cloudflare Pages. Domain-based email addresses may be forwarded to an internal mailbox through Cloudflare Email Routing.