Privacy Policy

Orbo is a service for businesses that take orders, deliver them and keep stock. It is operated by Tiruvi (“Orbo”, “we”).

This policy covers three groups of people, and says which hat we wear for each:

• Business users: owners and staff who sign in to Orbo. For their account data, Orbo decides how it is used.
• Drivers: people who use the driver screen to run deliveries. A business invites them; Orbo processes their data for that business.
• Customers of a business: people who place an order with a business that uses Orbo, or who open a tracking page. The business decides why their data is collected; Orbo processes it on the business's behalf. If you are a customer, the business you ordered from is your first contact for questions about your data.

• Account data: name, email address, phone number, role, and the workspaces and outlets you belong to.
• Order data: a customer's name, phone number, email, delivery address and map location, the items ordered, slots, notes, stage history, and proof-of-delivery codes.
• Driver location: while a driver is on a run, the phone sends its position so the dispatch board, routes and tracking page stay live.
• Payment records: amounts, status, method and references for online, QR and cash payments, and refunds. A business connects its own Razorpay account; we store the keys it gives us to do that, and we do not store full card numbers.
• Inventory and operations data: items, suppliers, stock movements, bills and settings a business enters.
• Technical data: API keys and request logs, webhook delivery logs, and basic device and browser information needed to keep the service secure.
• Questions you ask Orbo's assistant, and its answers, which are logged for the business.

• To run the product: take orders, assign and route drivers, show tracking, produce bills and forecasts, and send webhooks to the business's own systems.
• To authenticate users, control what each role may see and do, and keep an audit trail of who changed what.
• To secure the service, investigate abuse and fix faults.
• To answer support requests and send service messages such as sign-in and billing notices.

A driver's position is shown to a customer only while that driver is on the way to that customer, and only on that customer's tracking page. Businesses see driver positions on their dispatch board while runs are active.

Addresses are turned into map positions, and routes and travel times are calculated, by mapping providers listed below.

We do not sell personal data. We share it only as follows:

• The business whose order or account the data belongs to, and the staff and drivers it authorises.
• Service providers that help us run Orbo, each given only what it needs: Vercel (hosting), Neon (database), Clerk (sign-in), Razorpay (payments, through the business's own account), Google (the AI model behind Ask Orbo, which sees only the figures and records a question needs; and, where a business has set it up, geocoding and routes), OpenStreetMap services, Nominatim and OSRM, for addresses and routes where Google is not used, and OpenFreeMap, whose map tiles your browser fetches when you open a map (so it sees your IP address and the area you are viewing).
• Connected systems: a business can connect its website, WhatsApp, Corva or its own server through the API and webhooks. Data sent there is governed by that business's own policies.
• Authorities, where the law requires it, or to protect rights, safety and the security of the service.

A business's orders, bills, payments and stock are kept while it uses Orbo. When an owner closes the business in Orbo, all of it is deleted at once, bills included, so the owner downloads the bills first; copies in our database backups are gone within 30 days. A driver's live position is kept for a week. When you create a business we also note which version of this policy you were shown, and when. Questions asked of Orbo's assistant, webhook delivery logs and the log of events from Corva are kept for a year, the minimum the law sets for logs of processing, then deleted.

Access is limited by role, who opens an order is logged and kept for a year, API keys are scoped to a business, webhooks are signed, data is encrypted in transit and at rest, and the payment keys a business gives us are sealed with a key only the service holds. No system is perfectly secure; if we learn of a breach affecting your data, we will tell the affected business and, where required, the authorities, without undue delay.

Depending on where you live, including under India's Digital Personal Data Protection Act, 2023, you may ask to see, correct, export or delete your personal data, to withdraw consent, to name someone to act for you if you cannot, and to complain to the Data Protection Board of India (or the authority where you live) if we do not resolve it.

Deleting, yourself: anyone with a login deletes it under Your account (the picture at the top right). An owner closes a business in Settings, downloads everything held about a customer who asks to see it, and erases a customer who asks to be forgotten from one of their finished orders; their name, numbers and address go, while issued bills, which are tax invoices, stay as issued. A customer erased in a connected Corva is erased here too.

If you are a customer of a business, please contact that business first; we will help it respond. For account data, or if you cannot reach the business, use the data request page or our contact form. Cookies and browser storage are listed on the Cookie Policy.

Orbo is meant for businesses and is not directed at children. We do not knowingly collect data from anyone under 18 for our own purposes.

Our providers may process data in countries other than your own. Where we transfer personal data, we do so under the safeguards the applicable law requires.

When we make a material change, we will update the date above and, for business users, tell you in the product or by email before it takes effect.

Tiruvi · Contact us. Questions and complaints about your data go here; a person answers.