Privacy

When a customer sends a shopping list, the store receives their name, mobile number, delivery address, landmark, any delivery instructions, the list itself and the notes on it. Later the store adds the invoice details and how payment was collected.

Email addresses are not required anywhere in the customer flow. Customers do not create an account and do not set a password.

Only staff of that one store. Every record in OrderDesk belongs to exactly one store and the database refuses to return another store's rows, regardless of what the application asks for.

Within a store, access still narrows by role. Delivery staff see only the orders assigned to them — the address, the amount and how to collect it — and never other customers, internal notes or analytics.

Each order gets a long random link. Anyone holding that link can see that order's status, list and invoice, which is why the store should send it only to the customer. Order numbers are never enough on their own, and OrderDesk stores only a hash of the link, not the link itself.

No marketing profiles, no loyalty scoring, no advertising, no selling or sharing of customer data, and no automatic subscription to promotions. Customers are not asked for consent to anything beyond preparing and delivering their order.

Techvora, which operates OrderDesk, sees store, plan and usage counts. Reading a store's actual orders requires that store's owner to grant timed support access, and every such access is recorded.

A store owner can archive old orders and set a retention period. Invoice retention requirements differ by state and by business, so the right period is the one the store's accountant advises — OrderDesk deliberately does not assume one.

A delivery address can be cleared from an old order while the accounting reference is kept. For any request about their own data, a customer should contact the store they ordered from.