Trust
Security
Arvio's security measures: sign-in, roles, locks and alarm, signed updates, and how to report a vulnerability.
This page lists the measures that exist and work. Arvio holds no security certifications.
Signing in
No passwords
Arvio Home and Arvio Partner have no passwords. You get in with a link or an 8-character code from your email. Each works once and lasts 15 minutes.
A limit on guessing
After 5 wrong codes in 15 minutes, that address accepts no more until the window passes. At most 5 sign-in emails go out every 15 minutes.
One answer for everyone
An address with no account gets the same answer as one with an account. The form never reveals who is a customer.
Sessions
The database keeps only a hash of each session. A device you stop using is signed out within 30 days at most. Signing out ends the session in the cloud too, not just on the device.
Your devices
Under Εγώ → Λογαριασμός → Συσκευές (Me, Account, Devices) you see where your account is open. Sign out any one of them, or all the others at once. Arvio Partner has the same screen.
Who can do what
Limits are enforced on the server, not just hidden on the screen. An action your role does not allow is refused however it is requested.
| Role | What it does | Its limit |
|---|---|---|
| Owner | Everything in the house: people, guests, theme, removing the installer. | The house is theirs. An installer becomes owner only if the owner gives them the role, or in a house that has no owner. |
| Manager | Runs the house and its people. | Cannot change the owner or delete the house. |
| Member | Lights, heating, blinds and music throughout the house. | Cameras, locks and alarm only where they have been given access. Cannot add people. |
| Guest | No account. Only the rooms and the period in their invitation. | No cameras and no alarm. A door only with a PIN, if the invitation includes one. |
| Installer | Sees and configures the house while they hold support access. | Support access does not make them a member or the owner. The owner can remove them. |
| SFK support | Sees the list of accounts and opens a hub's settings when needed. | Each such access is shown to the owner, under «Πρόσβαση από έξω» (Access from outside). |
Locks and alarm
One rule: unlocking, opening and disarming need a person's confirmation, and no command waits around to run later.
- An automation never unlocks, opens a lock or disarms. Arvio Core refuses it and records the refusal in the automation's trace.
- Arvio Core rejects unlock, open and disarm without a confirmation, wherever they come from.
- A security command from Arvio Home lives for 30 seconds at most. If the hub is offline it is refused on the spot. Nothing is queued for when the hub comes back.
- The app does not say a door is locked until the hub answers. If the hub stops answering, it says the state is unknown rather than showing the last one it knew.
- In Arvio Home, locking and arming ask for a yes first.
- The TRU assistant unlocks only for an owner or manager, and only after you answer yes to its question.
- The installer and SFK support cannot unlock or disarm remotely, not through a scenario either.
- A guest opens only the doors in their invitation, with a PIN. Five wrong tries in 15 minutes lock the PIN for 5 minutes, and there is a limit of 20 unlocks an hour.
- On a wall panel, the door opens only within 45 seconds of the doorbell ringing, with two taps, and only from a panel paired with that hub.
- In a 24/7 venue, each booking has its own PIN. We keep only its hash, the check happens locally on the hub, and the installer never sees it.
- After a restart the hub only reads. It sends no commands again, so no lock, alarm or garage door moves because the hub started up.
The hub
One hub, one installation
The QR on the label holds no secret, and a photo of it is not enough. You also need the 6-digit code from the hub's page on the local network, which changes every 5 minutes.
Outbound connection only
The hub opens the connection to SFK's relay itself. You open no ports on your router.
Signed updates
Every update carries an ed25519 signature from SFK, made with a key kept offline. The hub refuses anything unsigned or altered.
No shared login
The Arvio OS image contains no SSH key and no password. A support key is added separately to each hub, by someone holding its disk.
Encrypted backups
Backups are encrypted on the hub for two keys: the owner's and SFK's. The installer has neither.
Clean logs
The hub keeps separate logs for actions, automations, devices, the system and security. PINs, codes, tokens and passwords are removed before a line is written.
Cameras
In Arvio Home, the owner and manager can see camera images. A member sees only the cameras they have been given, and a guest sees none. Arvio Partner does not open images: an installer adds a camera but does not watch it from there.
When you watch live from outside, the video passes through the relay on a ticket that expires, and is not stored.
If you find a vulnerability
Write to hi@arvio.systems, in Greek or English. It is the same contact we publish at arvio.systems/.well-known/security.txt. Tell us what you found, where, and how to reproduce it. Please do not publish it before we have looked at it together.
Test only on hubs and homes that are yours or that you have explicit permission to test, as the terms of use say. Do not send us other people's codes or PINs.
Read next
Tell us about your space
Tell us what you have and what you want, and we will work out together what your space needs.
