Your data.
Your control.
Practical protections for your restaurant and your customers.
Your restaurant has its own space
Every database read and write is limited to the restaurant or restaurants linked to the signed-in account.
Support sees masked customer details
Names, phone numbers, email addresses and addresses are masked for OrdrCiti support. Each access is logged, and the restaurant owner can view that log.
Sensitive connections are protected
Payment-provider keys, WhatsApp tokens, AI keys and Google Business Profile credentials are encrypted when stored, using AES-256-GCM and restaurant-level key protection.
Extra safeguards around sign-in
Passwords are stored as bcrypt hashes. Sessions use signed tokens, and login and reset-code attempts are limited. API safeguards also reject database-injection attempts and restrict browser access to approved sites.
Bill links reveal less
Each bill link uses a random code, and the bill page masks the customer’s phone number.