Strict separation of restaurants
On each request, the server checks the account and membership of the relevant restaurant. This keeps restaurant data separate.
Security
You decide which areas each team member can access and how long guest data is kept. Find out how sign-in, access checks and data retention work in Tischify.
Access and retention
Tischify checks access separately for each restaurant. Manage permissions, retention periods and signed-in devices in the settings.
On each request, the server checks the account and membership of the relevant restaurant. This keeps restaurant data separate.
Sign in with a code sent to your email. View signed-in devices in your account and revoke their access when needed.
Assign permissions to match each team member’s work, such as reservations, the website or menus. Manage membership separately for each restaurant.
Reach measurement works without cookies and without raw IP addresses. Do Not Track and Global Privacy Control are respected, and you can object on the privacy page.
Google Maps loads only when a guest explicitly asks for it. Before that there is no connection to Google.
After the set retention period, older reservations are anonymised and unused guest profiles deleted. Contact enquiries are also subject to automatic deletion.
Images and documents are held in private storage. Access uses verified links that are valid for a limited time.
Names, phone numbers, email addresses and internal notes never appear in logs, statistics or push messages. The lock screen shows no guest name either.
Automatic translation processes the designated website text fields. Guest data and sign-in credentials are excluded.
Data minimisation
Tischify limits data in technical logs and notifications. Audience measurement records usage without a personal tracking identifier.
What you control
Set permissions and retention periods in the settings. Use your device list to review signed-in devices.
Questions about security
Contact us to learn more about storage, access or deletion.