LAST UPDATED: September 27, 2026
1. Information We Collect
Account information: The email address, display name and password you provide. We store your password only as a salted hash. A session token is stored on your device to keep you signed in. When you confirm, as you create your account, that you are 16 or older and have read this Policy, we store the date of that confirmation and the version of this Policy it refers to.
Camera & setup data: Your camera’s device ID, the name you give it, and whether it is armed and when that last changed, stored with your account. During setup the App also uses the camera’s local IP address and the Wi-Fi network name (SSID) and password you enter; these are sent only to the camera over your local network, not to our servers. The password you choose for the camera is stored on your phone and, encrypted, with your account on our servers, so you can view it and use it on another phone; it is deleted when you remove the camera or delete your account.
QR / pairing scans
Examples: Data read from QR codes you scan with the camera during setup.
Why we collect it: To identify and pair a camera with your account.
Video & images from your camera
Examples: Live video streams, still images, and recordings produced by your camera and routed through the Service. Why we collect it: To deliver live view, recordings, alerts, and recognition features.
Alert rules & settings: The detections, rules, zones and lines you create, including any descriptions you type (for example “a person near the gate”).
Face recognition data: If you use face recognition: the names of the people you add, their photos, the face templates made from them, and the consent records described in Section 3.
Messages to the AI assistant: The text you type to the assistant and its replies. If you enter your own OpenAI API key, it is stored on your device and sent to our servers with each message so the assistant can use it.
Your voice (two-way talk): When you hold to talk, the App records your voice and sends it directly to your camera over your local network. Two-way talk works only when your phone is on the same local network as the camera, and your voice is not sent to our servers.
Push notification token
Examples: A Firebase Cloud Messaging (FCM) registration token associated with your device. Why we collect it: To send you alerts and notifications.
Connection data: Your IP address and details of the requests the App makes, which appear in our server logs.
Disarming a camera
Cameras are armed unless you disarm them in the App. While a camera is disarmed, our servers accept no video from it, so there is no live view of it in the App and no AI alerts for it. The camera keeps trying to connect to our servers, and each attempt is refused. Video the camera is already sending when you disarm it is cut off shortly afterwards. Disarming does not change the camera itself: if it records to an SD card, it keeps recording, and a recording you choose to play back through the App from outside your home network is still relayed through our servers as described above.
Privacy masks
Privacy masks are optional. You can black out parts of the picture, such as a street or a neighbour’s window, in the App under Settings → Cameras → your camera → Privacy masks, while your phone is on the same local network as the camera. The masks are saved on the camera, which blacks those areas out itself, so they are not in the video it sends to our servers or in alert snapshots. To let you draw the masks, the App loads a still picture straight from the camera over your local network; that picture is not sent to our servers.
Location permission
On Android, the App requests location permission because the operating system requires it to scan for and configure nearby Wi-Fi networks during camera setup. We do not collect, store, or transmit your geographic location. The permission is used solely to enable Wi-Fi provisioning.
What we do not do
We do not use third-party advertising networks, and the App contains no advertising or third-party analytics/tracking SDKs. We do not sell your personal data. We do not use your video, images, audio or face data to train AI models.
2. How We Use Your Information
To provide, operate, and maintain the Service (camera setup, live view, playback, AI alerts, notifications).
To authenticate you and keep your account secure.
To provide the optional face recognition feature, if you choose to use it.
To run the AI assistant when you use it.
To send service-related and alert notifications.
To respond to your support and privacy requests.
To detect, prevent, and address fraud, abuse, and security incidents.
To comply with legal obligations.
Our legal bases under the GDPR are: performance of a contract (providing the Service you sign up for), legitimate interests (keeping the Service working and secure, and preventing fraud, in a manner that does not override your rights), legal obligation, and explicit consent (for face recognition, see Section 3).
3. Face Recognition
Face recognition lets the Service tell you when a person you have added is seen by your camera. Facial images and face templates used to recognise people are biometric data, a special category of personal data under Article 9 of the GDPR.
The feature is optional and may be switched off. You decide whether to use it. We may also switch face recognition off for all users. While it is off, no people or face photos can be added and your camera’s video is not checked for faces, but you can still see the people you added before and delete them, in the Faces screen or by asking the AI assistant.
Consent
Your consent. Before you can add people, the App asks the account holder to agree to face recognition. We record the date and the version of the terms agreed to. When the version changes, the App asks again, and no people or face photos can be added until the new version is agreed to.
Each person’s consent. When you add a person, the App asks you to confirm that the person has agreed to be recognised, and you may record how you know them (for example “family member”). A person added before the App asked for this is marked as needing consent, and no photos can be added for them until you confirm it. We record the confirmation, its date and who gave it with that person. Only people whose consent was confirmed can be recognised.
Consent log. We also keep a log of these decisions. Each time you agree to face recognition or withdraw your consent, confirm a person’s consent, delete a person in the Faces screen or through the AI assistant, remove your last camera, or delete your account, we add an entry saying what happened, when, and, where it applies, the version of the terms. Entries are linked to your account’s internal identifier, not your email address, and an entry about a person holds a coded form of the internal identifier we gave that person, never their name. The log contains no names, photos, face templates, descriptions of how you know someone, or email addresses. It is kept when you delete a person, withdraw your consent or delete your account, as a record of the consents and deletions listed above.
Your responsibility. Only add people who have agreed, and only use face recognition on a camera that sees your own private property, never a street, shop or workplace.
What is processed
For the people you add: the name you give them, the photos you upload or take, and a face template (a list of numbers describing the face) made from each photo. When the Service recognises one of them with high confidence, up to 20 more templates taken from your camera’s video may be added to that person’s data, so they can be recognised from more angles.
For everyone else who passes the camera (visitors, neighbours, passers-by): on a camera with an alert that looks for a person you added, the faces in the video are detected and a face template is made from each one so that it can be compared with the people you added. A template that does not match anyone is discarded immediately and not stored. These people can still appear in alert snapshots, which are kept for 14 days (Section 5).
We do not build a collection of unknown faces, and we do not match faces against any list other than the people you added yourself.
Where it is processed
Names, photos and templates of the people you added are stored on our servers, hosted by Hetzner in the European Union. Your camera’s video is analysed, including the face detection described above, on GPU machines we rent through Vast.ai, whose location is not restricted to the European Union (see Sections 4 and 8). Face photos and templates are not placed on these machines, so at present they cannot recognise the people you added. The settings we send to these machines refer to the people you added only by an internal identifier and the date their consent was confirmed; their names and the other consent details (such as how you know them) are not sent. Face photos and templates are never sold, and are not sent to the AI assistant’s provider.
Deleting face data
Delete a person in the App’s Faces screen, or by asking the AI assistant, to delete their name, photos, templates and consent record from our servers. In the Faces screen, if an alert object looks for that person (a Known Face object under Alerts → Objects), the App asks before deleting them; a deletion through the AI assistant has no such check. However the person is deleted, that object is turned off.
Removing a camera. The people you add belong to your account and are used by all of your cameras, so removing a camera keeps them for your other cameras. Removing your last camera deletes everyone you added (their names, photos, templates and consent records).
Withdraw your consent at any time in the App under Settings → Withdraw face recognition consent, or by emailing privacy@esplora.ai from your account’s email address. We will delete every person you added, on all of your cameras, and your consent record, turn off the alert objects that looked for them, and no people or face photos can be added again until you agree again.
Deleting your account also deletes every person you added (their names, photos and face templates) and your face recognition consent record.
In each case the consent log described above is kept. Deleting people and withdrawing your consent work while face recognition is switched off.
4. How We Share Information
We use the service providers below to run the Service. The table shows what each of them receives:
Hetzner Online GmbH (Germany), servers in the European Union Data: All data the Service stores and routes: account, camera and settings data, alert snapshots, face recognition data, and live video and audio passing through our servers. Purpose: Hosting of our servers.
Vast.ai (United States), and the independent hosts whose GPU machines we rent through its marketplace. The machines may be located outside the European Economic Area. Data: Your camera’s live video, your camera and alert settings, and, if you use face recognition, an internal identifier for each person you added and the date their consent was confirmed (not their names). Face photos and templates are not sent to these machines. While face recognition is switched on, when an alert looks for a person you added, the faces in the video are detected on these machines. Alert snapshots are created on these machines and sent to our servers. Purpose: GPU computing that analyses your video for alerts, including detecting faces.
OpenAI (United States) Data: When you use the AI assistant: your messages and the assistant’s replies, and information about your setup that the assistant looks up to answer you, such as the names of your cameras, rules and zones, and, when you ask about past events, your recent alert history (the time, rule name, type, priority and message of each alert). The full name of each person you added to face recognition is replaced with a placeholder (for example “Person 1”) before any of this is sent, and put back in the replies you see. A first or last name on its own, a name written in a different order, a nickname, the name of someone you have not added, and the name of a person you have since deleted are sent as they appear. No camera video, snapshots, face photos or face templates are sent. OpenAI may keep this data for a limited period under its own terms, for example for abuse monitoring. Purpose: To run the AI assistant.
Google LLC (Firebase Cloud Messaging), and Apple’s push notification service on iPhone Data: Your push notification token, the text of each notification (for example the alert name and message), and a link that lets your phone download the alert snapshot for 24 hours. Purpose: To deliver push notifications to your device.
Hostinger, legacy hosting Data: Data you send to the web pages and parts of an older version of the Service that still run there. Purpose: Hosting of legacy web pages and services.
Software development contractors Data: Data on our servers that they can access while building and maintaining the Service. Purpose: Development and operation of the Service.
We may also disclose information where required by law, to enforce our terms, or to protect the rights, safety, and security of our users or the public. We do not sell personal data and do not share it for third-party advertising.
5. Data Retention
We keep personal data only as long as necessary for the purposes described in this Policy:
Account, camera and settings data — until you delete your account.
Alert history, snapshots and alert details — deleted automatically 14 days after the alert, or earlier if you delete your account. A copy of recent alert details in our internal message queue is overwritten as newer alerts arrive, and we also remove your copies from it when you delete your account.
Live video and audio — not recorded on our servers.
Recordings — stored on your camera’s SD card, not on our servers. You can erase them by formatting the SD card from the App.
Face recognition data — until you delete the person, remove your last camera, withdraw your consent or delete your account (Section 3).
Consent log (Section 3) — kept after you delete a person, withdraw your consent or delete your account. It contains no names, photos, face templates or email addresses.
AI assistant messages — we don’t keep a history of your conversations in your account; the App keeps a conversation only until it is closed. Our server logs can record the actions the assistant takes for you (for example a rule it created). OpenAI’s retention is described in Section 4.
Push tokens — until you delete your account, or until Firebase tells us the token is no longer valid (for example after you uninstall the App).
Usage counters and limits (how much AI processing your cameras used, and the limit that applies) — expire automatically, counters within 35 days and limits within 90 days.
Server logs — capped in size and overwritten by newer entries.
Emails to
privacy@esplora.ai— for as long as needed to handle your request.
6. Your Rights & How to Delete Your Data
If you are in the European Economic Area or the United Kingdom, you have the right to access, rectify, erase, restrict, and port your personal data, to object to certain processing, and to withdraw consent at any time. You also have the right to lodge a complaint with a supervisory authority — in Italy, the Garante per la protezione dei dati personali.
Account and data deletion: You can permanently delete your account directly in the App via Settings → Delete account. You can also request deletion by emailing privacy@esplora.ai; we will respond within the timeframe required by applicable law. What is deleted, and what may remain, is listed on our account deletion page.
Face recognition: you can delete individual people in the App’s Faces screen, and you can withdraw your consent at any time in the App’s Settings or by emailing privacy@esplora.ai, which deletes everyone you added (Section 3).
Requests by email: we carry out deletion requests and withdrawals of consent that you send by email with an internal tool that uses the same deletion steps as the App.
If you are not an Esplora user — for example a visitor, neighbour or passer-by who may have been filmed by an Esplora camera, or a person added to someone’s face recognition — you can also exercise your rights by emailingprivacy@esplora.ai. Please tell us where and when you think you were filmed, so we can find the data.
7. Security
We use technical and organizational measures to protect your information. Communication between the App and our cloud Service uses HTTPS/TLS, and live video delivered to the App is encrypted. Your camera currently uploads its video to our servers over RTMP, which is not encrypted; we are working with the camera manufacturer to encrypt this connection and will update this Policy when it is. Communication between the App and a camera on your local network uses the camera’s own local interface, which is not encrypted. Setting up a camera in the App includes replacing its factory password, which is the same on every camera, with a password you choose; the App sends that password to the camera over this local interface. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
8. International Transfers
Some of the service providers in Section 4 are located outside the European Economic Area, or may process your data there: OpenAI and Google (United States), Vast.ai (a United States company whose rented GPU machines may be in any country), and Zoho (the privacy mailbox is hosted in India). You can contact us atprivacy@esplora.ai for more information about these transfers.
9. Children
The App is not intended for use by anyone under 16, and you must confirm that you are 16 or older when you create an account. We record the date of that confirmation and the version of this Policy it refers to. If you believe a child under 16 has created an account, please contact us so we can delete it.
10. Changes to This Policy
We may update this Policy from time to time. We will post the updated version here and revise the “Last updated” date above. Material changes will be communicated through the App or by other appropriate means.
11. Contact Us
Esplora — Milan, Italy
Privacy enquiries: privacy@esplora.ai
© 2026 Esplora.