ZHome Privacy Policy
Effective date: 18 October 2026 Developer: Maurizio Zucchi, contact: design.dev.pl@gmail.com
ZHome is an app for writing and reading NFC tags (stickers) and for controlling Google Home devices with those tags. This policy explains what data the app handles and where it goes.
1. Summary
- ZHome does not require an account and has no servers of its own.
- The developer does not collect personal data and sells nothing. The only thing that may reach the developer is anonymous crash reports (section 5), which you can turn off.
- The app contains no ads and no tracking.
- Data you enter stays on your phone and on the NFC tags you write it to.
2. Data stored only on your phone
| Data | Purpose | Where |
|---|---|---|
| Saved Wi-Fi networks (network name, security type) | to prepare the next Wi-Fi tag quickly | app storage on the phone |
| Passwords of saved Wi-Fi networks | as above | encrypted system storage (Android Keystore / iOS Keychain) |
| Google Home device list (names, rooms, state) | to show the list instantly | app storage on the phone, for up to 6 months |
| Chosen language | to show the app in your language | app storage on the phone |
You can remove this data by uninstalling the app or clearing its data in system settings. Saved networks can also be deleted inside the app.
3. Data written to NFC tags
A tag only contains what you choose: an action (a Google Home device identifier), Wi-Fi network details (including the password, in plain text) or a list. Anyone who holds a phone near the tag can read this data. Do not put information on tags that you would not share with people who have physical access to them.
The "Lock tag permanently" option makes the tag content impossible to change or erase — including by you.
4. Google Home
If you connect the app to Google Home, ZHome uses the official Google Home APIs:
- sign-in and consent happen in a Google window — ZHome never sees your Google password,
- the app reads your device list and changes device state (on/off, lock/unlock) when you ask it to,
- this data travels between your phone and Google and is processed by Google under the Google Privacy Policy,
- you can revoke access at any time in the Google Home app or at myaccount.google.com/connections.
The developer of ZHome does not receive this data.
5. Crash reports (Firebase Crashlytics)
We use Google's Firebase Crashlytics to collect crash reports. When the app crashes, a report is sent the next time you are online. It contains:
- the error trace (where in the code it happened) and the app state at the moment of the crash,
- device information: model, OS version, app version, language, free memory,
- a random installation identifier (it does not identify you or your phone outside this app),
- basic session information (e.g. how long the app was running) that helps judge how widespread a problem is.
Reports do not contain the content of your tags, Wi-Fi passwords, lists, Google Home device names or any personal data. They are sent over an encrypted connection (HTTPS), are used only to find and fix bugs, and are not used for ads or shared with other companies (other than Google as the service provider). Google keeps crash reports for 90 days. More: Google Privacy Policy and Privacy and Security in Firebase.
You can turn this off: Settings → “Crash reports”. When it is off, the app sends no crash reports.
6. Permissions
- NFC — reading and writing tags.
- Internet — for communicating with Google Home and sending crash reports. NFC tags work offline.
- Vibration — confirming a tag read or write.
7. Children
The app is not directed at children under 13 and does not knowingly collect any personal data from children.
8. Your rights
The developer does not store your personal data — all of it remains under your control on your device. You can turn crash reports off in Settings and ask by e-mail for reports already sent to be deleted. For privacy questions, contact: design.dev.pl@gmail.com.
9. Changes
Changes to this policy will be announced by updating this page and its effective date.