Privacy Policy

Publisher: Anurag Pandey
Effective date: 18 August 2026
Contact: anuragpandey5957@gmail.com

Food Data Extractor is an independent utility for authorised restaurant partners. It is not affiliated with, endorsed by or sponsored by Zomato, Swiggy or any other partner platform.

Website analyser and calculator

Files selected in the settlement analyser are read and analysed locally in your browser. Settlement files, payout details and calculated results are not uploaded to the publisher or licensing service. The income margin calculator also operates locally on your device.

Extension export data

The extension may temporarily handle outlet identifiers, orders, menu information, customer identifiers contained in authorised responses, ratings, reviews, advertising metrics, settlements, deductions, fees, taxes, commissions and invoices. Export processing occurs in your browser. Export contents, partner-platform passwords, cookies, one-time passwords and session tokens are not transmitted to the publisher or licensing service.

Licensing data

To provide usage limits, activation and subscription enforcement, the licensing service handles a random installation identifier, a revocable device token, plan, subscription status, module selection, date-range length, usage counters and a cryptographic hash of an outlet identifier. During checkout it also handles the purchaser's email, Razorpay subscription identifier and hashed activation key.

Community identity and content

Community sign-in uses Google Identity Services. The community service verifies a Google account identifier, verified-email status and display name. It stores protected cryptographic hashes of the Google account identifier and email address, the Google display name, chosen public username, optional public restaurant/outlet name, account role and status, security-session records, posts, replies, reports and moderation history. It never receives or stores the Google password.

If the Partner Data Exporter extension is installed and actively licensed, the community page may ask it for a locally saved restaurant/outlet name to prefill the public profile form. This is only a local suggestion that you must confirm; the community service does not receive activation keys, device tokens, entitlements or licensing-database records.

Community posts and replies become public immediately after a signed-in member publishes them. The community does not provide a mobile contact-number field, and previously stored dedicated contact values are cleared during migration. Do not publish phone numbers, customer or third-party personal data, credentials, partner exports or confidential business records inside post or reply text. Community data is kept in a dedicated Cloudflare D1 database that is separate from extension licensing and payment data. Sessions expire automatically; reports and security records may be retained to prevent abuse and resolve disputes.

Payments

Payments are processed by Razorpay under Razorpay's own terms and privacy policy. Card, bank and UPI credentials are entered into Razorpay and are not received by this website, the extension or the publisher's licensing service.

Advertising, cookies and consent

Public content pages use Google AdSense. Google and other third-party vendors may use cookies or similar identifiers to serve, measure and personalise ads based on a user's prior visits to this and other websites, where consent and applicable law permit.

Google's use of advertising cookies enables Google and its partners to serve ads based on visits to this site and other sites. Users can control personalised advertising through Google Ads Settings and can review wider industry opt-out choices at AboutAds.

For visitors in the European Economic Area, the United Kingdom and Switzerland, a Google-certified consent management platform may request consent before eligible advertising cookies or personalised ads are used.

Restaurant reports and exported operational data are not shared with advertising providers and are not used to personalise ads.

Storage and retention

Browser storage may contain interface preferences, random installation identifiers, a revocable device token and a cached plan summary. Downloaded exports and analyser results remain on your device. Licensing and payment records are retained while an account is active and afterward only as required for security, disputes, accounting and legal obligations. Community sessions, contributions, reports and moderation records follow the retention described in the community section.

Sharing, security and user control

Limited licensing data is shared only with infrastructure providers needed to operate the service. Network transmission uses HTTPS. Users can stop exports, delete local files, clear browser storage, deactivate a device or uninstall the extension. Contact anuragpandey5957@gmail.com to request access, correction or deletion of licensing or community account data.

Changes

Material changes will be reflected by updating this page and its effective date.