Privacy policy
1. In short
Crypto Masternode Monitor (“the application”) is a mobile app for monitoring masternodes on the blockchain networks it supports. That list grows with each release; the networks available in the version you installed are shown in the app, under Settings → Networks.
- No personal data is collected by the publisher.
- No account is required. No sign-up, no user identifier.
- No tracking, no advertising, no analytics, no third-party audience-measurement SDK.
- No server belongs to the publisher: the app runs entirely on your device and queries the public APIs of the blockchain networks directly (and the GitHub API for updates).
- All your data stays on your device, unless you turn on Google Drive sync — in which case your node list is also stored in your own Google Drive (section 8). Sync is optional and off by default.
2. Data processed and where it is stored
The app stores locally, on your device only, the data you enter for it to work:
| Data | Nature | Where | Sent? |
|---|---|---|---|
| Monitored nodes | Public masternode identifiers (public key, proTxHash or collateral outpoint, depending on the network) and labels you choose | Local app storage (AsyncStorage) | No — only the public identifier is used to query the relevant network API |
| Settings | Display preferences, alert thresholds, theme, language, endpoint URLs | Local app storage | No |
| RPC access credentials (optional) | Username / password of an RPC node you provide, for the networks that require one | System secure vault (Android Keystore / iOS Keychain), one service per network | Only to the RPC endpoint you configured, to authenticate to it — never anywhere else |
This data is never sent to the publisher or to any third party other than the APIs described in section 4. Networks whose public API works without authentication have no RPC credentials to enter.
3. What the app never does
- It never asks for, enters, stores or displays the private key of a masternode (
masternodeprivkey,genkey, operator BLS key, WIF key). If you paste a string that looks like a private key, it is rejected with a warning and never saved. - It does not read your contacts, location, files or calendar. It learns your identity only if you connect a Google account for sync, and then keeps nothing but the address (section 8).
- It contains no advertising tracker and no audience-measurement tool.
4. Outgoing network connections
To show the status of your masternodes, the app makes requests to the APIs of the blockchain networks you monitor:
- when a network has an official public source (the project's explorer or API), the app ships preconfigured with it;
- otherwise, it queries only the node you provide yourself: the endpoint stays empty until you fill it in, and no third-party service is used by default;
- in every case, you can replace the address with one of your own choosing.
The exact address queried for each network is shown in the app, under Settings → Networks. That list is what counts, including after a new network is added: it describes the version you actually have installed.
In addition, if you enable new-release notifications, the app queries the GitHub API (api.github.com) at most once a day per network to detect a daemon update.
As with any Internet request, these third-party servers receive your IP address and may log it according to their own policies, over which the publisher has no control. Requests contain only the public identifier of the queried node; no personal data is added.
Technical note: some networks publish their masternodes API over cleartext HTTP only, with no HTTPS version available — that is currently the case for Beldex. The app allows cleartext traffic for those specific domains and for no other; any endpoint you add yourself should use HTTPS.
The contact form (Settings → Docs & support) makes no network request of its own: the app prepares a message and hands it to your own mail app, which sends it under your control. The optional technical block, shown before sending, contains only the app version, the operating system and the interface language — no node identifier, no endpoint address, no password.
5. Camera
Camera access is used exclusively to scan a masternode QR code when adding one. The image is neither saved nor transmitted; it is analysed in memory then discarded. Permission is requested on first use and can be revoked at any time in the system settings.
6. Clipboard
The app can copy a public node identifier to the clipboard (at your request, via a button) and paste an identifier you have placed there. It never reads the clipboard automatically and never transmits its contents to anyone.
7. File backup and restore
You can export your list of nodes (and, if you tick the box, your settings) to a .json file, then restore it later. This file is created and read only at your request: export goes through the system share sheet (you choose the destination), import through the system file picker (you choose the file).
This file never contains your RPC passwords (they stay in the system secure vault and never leave it). Only data that is already local appears in it: public node identifiers, labels, settings and endpoint URLs. You are responsible for where you store this file.
8. Google Drive sync (optional)
The app can keep the list of masternodes you monitor in sync across your devices, through your Google Drive account. This feature is off by default: as long as you do not connect an account, the app sends no request to Google and asks for no permission.
Where the data lives. The file is written to the hidden, app-reserved folder
(appDataFolder) of your own Google Drive. It is invisible in the Drive interface and unreachable by
other apps. The publisher has no access to it and still owns no server: the data goes from your
device to your Drive, with nothing in between.
What is synced. Only what you entered: the network, the masternode's public identifier, the name you gave it, and whether its alerts are on. If you tick the matching option, your settings are included too (language, theme, thresholds, data-source URLs).
What is never synced. Your RPC credentials — they stay in each device's secure storage and must be re-entered on a new device. Neither observed statuses, nor incident history, nor notification counters ever leave the device.
Permissions requested. Only one concerns your Drive data, and it is the narrowest available:
drive.appdata. It grants access to neither your files, nor the list of your files, nor anything other
than what the app wrote itself. Google's consent screen adds the account identity to it (last name,
first name, e-mail address, picture): this is a requirement of the official Google sign-in component, which cannot
do without it, not a request from the app.
What the app keeps of it. Your e-mail address only, and only to show which account is connected on your device. The last name, first name, picture and account identifier are discarded on receipt and never stored. The address itself is written neither into your settings, nor into the backup file, nor into Drive: it disappears when you sign out. None of this reaches the publisher, who has no server to receive it.
How to stop. In Settings → Backup, "sign out" stops syncing and leaves the file in your Drive; "sign out and delete" erases the file and revokes the app's access. You can also revoke it at any time from your Google account.
Google acts here as your storage provider, under its own terms and privacy policy.
9. Notifications
Notifications are local: generated by your device when a node changes state (for example becomes unavailable or comes back online) or when a new daemon version is released. They pass through no third-party notification server (no FCM/APNs for app content) and contain no personal data.
10. Background processing
The app may periodically check the status of your nodes in the background (under the control of the operating system) to alert you. This uses the same connections as section 4 and collects nothing more.
11. Data sharing
No sharing. The publisher collects no data, therefore sells, rents and transmits none to any third party, for any purpose (including advertising).
12. Retention period
The data listed in section 2 is kept on your device until you delete it (removing a node in the app, clearing the app's data, or uninstalling). Uninstalling also removes the RPC credentials from the secure vault.
13. Your rights (GDPR and equivalent laws)
Since the publisher holds no personal data about you on any server, there is no data to access, rectify, export or erase from it. You retain full control of your local data at all times through the app and your device settings.
For any question about this policy, write to guitapp.dev@proton.me.
14. Children
The app is not intended for children under 13 (or the minimum age applicable in your country) and does not knowingly collect any data about them.
15. Changes
This policy may be updated (new feature, new network, legal changes). The last-updated date appears at the top of the page. Significant changes will be announced in the store release notes.
16. Contact
Guillaume THIERY
guitapp.dev@proton.me
France