Legal
Privacy policy
The Synapsi account: what we hold, and what we can read of it.
Last updated: 4 September 2026
In short. This policy covers the Synapsi account, which is shared by the apps that have one. What the account holds is sealed on your device before it is sent: we store a byte string and no way to read it. We do not profile you, we do not advertise, and we sell nothing to anybody. What each app does on its own device — cameras, video, crash reports — is in that app's own privacy page, linked from its site.
1. Who processes the data
The controller is Ubiquitous S.r.l., Via Ariosto 25, 00185 Roma, Italia, P.IVA 17584931004. For anything about this policy, write to privacy@synapsi.ai.
2. What an account is
An account is an identity and a sealed blob. The identity is either an email address you chose or the Google account you signed in with; the blob is your settings — for Farview, the list of cameras and their credentials — encrypted on your device with a key we never receive.
What sits on our server, per account, is: the identity, the sealed blob and its version number, the date the account was created, and the sessions currently signed in. A copy of our database is a list of identities and a pile of ciphertext.
The price of that is not negotiable and we would rather write it here than in a support reply: a lost key is an unrecoverable blob. There is no reset that keeps the data, because there is nothing on our side to reset it with.
3. How you sign in
With a passphrase
Your passphrase never reaches us. The app derives two different values from it on your device: one proves who you are to the server, the other unseals your blob and is never sent. Asking whether an address has an account returns the same shape of answer whether it does or not, on purpose: it is not a way to find out who our customers are.
With Google
If you sign in with Google, Google tells us the account's stable identifier, its email address and whether Google has verified it. We key the account on the identifier, never on the address — an address can change hands, an identifier cannot. We ask Google for nothing else: no contacts, no Drive, no profile beyond what the sign-in itself carries. Google's own handling of your sign-in is Google's, and it is governed by its privacy policy.
Signing in with Google gives us an identity, not a key. If the app is one that seals a blob, it still needs your key material, and that is still yours.
4. What crosses our machines, and what does not
Video never passes through a Synapsi server by default. On your own network the app talks to the camera directly; from outside it goes through a relay you run, on your hardware and your bandwidth.
On a plan that includes the tunnel, and only if you switch it on, video does cross a machine of ours. That machine copies bytes between two sockets and reads none of them; with TLS on your relay — which we recommend, and which this is the reason for — what crosses is ciphertext we hold no key to. To enforce the plan's fair use we count how many bytes an account moves in a month. We count the number. We do not record what was watched, when, or from where.
5. What we do not do
- No advertising, no advertising identifiers, no profiling.
- No selling or sharing of personal data with anyone, for any purpose.
- No reading of your sealed blob — not because we choose not to, but because we cannot.
6. Where it is kept, and for how long
The account service runs on servers in the European Union. We keep an account for as long as it exists: there is no archive of deleted accounts, because a sealed blob is of no use to anybody, us included. Deleting the account deletes the blob with it, and it is done from inside the app.
Sessions expire on their own. Server logs, which record that a request happened and not what it carried, are kept for a short operational window and then rotated away.
7. Your rights
Under the GDPR you may ask for access, rectification, erasure, restriction, portability and objection, and you may complain to the Garante per la protezione dei dati personali. Write to privacy@synapsi.ai.
One limit is worth being honest about: we can hand you your sealed blob, but we cannot decrypt it for you. Portability of something only you can read is the file itself.
8. Changes
If this policy changes in a way that matters, the date above changes and the change is announced in the apps' release notes. The previous wording does not govern data collected after the change.