🧾OrderPage

Privacy Policy

Effective date: 17 October 2026

App: OrderPage: WhatsApp Orders (com.binaryscript.whatsorder), for Android and iOS, and the store pages at orderpage.app

Provider: BinaryScript, Bangalore, India

Contact and grievance officer: nk92.iit@gmail.com

This policy explains what information OrderPage (“the app”, “we”, “us”) collects, why, who we share it with, how long we keep it, and how you can delete it. It covers the seller app and the public store pages buyers use to order.

In short

We store what sellers put on their store and the orders buyers place, so the store and its orders work.
We do not sell personal information and we do not show ads in the app.
We use Google services (Firebase) to run the app, and a few other providers listed below.
Sellers can delete their store, its orders and their account at any time from the app.

1. Who this policy covers

Sellers: people who use the OrderPage app to run a store, and the staff and managers they add to their team.
Buyers: people who open a seller's store page (for example orderpage.app/your-store) to browse, order, book or ask for a quote.

For buyers, the seller is the business you are ordering from. The seller decides what happens with your order; we store it and deliver it on their behalf.

2. Information we collect from sellers

Your store (public)

What you add to your store is saved in our database so your store page works, and it is visible to anyone who has your link: business name and description, your WhatsApp number, items, prices and stock levels, opening hours, delivery and booking settings, the questions you ask buyers, and the payment details you choose to show buyers (for example a UPI ID, bank details or a payment link). Please add only what you are happy for your customers to see.

Your account

An account ID. The app signs you in automatically with an anonymous account; you never need a password.
Google account. If you sign in with Google (required on Android phones in India, where it is how you subscribe; optional elsewhere, to back up and restore your store), we receive your Google account's name and email address.
Contact details at sign-up. Your name and WhatsApp number, your language, your phone's platform (Android or iOS), how far you got in setting up the app, and whether you have a subscription and until when. We use this to support you and to understand where new sellers get stuck.
A private recovery code stored on your phone, which lets you restore your store on a new phone. We keep only a scrambled (hashed) version of it.
Your team. If you add staff or managers, we store their account IDs, the name each person enters when asking to join, the role you give them, whether they are on duty, which orders they are given, and which of them did what (for example who confirmed an order or took a payment). An invite you send holds the person's name and role for two days, or until it is used or cancelled. If someone installs the app from an invite link, the app reads the invite code from Google Play's install record once, on first launch.

Your orders and business records

The orders your store receives (see section 3), plus what you record against them: order status, payments and advances received, stock changes and restock lists, bookings, days off and blocked dates. These are private to you and your team.

Some of these records are about other people, entered by you: orders you type in for customers, your subscribers (for example tiffin, milk, gym or class members: name, phone number, address, plan and the days delivered or attended), and the last few phone numbers you sent a restock list to. Names of the people who serve customers that you list in Settings are shown on your store page so buyers can choose one. Please add people's details only when you have a business reason and they would expect it.

Your phone and how you use the app

Notification token, so we can send new-order alerts to your phone and your team's phones.
App usage and diagnostics through Google Firebase: which screens and features are used, app performance, and crash reports (device model, operating system and app version). This helps us fix problems and improve the app.
Your shop's location (optional). If you set it in Settings, from your phone's location (only when you tap to use it) or from your Google Maps link, it is saved with your store so the app can show how far each delivery is. Like your store's address, it is part of your public store details.
Approximate location from your internet connection (city, region and country), looked up through BigDataCloud when the app starts. We do not use GPS for sellers. If you pay through PhonePe (see section 6), this approximate location is saved with your payment account.
When you contact support, the message includes your device model, operating system and app version so we can help faster.

3. Information we collect from buyers

Your order. When you place an order, booking or quote request, we store what you enter: your name, phone number, delivery address, the items and quantities, your answers to the seller's questions, dates you choose, and any note. The seller and their team can see it and use it to fulfil your order.
Your location (optional). If you tap to attach your location for delivery, your browser asks for permission and the pin, with how exact your phone says it is, is saved with your order so the seller can find you. To show you where the pin landed, your browser asks OpenStreetMap's address service (or, if that does not answer, BigDataCloud) to name the area, city and PIN code for that point, and that name is saved with your order too. The seller's app may ask OpenStreetMap the same once, for an order that has no name yet. Nothing is taken unless you tap it and allow it. A landmark you type is saved with your address.
On your own phone or computer. The store page remembers your cart, your name and contact details for next time, your language, and your last order, in your browser's own storage. This stays on your device; clearing your browser data removes it.
Visit counts. The store page adds to anonymous counters (for example: page opened, cart started, order sent) so the seller can see how their store is doing. These counts do not identify you.
Your PIN code (India). If you type a 6-digit PIN code in your address, the store page sends only those six digits to India Post's public PIN code service (api.postalpincode.in) to show the area it belongs to. The area name is saved with your order.
Questions about an order. At stores outside India, the order's status card lets you ask the shop about your order and read its reply. We store what you and the shop write, as text only, with the time and the language of the page. The shop and its team can read it; we do not use it for anything else. It is deleted 7 days after it was sent (the deletion can run up to a day later). Please do not put card numbers or passwords in it.
WhatsApp and other messaging apps. For most stores, sending your order opens WhatsApp with the order written out for you to send to the seller. Some stores also let you send it through Instagram, Messenger, Telegram or email. That message is between you and the seller and is covered by that app's own privacy policy.

The store page has no advertising or analytics trackers of its own. Its fonts are served from orderpage.app itself.

Meta Pixel, only if the seller turns it on. A seller who advertises on Facebook or Instagram may add their Meta Pixel to their store. Once the page has loaded, it then tells Meta that the page was viewed (and which product, when you open a product's own link), that something was added to the cart, that checkout was opened and that an order was placed, with the order's total and currency (never your name, phone number, address or what you ordered). Meta also receives what a browser sends to any website, such as your IP address, browser details and Meta's own cookies, and uses it under its own privacy policy. In the European Economic Area and the UK the page asks first, and nothing is sent to Meta unless you tap Allow; your answer is kept on your phone for that store.
Visits from Facebook and Instagram. When you open a store from Facebook or Instagram, the page keeps a note of it on your phone for 7 days, so the seller can see how many visits and orders came from there. Only the two counts leave your phone.

4. How we use information

To run your store page, show it to buyers, and deliver orders, bookings and alerts to the seller.
To let sellers and their team manage orders, payments, stock and bookings.
To back up and restore stores, and to keep them secure (for example checking that only the owner can change a store).
To process subscriptions and check who has paid.
To provide support, fix problems and improve the app.
To measure how well our own advertising works: when you install or subscribe after seeing an ad for OrderPage on Google, Firebase tells Google Ads that it happened. We do not show ads in the app.

We do not sell personal information.

5. Who we share information with

Who	What	Why
Anyone with a store's link	The public store details in section 2	So buyers can see the store and order
The seller and their team	Buyers' orders (section 3)	To fulfil the order
Google (Firebase and Google Cloud)	Everything we store, plus app usage, performance and crash data	Hosting, database, sign-in, notifications, analytics, crash reports and security checks
Google Play and the Apple App Store	Subscription purchases	To take payments; we never see your card details
BinaryScript's payment service and PhonePe (India, Android)	Your account ID, Google email, phone platform, app version, country and approximate location, and your subscription payments	To take UPI payments through PhonePe and confirm your subscription
BigDataCloud	Your phone's IP address; for buyers who attach a location and when OpenStreetMap does not answer, that point	To look up the seller's approximate location (section 2), and to name the area of a buyer's pin (section 3)
India Post (api.postalpincode.in)	A 6-digit PIN code a buyer types (only the digits)	To show the area that PIN belongs to (section 3)
OpenStreetMap Foundation (Nominatim)	The point of a buyer's attached location	To name the area, city and PIN code of that point (section 3)
Search engines	The address and public details of live stores	So customers can find stores; we list live stores in our sitemap and notify search engines when a store changes. Paused stores are not listed
Google Sheets, in the seller's own Google Drive (only if they connect it)	Each new order, and orders from the last 30 days when connected (section 7)	To keep the seller's orders in their own spreadsheet
Software a seller connects (only if they turn it on)	Each new order (section 7)	To send orders into the seller's own systems
Meta (only on stores whose seller turns on Meta Pixel)	That the store page was viewed (and the product, from a product's own link), a cart started, checkout opened or an order placed, with the order's total and currency; and what a browser sends to any website (IP address, browser details, Meta's cookies) (section 3)	So the seller can measure their Facebook and Instagram ads; in the EEA and the UK only after the buyer taps Allow
Authorities	What the law requires	When we are legally required to

6. Payments and subscriptions

OrderPage offers paid plans. Depending on your phone and country, you pay through Google Play Billing, the Apple App Store, or (on Android in India) UPI through PhonePe using BinaryScript's payment service. We do not receive or store your card, bank or UPI PIN details; those are handled by Google, Apple or PhonePe under their own privacy policies. We keep a record of your plan and when it ends.

7. Sending orders out of OrderPage

Sellers can choose to have each new order also sent to a Google Sheet, to their own software, or both (Settings › Send your orders). Nothing is sent anywhere until the seller turns it on.

To a Google Sheet

When you tap Connect Google Sheet, Google asks you to let OrderPage “see, edit, create and delete only the specific Google Drive files you use with this app”. This permission (Google's drive.file access) covers only the files OrderPage creates. OrderPage cannot see, open or change any other file in your Google Drive, and it does not receive your Google contacts, email or other account data through this connection.

OrderPage then creates one spreadsheet in your Google Drive, adds your orders from the last 30 days, and adds each new order as a row within seconds. Each row holds the order's date and time, order number, the buyer's name, phone number and delivery address, the items, quantities and prices, the total, the delivery date, the buyer's answers to your questions, any note, and the order's ID. It does not include the buyer's map location.

To add rows while your phone is off, we keep a Google access token for your sheet on our servers, in a place no app can read, including yours and your team's. We use it only to add orders to the sheet OrderPage created, and we never read the sheet's contents back. The sheet belongs to you: you can share it, edit it or delete it in Google Drive like any of your files.

Tap Stop adding orders (or use a different Google account) and we ask Google to cancel the permission and delete the token straight away. Deleting your OrderPage account does the same. The sheet and its rows stay in your Google Drive until you delete them. You can also remove OrderPage's access at any time in your Google Account (Security › Your connections to third-party apps and services).

OrderPage's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use this access only to create your orders sheet and add your orders to it. We do not use it for advertising, we do not sell it or pass it to anyone else, and no person at OrderPage reads it, except when you ask us to help, when needed for security, or when the law requires.

To your own software

If you choose to connect your own billing or delivery software, OrderPage sends each new order placed on your store to the web address you provide. Each order includes the order number, date and time, the buyer's name, phone number and delivery address, the items, quantities and prices, the buyer's answers to your questions, the delivery date, any note, and the order total. It does not include the buyer's map location. Nothing is sent until you set this up, and you can turn it off at any time. Once delivered, this information is held in the software you chose and is governed by its owner's terms and privacy policy; you are responsible for how it is used there.

Each order we send is signed with a secret key so your software can confirm it came from OrderPage. The key is stored in your OrderPage account, where only you can see it (your staff cannot), and it is deleted when you turn the feature off. The key does not give anyone access to your OrderPage account.

For buyers: if the store you order from has connected a Google Sheet or its own software, your order details are also passed there so the seller can prepare and deliver your order.

8. Where information is stored

We store information with Google Firebase and Google Cloud. Google may process it on servers outside your country, including in the United States, under Google's own safeguards. See Google's privacy policy.

9. How long we keep information

Stores, orders and business records: while the store exists. They are deleted when the seller deletes their store and account.
Sign-up contact details and subscription status: while the account exists, and deleted with it.
Google Sheet access token: until the seller stops adding orders, switches Google account, removes OrderPage's access in their Google Account, or deletes their OrderPage account. The sheet itself is the seller's file in their Google Drive.
App usage, performance and crash data: kept by Google for the periods set in Firebase, then deleted automatically.
Information on a buyer's own device: until the buyer clears their browser data.
Payment records: as long as the law requires us to keep them.

10. Deleting your information

Sellers: in the app, go to Settings › Delete my store and account. This permanently deletes your store, its link, its orders and records, your team access, any other stores you own, your sign-up details, and your account, and cancels any Google Sheet connection. A sheet already in your Google Drive stays there for you to keep or delete. You can also read how deletion works, or ask us to do it, at orderpage.app/delete-account.

Buyers: to correct or delete an order, contact the seller you ordered from; they can see and manage it. You can also email us with the store's link and the order details and we will help.

11. Your rights

You can ask us to tell you what information we hold about you, correct it, or delete it, and you can withdraw consent you have given (for example by removing a connected Google account, stopping orders to a Google Sheet, or turning off a connection to your software). Depending on where you live, you may have further rights under laws such as India's Digital Personal Data Protection Act, 2023. To use any of these rights, or to raise a complaint, email our grievance officer at nk92.iit@gmail.com. We aim to respond within 30 days.

12. Security

Information travels over encrypted connections (HTTPS) and is stored on Google's infrastructure. Access to each store's private data is limited by security rules to the store's owner and the team members they approve. No system is perfectly secure, so please keep your recovery code private: anyone with it can take over your store.

13. Children

OrderPage is meant for businesses and their customers, not for children under 13 (or the minimum age in your country). We do not knowingly collect information from children. If you believe a child has given us information, contact us and we will delete it.

14. Changes to this policy

We may update this policy as the app changes. When we make an important change, we will update the effective date above and, where appropriate, tell sellers in the app.

15. Contact

Questions, requests or complaints: nk92.iit@gmail.com (BinaryScript, Bangalore, India).