MEERHOF
Privacy Policy
Meerhof is an app for controlling the heating and cooling in your own home through a ComfortClick bOS building controller. This policy explains what the app does with your information.
The short version
- Meerhof has no servers of its own. There is no Meerhof account, no Meerhof database, and nothing is sent to the publisher.
- Your credentials and settings stay on your device.
- The app talks to two places: your building's own controller, and — only when you sign in with an Access ID — ComfortClick's lookup service, to find that controller's address.
- There is no analytics, no advertising, no tracking and no crash reporting. The app contains no third-party SDKs of that kind.
What is stored on your device
All of this is held in the app's private storage, readable only by the app:
| What | Where | Why |
|---|---|---|
| Access ID, username and password | Encrypted storage backed by the Android Keystore | So you are not asked to sign in on every launch |
| Server address and certificate key for your controller | Same encrypted storage | To reconnect, and to verify the controller is the one you paired with |
| Room names, icons and order you have customised | App storage | Your personalisation |
| Appearance settings (theme, colours, frosted panels) | App storage | Your personalisation |
| A background photo you choose | Copied into the app's private files | So the backdrop survives the original leaving your gallery |
| Recent error messages (most recent 30) | Memory only, never written to disk | Diagnostics while the app is running; cleared when the app closes |
Live readings — temperatures, setpoints, window contacts, unit status — are held in memory while the app runs. They are not written to disk and not sent anywhere except back to your own controller when you change something.
What is sent, and to whom
1. Your building's controller
The app connects directly to the ComfortClick bOS controller for your building over an encrypted (HTTPS/TLS) connection, and sends:
- your username and password, to sign in;
- the changes you make — a setpoint, a fan speed, a cooling permission.
This is a direct connection between your device and that controller. Where the controller is, who operates it, and what it records are decided by whoever runs your building's system, not by this app. If the controller is on your local network, the connection does not leave it.
2. ComfortClick's Access ID lookup
If you sign in with an Access ID, the app asks ComfortClick where your controller is, with a single request:
GET https://www.comfortclick.com/api/bosclient/GetServerAddresses?accessId=<your Access ID>
Only the Access ID is sent. Your username and password are never sent to ComfortClick. The reply is your controller's local and public addresses and its public key. ComfortClick is an independent company and its handling of that request is governed by its own privacy policy.
You can avoid this request entirely by signing in with your controller's address instead of an Access ID, using the “Server address” option on the sign-in screen.
3. Nothing else
No other network destination exists in the app. Nothing is sent to the publisher, to an analytics provider, to an advertiser, or to a crash-reporting service.
Photos
If you choose your own background image, the app opens the Android system photo picker. The app does not request access to your photo library — the picker hands back only the single image you select. That image is decoded, scaled down and copied into the app's private storage, and is only ever drawn behind the app's own screens. It is never uploaded.
Demo mode
Signing in with the demo credentials runs the app against a simulated building inside the app itself. In demo mode the app makes no network requests at all, and the rooms, readings and history you see are generated on the device.
Permissions
| Permission | Why |
|---|---|
INTERNET |
To reach your building's controller and, for Access ID sign-in, the lookup service |
ACCESS_NETWORK_STATE |
To tell “you are offline” apart from “the controller is not answering” |
The app requests no storage, location, camera, microphone, contacts or identifier permissions.
Security
- Connections to your controller use TLS. The certificate is pinned to the public key published for your Access ID, so the app refuses to connect if a different certificate is presented and tells you why.
- Your password is stored with Android's
EncryptedSharedPreferences, with the key held in the device's hardware-backed Keystore. It is not stored in plain text and is not included in any backup readable by the publisher. - The session token is never written to disk; the app signs in again on a cold start.
Keeping and deleting your data
Nothing is kept by the publisher, so there is nothing for the publisher to delete. On your device:
- Sign out (System → Account → Log out) erases the stored Access ID, username, password and server details immediately.
- Uninstalling the app removes everything it has stored, including your chosen background image and personalisation.
Readings and error messages are held only in memory and are gone when the app closes.
Children
Meerhof is a utility for controlling a home heating system. It is not directed at children and collects no information about anyone, of any age.
Changes to this policy
If this policy changes, the new version will be published at this address and the effective date above updated. Material changes will be noted in the app's release notes.
Contact
Questions about this policy: [email protected]
Questions about what your building's controller records — including who can see your heating history — are for whoever operates that system; this app has no access to it beyond what it displays.