Transparency Commitment: RestoNexa is an account-based, business-to-business (B2B) restaurant management system. We do not sell, monetize, or harvest personal data.
1. Privacy Roles (Controller vs. Processor)
- Data Controller: The restaurant owner acts as the Data Controller for all patron/customer records, menu pricing, staff permissions, and store sales entered into the app. RestoNexa acts as the Data Controller solely for owner account authentication and subscription licensing.
- Data Processor: RestoNexa acts as a Data Processor executing billing calculations, KOT generation, inventory updates, and multi-device synchronization on behalf of the restaurant.
2. Information We Collect
2.1 Restaurant Owner & Account Data
- Account Identifiers: Name, registered business email, primary mobile number, username, and encrypted password (hashed via Argon2/Bcrypt).
- Business Profile: Restaurant/Brand trade name, legal entity name, store address, GSTIN / Tax ID, FSSAI / local food health license number, operating currency, and tax configurations.
- Subscription & Payments: Subscription tier, Google Play Billing purchase tokens, and transaction reference IDs. Raw credit/debit card numbers are handled directly by PCI-DSS compliant processors and are never stored by RestoNexa.
2.2 Staff & Team Details
- Staff Profiles: Staff member names, phone numbers, assigned roles (Admin, Cashier, Captain, Waiter, Kitchen Chef, Manager).
- Security Credentials: Encrypted terminal PIN codes for shared terminal mode.
- Operational Audit Logs: Clock-in/out timestamps, order punch logs, bill split events, discount approvals, and KOT void audit trails.
2.3 Orders, KOT & Billing Data
- Order Records: Dine-in table orders, takeaway, room service, and home delivery orders.
- Kitchen Order Tickets (KOT): Item names, food modifier choices (spice level, add-ons), special chef notes, kitchen station routing, and prep timestamps.
- Billing & Invoices: Invoice serial numbers, itemized prices, applied taxes (CGST, SGST, VAT, Service Charge), discounts, coupons, round-offs, and final totals.
- Payment Methods: Settlement records (Cash, UPI QR, Credit/Debit Card, Net Banking, or Customer Khata Credit).
- Sales Reports: Cash drawer tallies, day-end shift reports (Z-Reports), and tax summaries.
2.4 Restaurant Patron / Customer Details
- Guest Details (When Entered): Customer name, mobile number, delivery address (for delivery orders), and email address (for digital receipts).
- Customer Khata (Credit Ledger): Credit ledger balances, partial payments, and transaction history.
- Loyalty & Dining History: Visit frequency, order preferences, and loyalty reward points.
3. Android App Permissions & Hardware Access
| Permission |
Purpose & Usage |
CAMERA |
Used strictly on-demand to scan dining table QR codes, product barcodes, expense receipts, or upload restaurant logos. Never runs in the background. |
BLUETOOTH_CONNECT
BLUETOOTH_SCAN |
Used solely to discover and stream ESC/POS commands to wireless 58mm/80mm thermal receipt and kitchen KOT printers (flagged with neverForLocation). |
POST_NOTIFICATIONS |
Used to send instant notifications for incoming orders, KDS kitchen updates, and subscription alerts via Firebase Cloud Messaging. |
READ/WRITE_STORAGE |
Used to export PDF/Excel sales reports to device memory and load restaurant logo images. |
BILLING |
Used to manage and verify RestoNexa subscriptions securely through Google Play In-App Billing. |
INTERNET |
Used for real-time cloud synchronization between waiter tablets, kitchen screens, and the server. |
4. Third-Party Services
RestoNexa integrates with trusted service providers:
- Google Play Services: Core application services and in-app billing.
- Google Firebase: Firebase Cloud Messaging (FCM) for push alerts; Crashlytics for diagnostic crash reports.
- Payment Gateways: Razorpay / Stripe / Google Play Billing for subscription processing.
- Communication APIs: WhatsApp / SMS gateways for transmitting digital invoices upon request.
5. Data Security & Protection
- In-Transit Encryption: All communications between the app and servers use modern TLS 1.3 / HTTPS encryption.
- At-Rest Encryption: Passwords and staff PINs are hashed using Bcrypt/Argon2. Sensitive credentials and database backups are encrypted with AES-256.
- Role-Based Access Control: Staff accounts are strictly limited to their operational permissions (e.g. Waiters cannot view financial analytics or profit-loss statements).
- Multi-Tenant Isolation: Data for each restaurant is isolated by a unique Restaurant ID.
6. Data Retention Policy
- Active Accounts: Operational data is retained during the active life of the restaurant's subscription.
- Financial & Tax Compliance: Completed invoices, bills, and tax reports are retained for up to 7 years in compliance with statutory audit and taxation regulations.
- Diagnostic Logs: Technical crash logs and temporary telemetry are automatically purged after 90 days.
7. Account & Data Deletion (Google Play Compliance)
Restaurant owners have the right to request deletion of their account and all associated operational data at any time.
Deletion Methods:
1. In-App: Go to Settings > Account / Profile > Delete Account & Data.
2. Web Portal: Visit our public deletion page at https://hotelprosolutions.com/restaurant/delete_account.php.
3. Email: Send a request to privacy@hotelprosolutions.com from your registered email.
Upon verification, personal credentials, staff profiles, and active tokens are permanently purged within 30 days. Required tax invoices are anonymized and retained only for statutory periods.
8. Children's Privacy
RestoNexa is a commercial B2B software designed strictly for business operators and adults. We do not knowingly collect personal data from children under 13 (or under 18 where applicable).
9. Contact & Grievance Officer