Security and data access

How access to data works: who sees what, how passwords and sign-ins on phones are kept, how DVR video, frames and plans are protected and what happens to card details when you pay.

Account isolation#

• An employee sees only the equipment and data of their own account: cameras, devices, tracks, checkpoints, reports. Pages and records of another account do not open, not even by a direct link.
• The server checks a role’s permissions, not the look of the page: a viewer will not save changes even if they open a form.
• Another account’s equipment cannot be linked to your asset, placed on your floor plan or added to your retranslator.
• All accounts are visible to the service administrators: this is needed to connect equipment, move it between accounts and investigate faults.

Roles in detail: Users and roles.

Passwords and sign-ins#

• The server keeps not the password but its hash: the password itself cannot be recovered from the database. A new password must be at least 8 characters long and not too simple.
• The web app and the apps work only over a secure HTTPS connection.
• Windows stores the password only if Remember password is ticked, and then encrypted by Windows: only this user on this computer can decrypt it.
• Android does not store the password at all. After signing in, the phone gets its own access key for 90 days, which renews itself while the app is in use. My phones lists all the phones signed in under your username, and any of them can be disconnected: its key stops working at once.
• Telegram: the panel is linked to your Telegram account once, with your username and password. After that the server recognises you by Telegram’s signature, and the panel’s key lives for 12 hours and renews itself. Sign out in the panel’s account screen unlinks Telegram.
• An employee disabled by the owner loses their sign-in at once and in all the apps.

Video, frames and files#

• DVR video opens through a signed link issued for one device and one channel for 12 hours. Knowing the terminal number is not enough to open someone else’s video.
• Checkpoint passage frames and floor plans are served only through the web app, after a check that they belong to your account. There are no public links to them.
• There is no video archive on the server: video is shown live and not recorded.
• A camera’s RTSP address, together with its username and password, is visible to every employee of the account in Analytics. Create a separate view-only user on the camera and enter that one in the web app, not the camera’s administrator account.

Secrets in the settings#

• The token of your own Telegram bot and the mail password in Alerts are seen only by the owner and operators; they are not shown to a viewer.
• A retranslator’s password is not shown at all after saving: an empty field when editing means ‘keep the current one’.
• The address for receiving plates from your own ANPR camera contains a secret. If the address has fallen into the wrong hands, press “Change secret” in the checkpoint settings: the old address stops being accepted at once.
• The server does not let retranslator and barrier relay addresses into internal networks: an address such as 192.168.x.x or 10.x.x.x cannot be reached through the web app.

Card payment#

Card details are entered on the payment service’s page and never reach us: the server receives only the payment number and its result. 3-D Secure confirmation takes place on your bank’s side.

How long data is kept#

Tracks are kept for 90 days, camera checks for 30 days, the checkpoint passage log with frames for 90 days (frames of denials for 30 days), and then they are deleted automatically. All the periods are in Plans, limits and retention.

Found a vulnerability#

Write to us via the Contacts page. Please do not publish the details until we have answered and fixed it.

See also

Found a mistake, or didn’t find an answer? Write to us on Telegram or send us a request, and we will reply and fix the article.