The connection layer.
HTTPS protects information in transit between the app and its services. Account verification and session checks determine who is making a request; a protected connection alone does not grant access to business records.

Orderly
A secure connection is one layer. Encrypted storage, account verification, permissions, and session controls each do a different job. Orderly brings them together.
A manager reviewing pay, a team member opening a checklist, and an employee signing into a shared tablet need different access. Our design question is practical: how can the right information reach the right person, while limiting exposure at every handoff? The answer is a set of protections with clear responsibilities and clear limits.
HTTPS protects information in transit between the app and its services. Account verification and session checks determine who is making a request; a protected connection alone does not grant access to business records.
Business records and private media use AES-256-GCM application encryption. Encryption keys are kept separately from the stored records. Passwords use one-way verification hashes rather than being stored as readable passwords.
Role and individual permissions control what people can view or change. Sensitive profile details, cash-handling actions, employee administration, and operational tools have their own controls instead of sharing one broad management switch.
How do we protect a restaurant’s information while giving every team member the access they need to do good work?
A design principle for Orderly · The Frameworks CompanySign-in protections include password verification and supported two-factor authentication. Signed-in device controls let an account holder review sessions and revoke access when needed.
Permissions can distinguish a person’s own records from those of other team members, with access scoped by responsibility. Hiding pay on a shared screen is an additional privacy choice; it never substitutes for permission to read pay data.
Shared kiosks support an inactivity countdown and quick sign-out. Account handoffs retire the previous kiosk session. Revoked credentials are rejected on the next server request, while the app also checks session status when active.
Every layer has a role.
Browser private keys and readable message caches stay in page memory. Reloading, closing the page, signing out, or changing accounts discards them. To read older encrypted history, request access and approve the matching code on another device that can already read that history. Approval requests expire after 15 minutes.
Supported native app screens can apply capture protection and screenshot notices. Browsers cannot prevent operating-system screenshots. Capture controls are an additional safeguard, separate from encryption and permissions, and are not a guarantee that information can never be copied.
Storage encryption protects stored business content, but the running service can decrypt authorized records. Some technical metadata remains visible, and exports, client caches, older copies, and information already downloaded require their own protections. Message encryption is a separate layer, with the cache and preview limits explained on our Data protection page.
In development · Target release Q1 2027.
Device support and feature availability may vary by release and configuration.