FlowmatixSecurity & data protection
Built for Australian business, on principles you can audit.
No jargon and no hand-waving. Here is exactly how your data is isolated, stored, encrypted and retained — and, at the bottom, an honest list of what we don't yet do.
🗄️ Your own database, not a shared table
Flowmatix is schema-per-tenant: each business gets its own database. The connection itself is the tenant boundary — there is no shared table with a column identifying you, so one customer's query can't reach another customer's rows.
📍 Australian Privacy Principles
Your data is handled under the Australian Privacy Principles. Personal information collected at the kiosk stays in your own database on secure cloud infrastructure, with access restricted to Flowmatix.
🔐 Encrypted in transit
Every connection is TLS-encrypted and HTTP is redirected to HTTPS. Traffic is fronted by a global edge network, and session cookies are set Secure, HttpOnly and SameSite so they can't be read by scripts or sent cross-site.
👥 Role-based access + optional 2FA
Accounts are permissioned by role — who can view the on-site list, who can manage settings, who can export. Passwords are stored only as modern one-way hashes, form submissions are CSRF-protected, and administrators can switch on two-factor authentication (TOTP) with recovery codes.
🧾 A real audit trail
Sign-ins, induction acceptances, setting changes and exports are recorded as timestamped events. Induction and SWMS acceptances are versioned — you can show exactly what someone accepted, and which version, long after the fact.
🗓️ Retention you control
You set how long visitor records are kept; older records are purged automatically to your schedule. The purge never removes someone still signed in, so an open record is never lost by accident.
🛡️ Abuse protection on public forms
Public pages enforce server-side rate limiting by trusted client IP, honeypot and timing checks, and strict body-size limits — behind an always-on edge backstop — so the sign-up and contact forms can't be flooded or scripted.
🍪 Privacy-respecting analytics
Our marketing site runs Google Analytics, which sets analytics cookies — see the privacy policy for exactly what it collects and how to opt out. We set no advertising or re-targeting cookies. Our own visit counts use a daily-rotating, one-way hash that can't identify you or follow you across days. The signed-in app runs no analytics at all.
Straight talk
What we don't do (yet)
The fastest way to lose your trust is to overstate what the product does. So here is the honest boundary — if any of these is a hard requirement, tell us and we'll give you a straight answer.
- No public API yet. There's an Outlook add-in for pre-registration and Microsoft Teams for host notifications, but no documented customer-facing API to build against.
- No admin single sign-on yet. Administrator access is local accounts with role-based permissions and optional two-factor — not SAML/SSO.
- It's a web app (PWA), not a native app. The kiosk runs in the browser on your iPad; there's no separate App Store download.
- WWCC/VIT register validation is Victoria-scoped. Checks are captured and recorded everywhere; automated validation against the register is currently VIC.
- Sign-in flags and alerts — it doesn't block. A missing check raises an alert for your team to action; only an explicit watchlist match stops a sign-in.
Security question we didn't answer?
Email us — a real person who knows the system will reply, not a form letter.