Security

Last updated 29 September 2026

How Hello Beta protects household data and what it deliberately does not keep.

Linking a Swiggy account

You sign in on Swiggy’s own page. Your Swiggy password and one-time code go to Swiggy and never to Hello Beta.

We keep one access token per household, on our server. The apps cannot read it. Linking again replaces it. To disconnect, write to us and we will remove it.

Access is limited to the household

The apps require sign-in, and each household can see only its own calls and orders. Family members can see order details, including the delivery address, but not the masked delivery contact number.

Our operators can access data to run the service and investigate problems, so household controls do not mean that operators or service providers never process it. The privacy policy lists what is collected and who handles it.

Payment and confirmation

Hello Beta supports cash-on-delivery ordering and does not collect card, bank or UPI details. The assistant reads the basket and total back and asks for spoken confirmation. A confirmed scheduled booking may be processed later.

Audio, transcripts and consent

Call audio is sent to Sarvam AI, which runs the voice assistant. Hello Beta’s apps and server do not save call audio, but written transcripts are kept in our database. We have opted out of Sarvam using our calls to train its models.

The person using the voice app should understand and agree to this. The family member who sets Hello Beta up accepts on the household’s behalf and confirms they have explained the app to that person. See consent in the privacy policy before setting the app up for someone else.

Wake word and voiceprint

Hello Beta is tap-to-talk. Builds with the wake word enabled also detect “Hello Beta” and an enrolled speaker using models that run on the phone. The voiceprint stays in the phone’s private app storage. Pairing prompts use the phone’s speech services, which may process audio off the device.

Development builds can save short wake-word clips on the phone when a build option is enabled. This is separate from call audio and is off in household builds. We will not enable it on someone’s device without explaining it and getting their agreement.

Diagnostic records can include order identifiers, totals and failure details, so we do not describe them as free of personal data.

Retention and deletion

We keep records until you ask us to delete them. Deleting a household removes its calls, transcripts, diagnostics, orders, schedules, pairing records, notification registrations and grocery credentials. Sign-in accounts, invitations, backups and provider-held copies need separate steps, which we go through with you. Deleting Hello Beta records does not delete your Swiggy account or its orders.

We aim to handle deletion requests within 30 days and confirm the outcome by email. See how to request deletion and retention in the privacy policy.

Hosting and this website

Our server and database are in India. Some providers that handle speech, notifications, crash reports and website visits may process data outside India.

This website uses Google Analytics and Microsoft Clarity. Fonts are served from this site. A Content Security Policy restricts what pages can load, and browser policies restrict framing, microphone, camera and location access. See website data in the privacy policy.

Reporting a problem

Write to contact@hellobeta.co. A person reads security reports. There is no bounty programme.