Security, control, and trust

Sensitive restaurant data deserves careful control

Because URA is designed to handle operational and financial information, this page states the controls we intend to offer. Features are labeled honestly. We have not invented certifications, audits, or customer claims.

Role-based permissions

Planned / specified

Owners, managers, and other roles should only see what they are allowed to see.

Secure connection methods

Planned / specified

Connections to POS, accounting, and other tools are intended to use authorized, documented methods — not unofficial access.

Data encryption

Planned / specified

Data is intended to be protected in transit and at rest. Specific vendors and certificates will be published when confirmed.

Financial data protection

Planned / specified

Financial actions require human approval. Raw bank or card details should not be stored unnecessarily.

Audit logs

Planned / specified

Sensitive actions should leave a trail of who approved what, and when.

Human approval requirements

Specified in the product

Payments, orders, tax filings, published schedules, and public campaigns need a person.

Customer data ownership

Planned / specified

Restaurant data remains the customer’s. This draft is not a legal contract; terms will be published separately.

Integration access management

Planned / specified

Connected-system permissions should be visible and manageable by the owner.

Ability to revoke connected system permissions

Planned / specified

Owners should be able to disconnect a system and revoke access.

Nothing on this page is a completed certification (for example SOC 2 or PCI) unless and until URA publishes one. Ask during a demo for the current implementation status.