Privacy policy of the Porial Romi Assistant app
Effective date: 21 November 2026. Last updated: 21 November 2026.
1. The app and its publisher
Porial Romi Assistant (Android, package com.porial.romi) is the mobile app of the Porial Romi Assistant home automation server. Users install that server at home (or on a machine of their choice) and run it themselves; this policy calls it “your server”. The app only works with it, at the address you give.
Publisher: Porial. Contact for any question about this policy or your data: contact@porial.com.
In the app: “Privacy policy”, at the bottom of the Settings and of the first screen (before signing in), opens this text in your browser.
2. In short
- The app sends your data only to your server. The publisher runs no server for the app: it receives, sees and keeps none of this data.
- No account with the publisher, no ads, no advertising ID, no usage analytics, no crash reporting, no Firebase. No data is sold or transferred.
- The only exceptions, technical and described in § 5: components provided by Google (the ML Kit library that reads QR codes, Android’s WebView) may send Google information about their own operation.
- The app’s data is neither backed up to your Google account nor transferred to a new phone: the app is left out of Android’s backup (§ 5).
- What your server does with this data (history, automations) is up to the person who runs it: you, or a member of your household.
3. Data processed, purposes and timing
3.1 Signing in to your server
- Your server’s address, the sign-in code read from the QR code your server shows, or a username and password if you choose to sign in with a password. The password is only sent to your server and never stored on the phone.
- Sign-in tokens issued by your server: kept on the phone, encrypted with an Android Keystore key, and sent only to that server’s address.
- Purpose: signing you in to your server and keeping you signed in.
3.2 Phone registration
- A random identifier created when the app is installed (not the IMEI, serial number or an advertising ID), the device name as set in Android, the manufacturer, model, Android version and app version.
- Sent to your server when you sign in, then with each new app version.
- Purpose: creating the “phone” device in your server and addressing your notifications to it.
3.3 Phone sensors (optional)
- Battery level, charging state, charger type, network type (Wi-Fi, mobile, Ethernet; neither the network name nor its address): on by default, each can be turned off in the app’s settings. Screen on or off: off by default.
- Sent only when a value changes: when the app opens, when the charger is plugged in or out, and at most every 15 minutes in the background.
- Purpose: your home’s automations (for example, a reminder to charge the phone).
3.4 Location (optional, off by default)
- Only if you turn on “Location (presence tracking)” in the settings and grant Android’s location permission (precise or approximate, as you choose in Android’s dialog).
- Data: the phone’s last known location (latitude, longitude, accuracy and, when Android provides them, altitude, speed and bearing). The app does not turn on GPS to get it; it sends it when it has changed.
- The app does not ask for background location access. On Android 10 and later, Android therefore only gives it the location while it is in the foreground. On Android 8 and 9, which make no such distinction, the location may also be read during the periodic background updates (at most every 15 minutes).
- Purpose: knowing whether you are at home (presence tracking) and running the automations that depend on it, on your server.
- To stop: untick “Location” in the app or remove the permission in Android’s settings.
3.5 Notifications
- To receive your home’s notifications without any third-party notification service, the app keeps a connection open to your server, shown by a quiet “Persistent connection” notification (an Android foreground service). Settings → “Receive notifications” stops it.
- Received from your server: each notification’s title, text, picture and buttons. A picture is downloaded from the address the notification gives: your server, or another website if one of your automations names one (that website then sees the phone’s IP address).
- Sent to your server: the button tapped in a notification (action, notification identifier).
- Android 13 and later: the app asks for permission to show notifications.
3.6 Your server’s interface
- The app shows your server’s pages in an Android web view (WebView). What you do there (dashboards, commands, settings) goes to your server, as from a browser.
- Cached files, local storage and cookies of these pages stay on the phone. Links to other websites open in your browser. Depending on your server’s configuration, some pages may load content from other websites (map tiles, for example).
- Pages cannot reach the camera, microphone or location through this web view: the app grants them none of these permissions.
3.7 Android Auto
- The favourite entities you choose (list kept on the phone), their states read from your server and the commands you run (a tap toggles or runs an entity).
- The display in the car goes through Android Auto, as for any Android Auto app.
3.8 Phone backup (optional)
- Inactive until you add it (Settings → “Phone backup”, QR code shown by your server).
- As you choose: your photos and videos (with their metadata, including the GPS location recorded in photos), or the files of a folder you pick in Android’s folder picker; their names, sizes, dates and fingerprints. In two-way mode, the app also receives files from your server and writes them into that folder.
- Sent only to your server, over a channel end-to-end encrypted between the phone and your server (Noise protocol: X25519 and ML-KEM-768, ChaCha20-Poly1305), even when the server’s address is http://. The files are then stored on your server, in the folder chosen by its administrator.
- When: once a day, when a photo or video appears, when the app opens, or on “Back up now”, under the network and battery conditions you set.
- The channel’s key is kept on the phone, encrypted with an Android Keystore key that cannot leave it; like all of the app’s data, it is never copied by Android’s backup (§ 5).
- Purpose: backing up your files to your own server.
3.9 Camera
- The camera is used only to read your server’s QR codes (sign-in, phone backup). The image is analysed on the phone and is neither stored nor sent.
3.10 Settings and other data kept on the phone
- The app’s settings (chosen sensors, favourites, wall tablet mode…), the last values sent to your server (so that only changes are sent), the phone backup’s local index.
- The app contains no crash reporting or analytics tool: an error is shown on screen and sent to no one.
- The version installed from Google Play downloads no app: its updates come from Google Play.
4. Data sharing
No data is shared with third parties, sold or used for advertising. The only recipient of the data described in § 3 is your server, chosen and run by you. § 5 describes what Google components send to Google themselves.
5. Components provided by Google
- ML Kit (QR code reading, model bundled in the app). According to Google’s documentation (“ML Kit data disclosure”, https://developers.google.com/ml-kit/android-data-disclosure), ML Kit sends Google information about its own operation: device information (manufacturer, model, OS version), app information (package name, version), a per-installation identifier, performance metrics (processing time), the configuration used (image format and resolution), event types and error codes. Purpose: diagnostics and usage analytics of ML Kit by Google. This data is encrypted in transit (HTTPS) and, according to Google, not transferred to third parties. Neither the camera image nor the QR code’s content is part of it.
- Android WebView (a system component updated by Google). By default, Android checks the addresses opened in a web view with the Google Safe Browsing service. The app, however, turns off the sending of its web view’s diagnostics and usage data to Google (Android’s MetricsOptOut setting): it sends none, even if you agreed to share such data in Android’s settings.
- Android backup: the app is left out of it. Neither your phone’s backup to your Google account nor the transfer to a new phone copies its data (settings, installation identifier, sign-in tokens, phone backup key, last values sent). On a new phone the app starts afresh: you sign it in to your server again.
- Google Play (installation, updates) and Android Auto are Google services, under Google’s own policy: https://policies.google.com/privacy.
The app’s other libraries (Jetpack, CameraX, WorkManager, Compose, Ktor, OkHttp, Kotlin, BouncyCastle) run on the phone and send nothing to their authors.
6. Android permissions
| Permission | Why | When |
|---|---|---|
| Internet, network state | reaching your server; reconnecting when the network comes back | always |
| Camera | reading your server’s QR codes | the first time a QR code is read |
| Precise and approximate location (foreground only) | presence tracking | only if you turn on “Location” |
| Notifications | showing your home’s notifications | after signing in (Android 13 and later) |
| Foreground service (special use), start at boot, wake lock | keeping the notification connection; restarting sensors and the wall tablet at boot | while notifications are on |
| Photos and videos (including Android 14’s partial access), storage (Android 12 and earlier), media location | phone backup | only if you add the photo and video backup |
| User-initiated transfers | “Back up now” (Android 14 and later) | when you ask |
The app does not ask for background location, contacts, SMS, microphone, all-files access, the list of installed apps or the advertising ID. The Google Play version installs no app. A backed-up folder is chosen in Android’s picker, which grants access to that folder only.
7. Security
- When your server’s address starts with https://, all exchanges are encrypted (TLS). On the home network you may choose an http:// address: those exchanges are then not encrypted, and the app warns you before connecting and before sending a password there. The phone backup stays end-to-end encrypted in every case.
- Sign-in tokens and the backup key encrypted with Android Keystore keys; password never stored; the app’s data out of reach of other apps (Android sandboxing).
- Pages only receive the app’s tokens when they come from your server’s address.
8. Retention and deletion
- On the phone: the session is erased, and revoked on your server, when you sign out (Settings → “Sign out”); uninstalling the app, or clearing its data in Android’s settings, deletes everything it kept.
- On your server: data is kept according to its settings (history, backups), under its administrator’s control. To delete it: remove the phone from the device list (Settings → Devices), delete the history you want, delete the backed-up files or the phone backup.
- At the publisher: nothing; the publisher holds no data from the app. ML Kit data is kept by Google under its own rules.
- Accounts: the app creates no account. User accounts exist only on your server; its administrator creates and deletes them. If you use a relative’s server, ask them to delete your account and data.
- Deletion requests: write to contact@porial.com with any question; we explain how to delete your data from your server and answer within one month.
9. Your rights
You may ask for access to your data, its correction or erasure, the restriction of its processing, or object to it. As the app’s data is on your server, these rights are exercised with its administrator; for the data Google receives (§ 5), with Google. For any question: contact@porial.com. You may also lodge a complaint with your data protection authority (in France, the CNIL: https://www.cnil.fr).
10. Children
The app is meant for adults who use a home automation server. It is not directed at children and does not knowingly collect any data about them.
11. Changes
Any change is published at this address with its new date. A significant change (new data sent, new recipient) is also announced in the app’s release notes before it applies.
12. Contact
Porial — contact@porial.com
