Data Safety

Data safety covers how QRTable technically protects the information that flows through our POS, QR ordering, and website platform. This page explains the practices we follow. For what we collect and why, see our Privacy Policy.

1. Our Approach to Data Safety

Restaurants trust QRTable with orders, customer details, and payment flows every service. We build with that responsibility in mind: minimise what we store, protect what we do store, and make it easy for you to see and remove your data.

2. Encryption in Transit and at Rest

• All traffic between your devices and QRTable is encrypted over HTTPS/TLS, whether you are using the POS app, the QR ordering menu, or the website.
• Data stored in our databases is encrypted at rest using industry-standard methods provided by our hosting infrastructure.
• No method of storage or transmission is 100% secure, and we cannot guarantee absolute protection, but we design every layer to reduce that risk.

3. Hosting & Infrastructure

QRTable runs on established cloud infrastructure providers rather than self-managed servers, so the physical security, network protections, and uptime of the underlying hardware are handled by providers whose core business is infrastructure security. We keep dependencies and platform components up to date as part of routine maintenance.

4. Payment Security

• QRTable does not store full card numbers on our own servers.
• Payments are processed through PCI DSS compliant providers such as Stripe, PayPal, and Razorpay, depending on your region and setup.
• Your payout and billing details are managed directly with these processors under their own security and compliance programs.

5. Access Controls

• Staff access to production data is limited to what is needed to provide support and keep the platform running.
• Restaurant accounts have role-based access, so owners can control what staff, waiters, and delivery executives can see and do inside QRTable.
• Passwords are never stored in plain text.

6. Backups & Recovery

We run regular automated backups of core platform data so that service can be restored quickly in the event of a failure. Backup frequency and retention are reviewed periodically as the platform grows.

7. Data Retention & Deletion

• Your restaurant's data is retained for as long as your account is active.
• You can request export or deletion of your account and associated data at any time by contacting us.
• Some records, such as payment and tax history, may be retained longer where required by law.

8. Third-Party Subprocessors

We rely on a small number of trusted providers to run QRTable, including cloud hosting, payment processing, and email delivery. Each is chosen for its own security practices, and we only share the data each provider needs to perform its specific function.

9. Reporting a Vulnerability

If you believe you have found a security issue in QRTable, please tell us before disclosing it publicly. Email support@qrtable.io with details and, if possible, steps to reproduce it. We aim to acknowledge reports promptly and will keep you updated as we investigate.

10. Changes to This Page

We may update this page as our practices and infrastructure evolve. Updates will be posted here with a revised effective date.

11. Contact Us

Questions about data safety at QRTable can be sent to: