Security
Your data,kept safe.
A restaurant’s cash, payroll and team live on one platform. So the first job is to encrypt the data, show everyone only their own work and record who changed what.
In short
In plainwords.
What we do, without the jargon:
- Data travels encrypted; sensitive details (IBAN, tax ID) are stored encrypted
- Everyone sees only their own work
- Who changed what, when — on record
- Optional two-step login
- Backed up every night
- Personal data protected under GDPR and KVKK
Technical detail
Underthe hood.
- 01
Encrypted in transit
All traffic between browser and server is TLS-encrypted: TLS 1.3, with TLS 1.2 for older clients.
- 02
AES-256 field encryption
Sensitive fields (IBAN, BIC, tax and social-security numbers, phone, two-step login secret, chat messages) are encrypted at field level in the database with AES-256-GCM.
- 03
Passwords and sessions
Passwords are hashed with bcrypt, never stored in plain text. Sessions use JWT plus rotating refresh tokens; optional two-step login (TOTP).
- 04
Closed database
Database and cache ports are not exposed publicly; they are reachable from the internal network only.
- 05
Non-root containers
Services run as non-root users in isolated containers.
- 06
25 roles
Role-based access: cook, chef, location manager, accounting, auditor… Everyone sees only the data of their role and location.
- 07
Audit trail
Important changes are recorded with who, what and when (GoBD audit trail). Payroll and financial records are excluded from automatic clean-up and kept for at least 10 years.
- 08
Nightly backup
The database is backed up every night with tiered retention: 30 days daily, 12 weeks weekly, 12 months monthly, 7 years yearly. The restore process is documented.
- 09
GDPR / KVKK
Built with EU and Turkish data protection requirements in mind. A data processing agreement (DPA) is ready.
Documents
On paper,too.
Data processing, privacy and your rights, on their own pages in plain language: