Legal, security & accessibility

Each restaurant's data is isolated from every other restaurant on the platform. Accepted orders are recorded durably, and menu, service, and commercial definitions are versioned and auditable.

Staff and kitchen access is permission-scoped to what each role needs. Backup and recovery procedures protect operational data. Guest sessions are temporary and scoped to a single table visit — a table QR code alone is not an ordering credential.

To report a security concern, contact [email protected].

ForkPI does not require diner accounts and does not build persistent guest profiles. A guest session is tied to one table visit and does not follow the diner afterwards, or across restaurants.

Restaurant and operator information is processed only to provide the service. For data access or deletion requests, contact [email protected].

ForkPI uses strictly necessary cookies for authenticated sessions and security, such as keeping you signed in and protecting requests. It does not use advertising cookies and does not track guests across restaurants.

ForkPI aims to meet WCAG 2.1 AA. Interfaces support keyboard navigation, visible focus, screen readers, text scaling, and reduced motion, and never rely on colour alone to convey status or meaning.

If you encounter an accessibility barrier, please tell us at [email protected] so we can address it.

ForkPI is provided as a subscription service for dine-in restaurants. The full terms of service are presented during account creation and are available on request.

For a copy of the current terms, contact [email protected].

Operational status and any planned maintenance are communicated to customers. Optional providers expose their own health and degraded states inside your workspace.

For current platform status, contact [email protected].