Role-based permissions
Planned / specified
Owners, managers, and other roles should only see what they are allowed to see.
Security, control, and trust
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.
Planned / specified
Owners, managers, and other roles should only see what they are allowed to see.
Planned / specified
Connections to POS, accounting, and other tools are intended to use authorized, documented methods — not unofficial access.
Planned / specified
Data is intended to be protected in transit and at rest. Specific vendors and certificates will be published when confirmed.
Planned / specified
Financial actions require human approval. Raw bank or card details should not be stored unnecessarily.
Planned / specified
Sensitive actions should leave a trail of who approved what, and when.
Specified in the product
Payments, orders, tax filings, published schedules, and public campaigns need a person.
Planned / specified
Restaurant data remains the customer’s. This draft is not a legal contract; terms will be published separately.
Planned / specified
Connected-system permissions should be visible and manageable by the owner.
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.