"Is it secure" is a fair question to ask before putting a system in front of every transaction a venue processes. Here's the specific, unembellished answer rather than a marketing paragraph.
Encryption in transit and at rest
Data moving between a terminal and NUA's servers is encrypted in transit, and data at rest is encrypted in storage, the baseline any modern platform handling business and payment-adjacent data should meet.
Payments stay with PCI-compliant processors
Card processing runs through payment processors that carry PCI-DSS compliance themselves. NUA's role is orchestration, not custody of card data, which keeps the highest-risk part of the stack with specialists built for exactly that job.
Role-based access
A line cook's login can't see payroll. A shift supervisor's login can't change pricing tiers. Access is scoped to role, so the system that runs the whole venue doesn't hand every staff member the keys to all of it.
The AI audit trail
Every action NUA AI takes automatically is logged with what it did and why, not a black box making silent changes to pricing, stock, or staffing.
What we don't claim
We don't publish this as a substitute for a formal compliance certificate. It's a plain-language summary of the architecture, and we'd rather be specific than vague. See the full Security page for the complete breakdown.