On our side
Data stays in the country, on your server. Cross-border transfer never arises, because the system does not do it.
Data and security
Where there is a camera, there is one question: where does this data live?
The answer is short — with you. Video is processed on your own server, no face image is stored, and a guest stays a number rather than a name. Below is how to check each of those.
Send your security questions Send your checklist — we answer it point by point
- 0face images written to disk
- 0records copied to a Bayonic server
- 90 daysdefault retention — you change it
- AES-256database encryption
The data path
The frame disappears. The number stays.
The system looks at a frame to take one row out of it, not to keep it. Everything else is built from that row.
Your building · your server
- Framefrom the camera · in memoryframe discarded
- Vectora set of numbers · cannot be turned back into a photo
- IdentifierFR-005043 · no name
- Event and reporttime, segment, metric
Bayonic’s serverNothing is sent here — not the frame, not the vector, not the report.
What is stored
The list is short because the rest is not needed
Stored
- Face vector (a mathematical representation)
- The guest’s nameless number and visit history
- Events: time, camera, segment, duration
- Staff list and shift data
- Audit log: who opened what, and when
Not stored
- A face image or a frame file
- A guest’s name, phone or document
- Continuous video archive (that stays on your NVR)
- Call audio (in VOCO, only the calls you enable)
- Nothing is copied to a Bayonic server
Who sees what
Access follows the role, not the wish
Each role sees exactly as much as the job needs. Every time something is opened, the log records it.
| Role | Sees | Does not see |
|---|---|---|
| Cashier / waiter | the guest’s tier (new, regular, gold) | personal data, other branches |
| Manager | shift metrics, events, their own branch | other branches, system settings |
| Director | every branch, reports, comparisons | a face image — there is none |
| Bayonic | technical logs, while you have access open | your guest base and video — ever |
Retention and deletion
Retention is a setting, not a promise
The console carries a "data retention period" field: once the days run out, records are deleted automatically. Anonymisation mode goes further and cuts the link to the identifier.
Default period90 days — changed in the console
Anonymisationhistory stops being tied to an identifier
Full deletionon request the base is wiped, with a report
Exportyour data comes back to you whenever you ask
The legal side
What we answer for, and what stays with you
On your side
Notifying staff, your internal policy, and signing off the access list. At rollout we hand over template wording and a settings checklist.
What we do not claim
We promise no certificate and no legal opinion. We state what the system does — your lawyer judges the rest.
Questions
The five we are asked most
If your question is not here, send your list — we answer it point by point.
Send your security questionsDo you store faces?
No. A mathematical vector is taken from the frame and the frame itself is discarded. A photo cannot be reconstructed from the vector — it is a key for recognition, not an archive.
Do we need guest consent?
The system never asks for or stores a name, a phone number or a document — it works with a nameless number. Signage in the room and your internal policy stay on your side; we hand you template wording.
Where does the data sit?
On a server in your building. The cloud is optional, and the system keeps running if the line drops. That is architecture, not a setting.
Can Bayonic see our data?
No. Support access is opened by you, for a period, and every session is logged. Your guest base and your video are never copied to us.
What if the server is breached or stolen?
There are no face images on the disk — the most valuable thing is simply not there. The rest of the base is encrypted, access is limited by role and password, and the log shows what happened.
Review
Send us your security questions.
If you have internal requirements or a security checklist, put it here. You get a point-by-point answer, in yes/no form.