Your data stays yours.
Written for IT, DPOs and legal teams. The short answers first, the details below.
Security in four figures
- database per client
- 1:1
- hosting
- EU
- AI training on your data
- 0
- of requests logged in your database
- 100%
The head of IT asks. The film answers.
Film · 62 sBefore we sign
What we commit to, in plain words.
Your own database.
Each client gets a separate database. No shared tables, no mixing between clients. Even your product names stay with you: we sort products into categories with a reference built from our own restaurants. Removing a client removes their database, with a certificate of deletion.
Hosted in the EU.
Databases, backups and processing stay in the European Union. Backups are encrypted. GDPR and Swiss data protection compliant.
Never used to train AI.
One AI provider, under contract, with no training on your data. Queries are read-only and limited to the tables a question needs.
Logged in your database.
Each person sees only their scope. Every request is recorded in your own database, for as long as you choose. The text is readable only by the people you name, and documents or images are never kept.
From the first day to the last.
- Sign-in
- Two-factor sign-in for the backoffice.
- New phone
- A six-digit code by email links a phone to its person. Access is revalidated after 30 days without use.
- Departure
- Access cut in one click, on every channel.
- Messages
- Answers can erase themselves from phones after 12 or 24 hours. A copy stays in your database, for as long as you choose, readable by the people you name.
Read from your systems. Answered in your chat.
- 1 · Your systemsPOS, bookings, property, cameras
- Hosted in the EU
- 2 · ConnectorsRead-only access, credentials encrypted
- 3 · Your databaseSeparate, in the EU
- 4 · UniqBotChecks who asks, and their scope
- 5 · Your teamWhatsApp, Telegram or Slack
Consultation only: no order, reservation or POS changes. Consoles never show your business data. Camera images are sent only to the people allowed to ask for them.
Onboarding: you share read access to your systems and sign our data-protection terms, then we connect them on day one.
Briefs: voice notes are transcribed, then deleted. Audio is never stored. Transcription uses a sub-processor named on the sub-processors page. The brief and its transcript stay in your database, and you choose role by role who dictates and who reads.
Bot activity: what your team asks and what the bot replies stays in your database only, at the level and for the time you choose. An everyday phrase is stored as the command it became. The original words are kept only if you chose to keep content. The text is readable only by the accounts you name, each reading is audited, and we have no access to it. Reports, files and camera images are never kept.
Control Pro (coming soon) and staff data: flags reach only the roles you choose, every view is logged, and a person reviews each flag before anything happens. Flags concern actions in the POS.
Where your database lives.
- Default
Hosted by us
A dedicated database in our EU infrastructure, backed up and monitored. Nothing to set up on your side.
- On request
Your own database
Hosted by your IT, with the three access roles we need. Requirements document available on request.