Security and data protection
Visitor records contain names, ID documents, files and sometimes video. VisitSoft treats them as sensitive data by default. Here is what is in place.
Who sees what
- Roles defined by your organisation, with permissions per menu and per action
- Sessions that expire automatically
Consent first
- On your website, visits are not linked together until the visitor agrees
- The tracker never reads the contents of form fields: only what the visitor chooses to send reaches VisitSoft
- A video call only starts with the visitor's agreement
Documents and files
- Every file submitted in the chat or online is scanned for viruses before anyone can open it
- Until the scan has answered, the file stays in quarantine
Privacy at reception
- The waiting-room screen shows ticket numbers and counters only, never names
- Records are not visible to later visitors, unlike a paper log
Secrets and integrations
Keys for WhatsApp, Facebook, Google and other services are stored encrypted (AES-256-GCM) and can be rotated by the administrator at any time.
Audit trail
VisitSoft records who changed what, and when, on visits, bookings and dossiers. When a question comes up, the history answers it.
Hosting and retention
VisitSoft runs on your own premises or in the cloud. You set the retention rules and keep control of backups. We help you keep retention periods to what is necessary.
Frequently asked questions
Where is our data stored?
On your server if VisitSoft runs on your premises, or in the cloud environment agreed with you. Ask us for the details for your project.
What if a visitor asks for their data to be deleted?
Your retention rules and data protection procedure apply. We help you organise how such requests are handled.
Can we limit what a receptionist sees?
Yes, by role: each menu and each action can be allowed or not.
See it with your own front office in mind
Tell us how you receive visitors today. We reply within one working day, in English or French.