Privacy Policy
1. Who we are
DineLogics ("we", "us") provides a cloud restaurant management platform — point of sale, kitchen display, delivery rider coordination and owner analytics. It is operated from Pakistan. Contact: dinelogics.support@gmail.com.
For most data in the platform, the restaurant that subscribes to DineLogics is the data controller — it decides what customer and staff information is entered. DineLogics processes that data on the restaurant's behalf to deliver the service.
2. Information the apps collect
| Category | Examples | Why |
|---|---|---|
| Account & staff data | Name, login email, role, PIN (stored hashed), shift times | Signing in, access control, attributing orders and payments to the right staff member |
| Business data | Menu items, prices, orders, payments, stock levels, reports | The core function of the product |
| Restaurant customers' data | Name, phone number, delivery address and order notes entered by staff when taking an order | Preparing and delivering that customer's order; order history for repeat service |
| Device data | A device identifier generated on first sign-in; a push-notification token (Firebase Cloud Messaging) | Binding a till or kitchen screen to the right branch; delivering order alerts |
| Diagnostics | Server request logs (timestamps, endpoints, response codes) | Keeping the service reliable and secure |
The apps do not collect your precise or background location, contacts, photos, microphone or camera data, and contain no advertising or analytics SDKs beyond Firebase Cloud Messaging for notifications.
3. How information is used
- To operate the service: take orders, route them to the kitchen, dispatch deliveries, and report sales to the restaurant's owner.
- To secure the service: authenticate users, scope each account to its own restaurant, and audit sensitive actions (voids, refunds, discounts).
- To support the restaurant: diagnose problems it reports to us.
We do not sell personal information, use it for advertising, or share it with third parties for their own purposes.
4. Where data lives and how it's protected
- Data is stored in a managed cloud database and transmitted only over encrypted connections (HTTPS/TLS).
- Each restaurant's data is isolated per tenant; staff access is limited by role-based permissions.
- Passwords and PINs are stored as salted hashes, never in plain text.
- Our hosting providers (currently Railway for the backend and Vercel for web delivery) process data solely to run our infrastructure.
5. Retention and deletion
Operational data is retained while the restaurant's subscription is active, because it is the restaurant's business record (sales, taxes, stock). When a subscription ends, data is deleted or anonymised after a reasonable wind-down period, or earlier on the restaurant's written request.
Account deletion: accounts are created and removed by the restaurant's owner (or by us for the owner account). If you are a staff member, ask your restaurant owner to remove your account; if you are an owner — or a restaurant customer who wants their details removed from a restaurant's records — email dinelogics.support@gmail.com and we will process the request with the relevant restaurant within 30 days.
6. Children
The apps are workplace tools for restaurant businesses and are not directed at children under 13. We do not knowingly collect information from children.
7. Changes to this policy
If we make material changes we will update this page and the effective date above. Continued use of the service after a change means the updated policy applies.
8. Contact
Questions or requests: dinelogics.support@gmail.com · WhatsApp +92 307 6111181 · DineLogics, Multan, Pakistan.