Kept apart, down to the database.
Each store’s records are separated in the application and again by the database itself, so one store can never read another’s.
Trust & security
Your store’s data is the record of your business. It is kept separate, private and under your control, and here is how.
Separation
Each store’s records are separated in the application and again by the database itself, so one store can never read another’s.
Your team sees only the stores, modules and pages you give them, by role and person.
One login reaches each of your stores, and only yours.
Access
Our staff cannot open your store. You grant time-limited support access when you want help.
Support sessions, sign-ins and important changes are recorded for you to review.
Security emails for a sign-in from somewhere new, a password change or paused sign-ins.
Protection
Recorder passwords, camera links, POS connections, webhook secrets and staff phone numbers are stored encrypted.
Sign-in lives in secure, HttpOnly cookies that page scripts cannot read, and your profile is not stored in the browser.
Personal details are removed before anything reaches the AI provider, and conversations are encrypted at rest.
Practice
The code is checked every week for vulnerabilities, leaked secrets and risky dependencies.
Rate limits and lockouts stop password guessing, and bot checks guard sign-in and forms.
Every module runs on its own record. Clover, Square and online channels connect as add-ons you control.
Ask us during a demo. We’ll show you exactly who can see what, and how to change it.
We count visits with cookieless analytics. No cookies, no cross-site tracking. Privacy policy