ElevateMate · Privacy
Your configurations stay under your control.
How ElevateMate uses the local network, protects its library, handles optional iCloud backups and exports configuration files.
At a glance
No developer account. No developer server. No tracking.
- Direct communication with your displays on the local network
- AES-GCM-encrypted library on your Apple device
- Optional encrypted backups in your private iCloud Drive
- No advertising, analytics or tracking SDKs
1. Controller and scope
Controller
Fabian Vocke
Am Autobahnzubringer 1
76709 Kronau
Germany
Email
privacy@mate.build
This policy applies to ElevateMate for iPhone, iPad and Mac. ElevateMate is an independent configuration client for displays on which the separate ShellyElevate project is already installed. It cannot install ShellyElevate and is not part of or affiliated with that project.
Effective: September 25, 2026. The description reflects app version 1.0 and the technical state reviewed on that date.
2. Data processed on the local network
ElevateMate can scan active private IPv4 networks. Networks with more than 254 host addresses are limited to the local /24 range, and addresses are checked on port 8080. Candidate IP addresses are used temporarily to find compatible devices. Before a result is accepted, the app validates that the endpoint identifies itself as ShellyElevate.
When you add or open a display, the app can receive and process its address, device name, model, ShellyElevate version, capabilities, reachability and supported settings. When you save or apply changes, those settings are sent directly to the display. The developer does not route this traffic through a server and cannot read it.
The current ShellyElevate API uses unencrypted HTTP without authentication. Settings, including any credentials returned by or sent to the display, can therefore be visible to other parties with suitable access to the same network. Use ElevateMate only on a trusted local network. The app uses an ephemeral network session and does not intentionally cache these responses.
On supported Apple systems, local-network access is controlled by the operating system. You can change that permission in Privacy & Security settings. Without it, live discovery and device configuration cannot work.
3. Local library and device security
The local library can contain saved display names and addresses, model and version information, last-seen timestamps, configuration backups, reusable templates and their settings. Depending on the configuration, settings may include credentials such as an MQTT password or voice-assistant token.
Before it is written to the app’s Application Support area, the complete library is encrypted on the device using AES-256-GCM. The local encryption key is stored in Apple’s Data Protection Keychain as a device-bound item that is available only after the device has been unlocked. It is not synchronized to another device. Operating-system protection, device access control and your backups remain relevant in addition to this app-level encryption.
The app stores the on/off choice for optional iCloud Backup in system preferences. It does not use that preference for advertising or profiling.
4. Optional iCloud Backup
iCloud Backup is off unless you enable it. When enabled, ElevateMate encrypts a snapshot of the library on your device using AES-256-GCM and writes the encrypted file to iCloud Drive/ElevateMate/Backups. The app retains up to 20 of its backup files and removes older ElevateMate backups as new ones are created.
To restore the encrypted backup on another trusted device, its separate backup key is stored as a synchronizable item in iCloud Keychain. ElevateMate does not receive your Apple Account credentials and the developer cannot access or decrypt your iCloud files or Keychain item.
Apple processes iCloud content and metadata under your Apple Account terms and Apple’s privacy policy. Apple states that iCloud Keychain is always end-to-end encrypted, while the protection of iCloud Drive files depends on whether Standard or Advanced Data Protection is enabled. The ElevateMate backup payload remains additionally encrypted by the app in both cases.
Turning the feature off stops new automatic backups but does not delete existing files from iCloud Drive. You can remove them in Files on iPhone or iPad, or in Finder on Mac.
5. Backups, templates and JSON exports
Device backups and templates remain inside the encrypted library until you delete them. Before each batch change, ElevateMate creates a device backup. Changes are sent only to the compatible displays you select and are read back for verification.
If you export a backup or template as JSON, the exported file is deliberately readable and is not protected by the library encryption. ElevateMate displays an additional warning when the data contains known credentials. The system file or sharing interface sends the file only to the destination you choose. From then on, that destination’s privacy, security and retention terms apply.
6. Demo Mode and external links
Demo Mode uses fixed, fictional devices, addresses, settings and credentials. It does not scan your network, contact hardware or create iCloud backups.
The Settings page contains a link to the independent ShellyElevate project on GitHub. On iPhone and iPad it opens in an in-app Safari view; on Mac it opens in your browser. The site is contacted only after you select the link and is then governed by its operator’s privacy terms. Opening the local device API from a device menu connects directly to that display.
7. Analytics, advertising, accounts and support
ElevateMate contains no advertising, analytics, tracking or crash-reporting SDKs operated by the developer. It does not create a developer account, upload usage profiles or use the device data for automated decisions with legal or similarly significant effects.
If you contact support by email, the controller processes your email address, message content, attachments and the technical metadata needed to answer your request. Do not send passwords, unencrypted configuration exports or other sensitive settings. Support data is deleted when the request has been resolved unless legal retention obligations apply.
8. Retention and deletion
Saved displays, backups and templates remain in the local encrypted library until you delete the relevant item or remove the app and its data. Keychain items and iCloud files may persist independently of an app deletion under Apple’s platform and account behavior.
Removing a display from ElevateMate deletes its saved entry but does not erase the configuration on the Wall Display. Deleting an archive removes that backup or template from the active library. If iCloud Backup is enabled, a later encrypted snapshot reflects the changed library; older rotating snapshots may contain the previous state until they are pruned or you delete them from iCloud Drive.
9. Legal bases, recipients and transfers
Where the GDPR applies, processing required for app features you request is based on Article 6(1)(b) GDPR. Optional local-network permission and iCloud Backup are based on your consent under Article 6(1)(a) GDPR where consent is required. Processing technically necessary for security, reliable operation and answering non-contractual support enquiries is based on Article 6(1)(f) GDPR. Legal retention duties are based on Article 6(1)(c) GDPR.
No app data is disclosed to the developer through an ElevateMate server. Apple is a recipient when you enable iCloud services; a provider you select for a JSON export is a recipient under its own terms. Apple or a chosen provider may process data outside the European Economic Area using the safeguards described in its applicable terms and privacy information.
10. Your rights and changes
Subject to the legal requirements, you have rights of access, rectification, erasure, restriction, data portability and objection. You may withdraw consent with effect for the future and lodge a complaint with a data protection supervisory authority.
The developer cannot directly inspect, change or delete data that exists only on your devices, displays or in your private iCloud. Use the app, the display controls and your Apple Account tools for those copies, and contact the operator of an export destination for data stored there. Your statutory rights and the contact option above remain unaffected.
This policy will be updated if the app’s processing changes materially. The current version is published on this page.