A practical promise for responsible restaurant data

Useful data should have a defined purpose, owner, retention period, and access policy. “We may need it later” is not a strong reason to collect a guest or employee detail.

Make responsibility operational

Minimise fields, encrypt data in transit and at rest, separate tenants, and use least-privilege access. Record sensitive changes and review them. Give people clear consent and deletion paths where applicable, and document the few legal or accounting exceptions.

Backups need the same care as live systems. Test restoration, expiry, and incident response so the written policy matches reality.