Your privacy
Privacy policy
How we handle your information when you order with Okare.
Okare Enterprise · Last updated 21 October 2026
1. Who we are
Okare is a food-ordering and delivery service operated by Okare Enterprise, Musabani No-3, Musabani, East Singhbhum, Jharkhand 832104, India.
This policy covers the Okare customer app, our public website, and privacy or deletion requests made through this website. Rider and restaurant-partner services have different account and operational needs.
For privacy questions, access, correction or deletion requests, email support@okare.in or call +91 9942304436.
2. Information we collect
- Website analytics: We use Umami Cloud to measure visits to our public website and understand how visitors use its pages. Your browser connects to Umami to load its analytics script and send analytics events. Do not include personal information in website URLs. This website analytics integration is separate from the customer, rider and restaurant apps.
- Landing-page interaction analytics: We use Microsoft Clarity on our homepage to understand how visitors interact with it through heatmaps and session recordings. Your browser connects to Microsoft to load the tracking script and send interaction and technical data. Clarity may use cookies depending on consent and project settings. For details about Microsoft’s handling of information, see the Microsoft Privacy Statement.
- Website early-access requests: if you sign up for Android testing, we store your Google Play email, signup time and consent record in Supabase, and use your email to manage the test and add you to Google Play’s tester list. Our website hosting provider processes the request. We also use a hashed network identifier to limit repeated submissions; expired identifiers are cleared when subsequent signup requests arrive. Signup emails are removed when testing ends or when you request removal at support@okare.in. This does not create an app account or subscribe you to unrelated marketing.
- Account and contact information: your registered mobile number or email, authentication information, name and checkout contact details. Email/password authentication is handled by Supabase Auth.
- Delivery information: saved addresses, house or flat number, landmark, map pin and delivery instructions.
- Orders and payments: items, amounts, order status, payment method, transaction references, verification status, refund references and delivery confirmation codes.
- Preferences and support: favorites, notification preferences, food/delivery feedback, support tickets and information you include in messages.
- Device and service information: push notification tokens and operational request details such as IP address, timestamps, app/device information and error responses processed by our infrastructure and integrated services.
Payment credentials entered into PayU or a payment app are processed by those services. Okare’s order records store payment amounts, references and status, rather than your UPI PIN or card security code. Do not include passwords, OTPs or payment PINs in support messages.
3. How we use information
We use information to verify accounts, prepare and deliver orders, calculate charges, process and reconcile payments, provide order history and live tracking, send order/payment updates and announcements, respond to support requests and refunds, investigate errors or misuse, and maintain the service.
Information retained for accounting, payment reconciliation or disputes is used for those purposes. Deleting an account does not itself cancel an order or initiate a refund.
4. Location, notifications and device storage
Location permission is optional in the customer app. “Use my current location” helps place your delivery pin. You can enter an address instead. The customer app does not continuously transmit your live phone location for delivery tracking; it displays the assigned rider’s location while the delivery is active.
Your delivery address and pin are shared with the restaurant, assigned rider and authorized staff as needed to fulfill the order. Map and route services receive coordinates used for those features.
If you enable notifications, a device push token is linked to your account for order updates, payment alerts and announcements. Notification content may appear on the lock screen. You can change notification preferences in App settings and permissions in your phone settings.
The app stores sign-in sessions, cart and payment-recovery information, favorites and appearance preferences locally. Clearing app storage removes local information; it does not delete your server account. An offline device may retain cached information until it reconnects or you clear its app storage.
5. Who receives information
Restaurants, assigned riders and authorized operations/support staff receive the details needed for their role. Okare uses these connected services:
- Microsoft Clarity: homepage interaction analytics, heatmaps and session recordings.
- Umami Cloud: public website visit analytics.
- Supabase: account authentication, application database, storage where used, and server functions.
- StartMessaging: your mobile number and verification message to deliver login codes.
- PayU and payment partners: checkout contact and payment information for payment processing and verification.
- Expo and Firebase Cloud Messaging: push tokens, notification payloads and related delivery information.
- Google Maps and Routes: map/route requests, coordinates and related technical request information.
Loading maps, restaurant photos or other hosted content can disclose your IP address and request information to the hosting service. Providers process information under their applicable terms and privacy practices; their processing locations and retention arrangements depend on the service.
If you choose WhatsApp support, the conversation is handled through WhatsApp. Order-support actions may prepare an order reference in a draft; you choose whether to send it. Email requests are handled through email services.
6. How long information is kept
- Active accounts: account details and saved addresses are kept to provide the service until removed or processed through account deletion.
- In-app account deletion: a verified request schedules deletion after a 30-day waiting period. An hourly job processes eligible requests, so completion occurs on a subsequent run and may take longer if there is a processing backlog or a hold described below.
- Resolved non-payment support tickets: eligible for daily cleanup after 90 days without updates, when the associated order is complete and no related unresolved matter or retention hold applies. Payment/refund tickets are excluded from this cleanup.
- Live delivery coordinates: completion/cancellation cleanup removes live tracking coordinates. A separate daily cleanup covers eligible stale coordinates for terminal orders after 90 days; this is not a promise to retain a 90-day location history.
- Deletion completion records: a minimal record without the customer account ID is eligible for removal 90 days after completion.
- Order, payment, refund and dispute records: Our financial-retention target is 90 days after the associated order is completed or cancelled and all related payments, refunds and disputes are closed, measured from whichever occurs last. Records needed for an unresolved matter or a required legal retention hold may be kept longer. Automatic financial cleanup is enabled and scheduled daily at 9:00 AM India Standard Time. Eligible records are processed in batches; processing backlogs, technical issues or retention holds can extend the period beyond 90 days. Records existing when this cleanup was introduced have a minimum 90-day observation period from its installation. Contact support@okare.in for retention or deletion questions. This schedule applies to records controlled by Okare; provider logs and backups follow separate schedules.
- Provider logs and backups: follow separate provider and configuration-specific schedules. Removal from the active database does not mean immediate removal from logs or backups. We are verifying these schedules with providers; a single fixed period is not currently confirmed.
We do not describe all customer information as expiring after 30 or 90 days. For details about information retained in your case, contact support@okare.in.
7. Access, correction and account deletion
You can edit your profile and saved addresses, remove favorites and manage device permissions. To request access or correction beyond these options, contact support.
In the customer app: open Profile → App settings → Delete account, verify your registered phone or account password, and confirm the request. You can cancel before processing. Signing in does not cancel the request or restart the 30-day waiting period.
Without the app: use our public account-deletion request page, or email support@okare.in. Support verifies ownership and confirms the handling timeframe. Sending an email does not automatically start the in-app countdown.
Deletion removes the login account, profile, saved addresses, favorites, feedback and notification registrations. The process clears personal contact, address and delivery-note snapshots from retained orders/payments, delivery pins/codes and resolved support text. Necessary financial records remain as described above.
Active deliveries, unresolved payment/support matters, retention holds, linked staff accounts, uploaded files requiring review or technical failures can delay processing. The scheduled process retries eligible requests. Contact support using the request reference if a request is delayed.
We verify account ownership before acting on a request. Do not email passwords, sign-in OTPs or payment PINs. Once deletion completes, the old account and its history cannot be accessed by signing up again.
8. Protection and policy updates
We use access controls to restrict customer information to authorized users and services. No storage or transmission method eliminates every risk.
If you believe information was provided without authorization, including information about a child, contact support so we can investigate and address it.
We may update this policy when the service or its data practices change. The latest version and its update date will appear on this page. Contact us if you need clarification about a change.