AndrIoT / Security

Where your video goes

The path of live video, recordings and alerts, with what is encrypted, what passes our servers and what we could technically see.

Last updated: 18 November 2026

The short version

  • On Android 5 and newer, live video goes from the phone to your browser and is encrypted between the two. It is direct when the network allows and passes through our relay when it does not.
  • On Android 4.1 to 4.4 (the Legacy app), pictures go through our server. They are encrypted on the way, but not between phone and browser.
  • Nothing is recorded unless you turn recording on. Recordings are deleted after 24 hours, 7 days or 30 days, depending on the plan.
  • AndrIoT is a hosted service. It is not open source and you cannot run the server yourself, so you cannot check these statements in the code. We describe the weak points on this page as well as the strong ones.

Live video on Android 5 and newer

Live video and audio use WebRTC, the same technology as browser video calls.

  • Setting up the connection. The phone and your browser find each other through our server (signalling, over TLS). Our server sees the set-up messages, which include network addresses. It does not receive the video.
  • Direct path first. Both sides try to connect directly. To learn their own public addresses they ask public STUN servers run by Google and Cloudflare; no video goes there.
  • Relay when needed. If no direct path works (some mobile and office networks), the video goes through our own relay servers (TURN) in the European Union. The relay forwards encrypted packets. It cannot read them and does not store them. We do not measure how often the relay is used.
  • Encryption. The stream is encrypted between the phone and the browser (DTLS-SRTP, standard in WebRTC). The two ends agree on their keys through our signalling server, and there is no code for you to compare on both screens. So this is encryption between the two devices, not an end-to-end scheme that you can verify yourself.

Live pictures on Android 4.1 to 4.4

The Legacy app is small and has no WebRTC. It sends still pictures (about 4 a second by default) over its encrypted connection to our server, and the server passes them to your browser.

The pictures are protected by TLS on the way. They are readable on our server and at Cloudflare, which carries the connection to it. They are not stored.

Recordings

  • Clips are recorded only if you turn recording on for a phone.
  • The phone records an MP4 file and uploads it through our server to Cloudflare R2 storage with a European location.
  • Clips are not encrypted with a key that only you hold. Whoever runs the service could technically open them. Our policy is not to look at recordings; the Privacy Policy is the binding text.
  • Clips are deleted when your plan's history period ends: 24 hours on Free, 7 days on Standard, 30 days on Pro. When your storage is full, the oldest clips go first. You can delete any clip yourself, and deleting the account deletes all of them.
  • A link to play a clip is valid for 2 minutes and only for that clip.

Alerts, sensor readings and the activity log

  • Motion detection runs on the phone. No pictures are uploaded to work out whether something moved.
  • Alert texts, sensor readings and the activity log are kept in our database on servers in the European Union, for your plan's history period.
  • If you connect Telegram, a webhook or MQTT, alerts are also sent there. With Telegram, the snapshot of a recorded clip is sent too.

What the dashboard can do on the phone

The dashboard is more than a viewer. For every paired phone it includes a file browser and a terminal that runs commands on the phone, with the rights of the app. There is no switch on the phone to turn these off.

So anyone who can sign in to your AndrIoT account can use them. Use a strong password and turn on two-factor sign-in (Settings in the dashboard). Before you pair an old phone, reset it to factory settings and do not sign in to personal accounts on it.

The app makes outgoing connections only and opens no port on the phone.

Your account

  • Passwords are stored as salted hashes. Two-factor sign-in with an authenticator app is available.
  • The secret that identifies a paired phone is stored as a hash. Saved Telegram, webhook and MQTT secrets are stored encrypted.
  • Removing a phone, changing the password or deleting the account disconnects the live connections that were open.

Other companies involved

Cloudflare carries the traffic to our servers and stores recordings. Stripe handles payments. E-mail is sent through Resend. The website and the dashboard use Google Analytics, and the Android app uses Firebase crash and usage reporting. The support chat sends your chat text to an AI provider to draft answers. Some of these companies process data outside the EU. The Privacy Policy lists them.

What has not been done

  • The service has not had an independent security audit.
  • Old Android versions no longer get security updates, and an app cannot fix that.
  • The Legacy app has not yet been confirmed on real Android 4 phones.

Report a problem

Found a security problem? Write to hello@andriot.net. Privacy requests: privacy@andriot.net.