Privacy Policy
How Pipe Home collects, uses and protects your personal data.
Last updated: 2026-04-27
ℹ️ [TO BE UPDATED] This document is a working draft used to launch the website and to prepare for Google / Tuya verification. The final wording will be reviewed by counsel once the operating legal entity is established. Sections marked
[TO BE UPDATED]need that information.
1. Introduction
This document describes how Pipe Home (“we”, “us”, “the service”) collects, uses, stores and shares personal information of users of the Pipe Home mobile application (the “App”) and the related gateways, sensors and switches.
Pipe Home is a product of the mPipe project. The operating entity is: [TO BE UPDATED — company name + registered address + tax ID].
By creating an account and using the service, you confirm that you have read, understood and agreed to this policy.
2. Data we collect
2.1. Account information
- Email — required, used as the login identifier and for OTP verification
- Display name — optional, set by you
- Password — stored as a hash; we never see the original password
- Phone number — optional, used for SMS OTP (planned)
- Profile photo — optional, uploaded by you
If you sign in with a Google account (OAuth), we receive from Google: your email, name and public profile photo. We do not read your Gmail, Drive, Calendar or any scope outside basic identity.
2.2. Device data
When you pair a gateway and IoT devices, we store:
- Device identifiers: MAC address, model, manufacturer, firmware version
- Device telemetry: on/off state, brightness, room temperature, humidity, power consumption — depending on the device type
- Automation rules: scenarios and schedules you create
- Names + groupings: device, room and home names you assign
Telemetry is stored on your gateway first. A subset is synced to our cloud so you can monitor your home remotely and so voice integrations work.
2.3. App usage data
- Diagnostic logs: login sessions, API call timestamps, error codes (no sensitive payloads)
- Push notification tokens (Firebase Cloud Messaging) — to deliver alerts (door sensor, power loss…)
2.4. Data we do not collect
- Precise GPS location — the App does not request location permissions. You enter your city manually for the optional weather feature.
- Contacts, photos, files — the App never accesses your contacts or photo library.
- Advertising — we do not include advertising SDKs, do not track across apps, and do not use IDFA / AAID.
3. How we use the data
| Data | Purpose |
|---|---|
| Email + password | Authentication, account recovery |
| Device telemetry | Display state in the App, evaluate automations |
| Rules | Run automations under conditions you set |
| Push tokens | Send alerts (sensors, gateway errors) |
| Diagnostic logs | Troubleshoot, improve reliability |
We do not use your data for advertising, and we do not sell it to third parties.
4. Sharing with third parties
We share data only in the cases below, and only the minimum needed for each service:
| Third party | Data shared | Purpose |
|---|---|---|
| Self-hosted IoT backend (Pipe Home cloud) | All device data | Storage, sync, command delivery |
| Google (Smart Home Action) | Device names, state, command results | When you link with Google Home for voice control |
| Firebase Cloud Messaging (Google) | Device tokens, notification payload | Push notifications |
| Tuya Cloud (optional) | Tuya account identity, camera commands | When you connect Tuya cameras — only if you opt in |
| Cloud infrastructure provider | All data (encrypted at rest) | Storage, backup, operations — [TO BE UPDATED — provider name when production launches] |
We do not sell your data. We do not share it for advertising, market analytics or data brokerage.
When required by law (court orders, lawful requests from competent authorities), we may have to provide data — limited to the minimum necessary and in compliance with Vietnamese law.
5. Storage and security
- In transit: TLS 1.2+ for all App ↔ Cloud and Gateway ↔ Cloud connections
- At rest: cloud data is encrypted at rest by our infrastructure provider
- Passwords: stored as bcrypt / argon2 hashes; the original password cannot be recovered
- Region: servers located in [TO BE UPDATED — VN / Singapore depending on provider]
6. Retention
| Data type | Retention |
|---|---|
| Active account | Until you delete it |
| Detailed telemetry | 90 days; long-term aggregates are de-identified |
| Diagnostic logs | 30 days |
| Backups | 30 days after account deletion |
When you delete your account, personal data is marked for deletion immediately and physically removed from backups within 30 days.
7. Your rights
Under Vietnam’s Decree 13/2023/NĐ-CP on personal data protection, you have the right to:
- Access — request a copy of the personal data we hold about you
- Correct — ask us to update inaccurate data
- Delete — delete your account and data (see section 8)
- Restrict processing — request that we pause processing in specific situations
- Complain — file a complaint with the competent authority (Authority of Information Security — Ministry of Information and Communications)
To exercise any of these, email legal@mpipe.org. We respond within 30 days.
8. Account deletion
You can delete your account yourself in two ways. See the Delete Account page for step-by-step instructions.
9. Children
The service is not intended for users under 13. We do not knowingly collect data from children. If we discover such data, we delete it. Parents who believe their child has registered should contact legal@mpipe.org.
10. Cameras + video
If you use cameras (via the Tuya integration), please also read the Camera Policy for details on video data flow, storage and encryption.
11. Changes to this policy
We may update this policy over time. For material changes we will:
- Update the “Last updated” date at the top
- Email active accounts
- Show an in-app banner
Continued use of the service after the update means you accept the new version.
12. Contact
Privacy questions:
- Email: legal@mpipe.org
- Legal entity: [TO BE UPDATED]
- Address: [TO BE UPDATED]
Effective date: 2026-04-27