Khana Khazanaa

Privacy policy

Khana Merchant, Khana Captain, Khana Owner and the Khana Khazanaa website are restaurant services from PatilTech.

Updated 19 November 2026

Who handles your information

PatilTech runs the service. Each restaurant decides who may work in its outlet and what guest, staff and business records to enter. If you are a guest or employee, contact the restaurant about its records. You can also contact adesh@patiltech.com for help identifying the right process.

Accounts and device data

We use owner names, email addresses, phone numbers, restaurant details, staff names, assigned user IDs, roles and authentication information to create accounts, verify access and restore sessions. Requests also carry technical information such as IP address, browser or app information, timestamps and error details. We use these to deliver the service, investigate failures and protect accounts.

Restaurant operations

Depending on your permissions, the service processes table and order details, food preferences or notes, kitchen tickets, reservations, waitlists, guest names and contact information, delivery details, staff assignments, activity and shift records. Billing and accounting can include purchase history, bill amounts, payment method and status, transaction references, UPI and merchant payment-account information, invoice images, tax information, expenses, attendance, salary and payslips. Managers and captains use operational records. Access to owner reports and payroll depends on role and outlet.

Files, messages and optional features

Files you choose, such as menus, invoices or historical records, are uploaded for the requested feature. Assisted import sends the document or selected contents to the configured AI service for extraction. The restaurant assistant processes the question and relevant restaurant context. Prediction explanations use sales summaries and contextual information. Growth features can hold guest contacts, birthdays, preferences, consent and campaign records. A configured messaging provider receives recipient details and message content when a message is sent. Enter only information needed for the task.

Location and public pages

Outlet addresses and coordinates support maps and weather-based predictions. Address lookup sends the address or coordinates to OpenStreetMap’s Nominatim service. Weather lookup sends outlet coordinates to Open-Meteo. On the website, device location is used when you choose detection and grant permission. Android users can enter the outlet location manually. The public showcase loads some media from an external content host, which receives connection information. Demo and support email requests contain the information you choose to send.

Who receives information

Authorized staff and owners in your restaurant see information needed for their role. Guests, kitchen staff, delivery personnel and other recipients can receive the tickets, bills, shared links, exports or messages you direct to them. Cloudflare hosts and delivers the service and stores selected private files. Supabase provides authentication, database, file storage and realtime services. Resend and configured SMS providers such as Twilio deliver communications. Enabled payment services such as Razorpay and Stripe handle payment or subscription information. Assisted features send the required inputs through the Lovable AI gateway to its model providers. Integrations, including delivery and WhatsApp providers, receive information for the connected workflow. Provider processing can occur outside your country. We may also disclose information when legally required.

Security and information on your device

The apps use HTTPS for service requests and backend access controls to limit access by account and outlet. Sign-in sessions, preferences, offline records and pending work can be stored on the device. An enabled home-screen widget can display workspace information on the launcher. Protect shared devices and exported files. Sign out when handing over a device and remove any widget or exports that others should not see.

Retention, deletion and your choices

We keep account information while access is active and restaurant records while needed to provide the workspace. On a verified deletion request, we remove the account and associated personal data, subject to records needed for accounting, tax, payment disputes, security investigations or other legal obligations. Those exceptions last for the applicable obligation or dispute. Shared restaurant records may continue with personal identifiers removed where possible. Residual backup copies age out through the relevant provider’s backup cycle. Copies already exported by the restaurant are under its control. Contact us to ask which records apply to your request, request access or correction, or raise a concern.

Request deletion

Use the account and data deletion page from any browser. You can also open Delete account from the app’s sign-in screen or Settings.