Privacy Policy

Last updated 2 October 2026

Hello Beta is operated by HELLOBETA PRIVATE LIMITED, a private company incorporated in India (CIN U58201TS2026PTC222888), with its registered office at 8-3-1062, Flat No. 501, Plot No. 15, Jyothi Palace, Srinagar Colony, Khairatabad, Hyderabad 500073, Telangana, India. “We” and “us” in this policy mean that company. This policy explains what personal data Hello Beta collects, why, who handles it, how long we keep it, and how you can control it.

In short

What we collect: household and sign-in details, what is said and ordered on calls (as written text, not saved audio), delivery addresses, and app diagnostics.
Why: to take and place grocery orders by voice, show the family what happened, and fix problems.
Who else handles it: a small set of service providers, listed in section 6. We do not sell your data or use it for advertising.
Your control: you can ask to see, correct or delete your data, or withdraw your consent, at any time (section 8).
Contact: contact@hellobeta.co. A person will answer.

1. What Hello Beta is

Hello Beta is a voice assistant that takes a spoken grocery order, reads the basket back to the user, and places the order for cash on delivery after spoken confirmation. A companion app lets family members link a household account and see completed orders.

Hello Beta is an invite-only pilot for a small number of households. It places real Swiggy Instamart orders. Features can differ between app builds.

2. What we collect and why

Household details: a household identifier, members’ roles and display names, the language the assistant speaks, the selected delivery address, and ordering preferences (the words the household uses for products and how it likes to order). Why: to run the household’s account and understand its orders.
Sign-in and invitations: the family app uses Google Sign-In, so we receive the account identifier, email address and profile information Google returns. The senior app uses an anonymous identifier instead of an email. We also keep invitation email addresses, who sent them, an optional note, and whether the invitation was used. Why: to let people sign in and join a household.
Calls, baskets and orders: each call’s basket, quantities, total, screen state and start and end times, and each placed order’s items, totals, identifiers and the status Swiggy returns. Scheduled bookings also keep the items, address identifier, quoted amount, scheduled time, confirmation details and outcome. Why: to place orders and let the family review what happened.
Call transcripts: we copy the written text of calls from our speech provider into our database, along with call metrics. Why: to investigate what the user and assistant said when something goes wrong.
Delivery address on an order: the address an order was sent to, as a line of text, with the identifier your grocery account uses for it. The phone number attached is the masked number Swiggy issues for the delivery agent, not your own, and the companion app cannot read it. Why: to show and support the order.
Grocery account token: if you connect a Swiggy account, the access token Swiggy issues (section 5). Why: to place orders on your behalf.
Notification details: if a family device registers for notifications, its push token, sign-in and household identifiers, platform, registration times and delivery errors. Why: to send order updates and stop sending to rejected tokens.
Diagnostics and crash reports: call and tool events, timings, outcomes, failure details, pairing and checkout attempts, and crash and error reports. Some records include order identifiers or totals. Crash reports leave the device with console logs removed and the signed-in user reduced to an internal identifier. Why: to find and fix problems.
Device measurements: which screen the app reached, which build it runs, and, when the wake word is in use, two scores per utterance: how strongly the sound matched “Hello Beta” and how strongly it matched an enrolled voice. These are numbers, not audio or text, but they are derived from a voice, so we treat them as belonging to the household. Why: to improve the wake word and detect problems.

3. What we do not collect

Payment details. Orders are cash on delivery. We never take or store a card number, bank detail, UPI identifier or any other payment instrument.
Saved call audio. Our apps and server do not save call audio. During a call, speech is sent to our speech provider (section 6). We keep the written transcript.
Camera images. The family app uses the camera only to read the pairing code shown on the senior’s phone: no photo or video is saved or sent anywhere, and the microphone is never used for scanning. A family member can also join with the share link, without the camera.
Data for advertising. We do not sell personal data or build advertising profiles.

The person who sets Hello Beta up is often not the person it listens to: a family member installs it on a parent’s phone. That family member accepts our terms and this policy in the companion app on behalf of the household, and confirms they have explained the app to the person who will speak to it: that speech is sent for processing, that written transcripts and order records are kept, and that family members can see household order information. We record that acceptance with the policy version, the language shown, the time, which family member accepted, the household, and their confirmation.

Listening. Hello Beta is tap-to-talk. Builds with the wake word enabled also listen on the phone for “Hello Beta” using models that run on the device; that audio is not uploaded. Pairing uses the phone’s own speech recognition and text-to-speech, which may process audio off the device depending on the phone and its settings.

Voiceprint. Enrolling a voice reduces a few spoken examples to a short numerical profile used to recognise that voice later. It is biometric-derived data, so we handle it with care: it stays in the app’s private storage on the phone, is not uploaded to us, and the recordings it was made from are not kept. Uninstalling the app removes it.

Wake-word clips. The app can be built to save short clips of what the microphone heard, to improve wake-word accuracy. This is off in the builds given to households. If it is ever turned on for a device, the clips stay on that phone, and we will tell the person and ask for their agreement first.

Withdrawing consent. The person Hello Beta listens to, or the family member who accepted, can withdraw consent at any time by telling any family member or writing to contact@hellobeta.co. We act on the request whoever makes it, and it is treated as a request to delete the household’s data (section 7).

5. Linked Swiggy accounts

You connect a Swiggy account by signing in on Swiggy’s own page with your phone number and a one-time password. Your Swiggy password and that one-time password go to Swiggy and never to us.

What comes back is an access token, which we use to fetch saved addresses and products, manage the basket, place confirmed orders and read order status. We keep one token record per household, replaced each time you link again, together with the account identifier Swiggy returns and the token’s expiry. Only our server can use it. You will need to link again when the token expires or Swiggy rejects it.

To disconnect, write to contact@hellobeta.co. We aim to remove the token within 30 days and confirm by email. Disconnecting does not cancel orders already placed with Swiggy.

6. Who else handles your data

Sarvam AI turns speech into text and runs the voice assistant, so it receives call audio, conversation text and the context we supply. It keeps them under its own policies, and may process them outside India. We have opted out of Sarvam using our calls to train its models. We also retrieve call transcripts and metrics from Sarvam.
Our database and sign-in provider stores household records and handles sign-in and live screen updates. The data is held in India.
Our website and network provider serves this website and carries our server’s traffic.
Google handles family-app sign-in. Google Play also delivers the pairing code from a setup link to the senior app on first install (the Play Install Referrer) so the phone can pair itself.
Expo delivers push notifications, so it receives device tokens and notification text, which can include basket descriptions, totals, order identifiers and failure messages. Delivery then goes through Google’s or Apple’s push service.
Sentry (Functional Software, Inc.), EU region, receives crash and error reports from both apps. Audio, transcripts and order contents are not attached to them.
Swiggy receives the requests and orders we send for you, under its own terms and privacy policy. Ask Swiggy directly about data it holds.
Your phone’s speech services speak and recognise pairing prompts.
Our operators view household and call information through an access-controlled dashboard, and our server runs in India. Email you send us is handled by your email provider and ours.

Some of these providers process data outside India. We share data only to run Hello Beta, and we do not sell it.

7. How long we keep data, and deletion

We keep household, call, order, transcript and diagnostic records until you ask us to delete them. We do not currently delete them on a schedule.

To delete your data, write to contact@hellobeta.co. There is no charge and we will not ask why. We aim to act within 30 days and confirm by email. The account deletion page explains what to include. Deleting a household removes its calls, transcripts, diagnostic records, placed and scheduled orders, pairing records, push registrations and grocery credentials. Device measurements linked to the household are removed with it.

When we handle a deletion request we also review sign-in accounts, invitation emails and notes, and any transcripts or device events that could not be linked to the household, and remove them. Backups, support email and copies held by service providers are outside that step; write to us if you want those addressed. Stopping use of the app or uninstalling it does not by itself delete stored records.

8. Your rights

Under India’s Digital Personal Data Protection Act, 2023, you can ask us to:

tell you what personal data we hold about you and who we share it with;
correct data that is wrong or out of date;
delete your data (section 7);
withdraw your consent (section 4);
nominate someone to exercise these rights for you if you die or cannot act.

Write to contact@hellobeta.co for any of these. If we have not resolved your concern, you can complain to the Data Protection Board of India.

9. Security

Data is sent between the apps, our server and our providers over encrypted connections, and access to stored data is limited to our server and our operators. No system is perfectly secure, so we limit what we collect and who can see it.

10. This website

This website carries two analytics tools, the only third-party code on it. Google Analytics 4 counts visits and shows which pages are read. Microsoft Clarity records how a page is used (clicks, scrolling and the general shape of a session) so we can see where our wording confuses people. Both set cookies and receive your IP address. We do not use this information for advertising or sell it, and Google and Microsoft handle it under their own terms. Neither is in the Hello Beta apps, and nothing said to the assistant reaches them.

The website has no account, login or form. Blocking either tool with a browser content blocker does not change how the pages work. The service that hosts this site processes standard request information such as your IP address to deliver pages and defend against abuse. Fonts are served from this site, so no font provider learns that you read this page.

11. Children

Hello Beta is not intended for children, and we do not knowingly collect information from children.

12. Changes to this policy

If we change what Hello Beta does with personal data, we will update this page and the date at the top.

13. Contact

contact@hellobeta.co
HELLOBETA PRIVATE LIMITED
8-3-1062, Flat No. 501, Plot No. 15, Jyothi Palace, Srinagar Colony, Khairatabad, Hyderabad 500073, Telangana, India