Security
How we protect the information of restaurants and their customers.
Last updated: 15 November 2026
In a nutshell
- Bite2u does not store card numbers: online payments are processed by specialised payment providers.
- Information travels encrypted, and passwords are stored in a way that nobody, Bite2u included, can read them.
- Each restaurant only sees its own data, and each person signs in with their own access.
- We make encrypted backups every day and check that they can be restored.
- Found a security issue? Write to us at [email protected].
1. Our commitment
Restaurants trust Bite2u with their sales, their menu, their team and their customers’ data. Protecting it is part of the service, not an extra.
We apply technical and organisational measures to protect information against unauthorised access, loss and improper changes, and we review and improve them continuously.
2. Card payments
Bite2u does not store full card numbers or their security codes.
Online payments are processed by specialised payment providers that comply with the card industry’s security standards. Bite2u only receives the result of the payment and, at most, non-sensitive details such as the card brand or its last digits.
3. Encryption
- All communication between your device and Bite2u is encrypted.
- Passwords and staff PINs are stored with irreversible encryption: nobody can read them, Bite2u included.
- The keys of the services each restaurant connects (for example, e-invoicing) are stored encrypted.
4. Account access
- Each person in the restaurant signs in with their own access and only sees what matches their role (floor, kitchen, bar, delivery…).
- Actions involving money, such as charging, refunding or closing the till, are signed by the person who does them.
- New passwords must meet minimum requirements.
- Bite2u automatically slows down repeated attempts to sign in with a wrong password or PIN.
- Sessions expire on their own after a while, and the owner can remove access for a person or a device at any time.
5. Each restaurant, its own data
Each restaurant’s information is kept separate from everyone else’s. On every operation, the system checks that whoever requests data belongs to the restaurant that data belongs to.
Order prices and amounts are always calculated by Bite2u’s server, not by the device placing the order.
6. Infrastructure and monitoring
Bite2u runs on protected servers, with access restricted to authorised staff and security updates kept up to date.
We continuously monitor that the service is working and are alerted when something fails, so we can act as soon as possible.
7. Backups
We make backups every day. They are encrypted before leaving our servers and stored in a separate location, so only Bite2u can open them.
We regularly check that the backups can be restored.
8. Record of operations
A paid sale is never deleted: if needed, it is refunded, and there is a record of who did it, when and why.
Till closings and cash movements are recorded with the person who made them.
9. Our team and our processes
Only authorised Bite2u staff can access the systems, and only when they need to in order to provide the service or answer a request.
We follow internal policies on security, access control, backups and incident response, and we review the code and configuration periodically.
10. If an incident occurs
If we detect a security incident, we act to contain it, find out what happened and prevent it from happening again.
Where the law requires it, we notify the affected restaurants and the competent authorities. How we handle personal data is explained in our Privacy Policy.
11. What you can do
- Use a password you do not use anywhere else, and do not share it.
- Give each person on your team their own access or PIN, and remove it when they stop working with you.
- Sign out on devices you share with other people.
- Keep your devices and your browser up to date.
- Bite2u will never ask for your password by email, message or phone.
12. Found a security issue?
If you think you have found a security issue in Bite2u, write to us at [email protected] with as much detail as you can. We will review it and get back to you.
We ask that you do not access data that is not yours, do not change or delete it, do not disrupt the service and do not make the issue public until we have fixed it.
You may also be interested in
- Restaurant Blog
- How to Stop Paying 30% Commissions to Delivery Apps
- Uber Eats vs DoorDash vs Bite2u: Which Is Best for Restaurant Owners?
- Complete Guide to Food Delivery in South Beach Miami 2026
- How to Increase Restaurant Revenue with Online Ordering
- Delivery vs Takeaway: What's More Profitable for Restaurants?