Privacy policy

1. Who this covers

This notice covers HelloBollo account holders, authorised agencies and people submitting a business enquiry. The business receiving an enquiry decides how to fulfil it and whom to contact. It must explain its own use of customer information. Telephone and other connected providers have separate privacy practices.

The operator's legal identity, public privacy/support contact and grievance contact are not yet published. A working request channel, a complete retention schedule and the remaining account-erasure process must be in place before paid activation. The Support page is self-help; it does not send a privacy request.

2. Information and its purpose

The operator's private administration service holds account/access details, usage counts and support notes. Operational records are stored in the site's hosted database. No advertising or analytics service has been added to this app. The app does not train its own AI model on your enquiries.

Do not put identity documents, passwords, OTPs, card security codes or banking credentials into enquiries or business instructions. HelloBollo does not collect KYC documents or card details in its telephone setup flow.

3. Providers and data sent to them

• Test checkout. Opening sandbox checkout loads the payment service’s hosted form and supplies a test order, its amount and currency. The app does not prefill your private profile. Your browser and the hosted service exchange checkout and normal technical metadata. Enter only the provider’s documented test details. HelloBollo verifies returned identifiers on its server and saves a test record for your signed-in account; your operator CRM is not exposed to checkout.
• Authentication and hosting. The identity service processes sign-in, verification and password recovery. The site's hosting and database services process application records and normal network metadata. Sign-in providers supply basic account/profile information needed for your session.
• Telephone service. Your own telephone-provider account handles business KYC, number rental, payments and telephony. HelloBollo currently uses your connected credentials to verify account access and owned numbers, then save the number and language you select. This setup does not change provider routing or import live call events. Any future routing and call-processing activation needs a separate explicit configuration step and its own notice. The India-hosted live speech runtime is not connected; connecting the telephone provider alone does not begin AI audio processing. Before that runtime is activated, its notice must identify where caller audio, transcription and approved business facts are processed and which speech providers receive them. KYC documents, payment details and any recordings held by your telephone provider remain subject to your telephone provider's privacy policy. Deleting a HelloBollo workspace does not delete provider-held records.
• Prerecorded voice guidance. The operator sends generic scripts to a speech-generation service when authoring the small language guides. Playing a finished clip requests a public file from this site; it does not send your personal details, microphone audio or customer text to a speech-generation service. API authoring consumes the operator's credits. Telephone speech is a separate provider flow.
• Business discovery. Name/city lookups go to an external public map-directory service. Map data: © OpenStreetMap contributors. Website checks request a public homepage and robots.txt from the business website; the optional reader path sends the public URL to an external website-reading service. These sources receive ordinary request metadata. Public responses may be cached for up to 24 hours. Private account records, cookies and enquiries are not sent with these checks.
• AI business review. When you request a review, the public website or selected listing text and the business details you enter are sent to an AI review service to prepare business-specific recommendations. If you explicitly choose an owner-provided brief, that brief is sent instead; leave out private customer information. The returned report is held in the current browser view until you choose to save approved notes in your workspace. Public source text can be cached for up to 24 hours; private briefs and AI reports are not placed in that public cache. A daily hash of network metadata and persistent request counters enforce the free review allowance; raw IP addresses are not stored in those counters. Website observations and AI recommendations are shown separately.
• Optional AI drafts. When configured, an AI rehearsal or assessment review sends the submitted conversation/scenario and relevant business configuration to the configured AI service. Fixed-template or guided modes do not make that AI call. A separately enabled private server assistant sends the selected business facts and conversation to the operator's configured model host. Review the selected mode before sharing personal information.

Provider systems may process information outside India; an India-only processing location is not promised. Their policies and the connected account's settings govern their processing and retention. HelloBollo has not verified a zero-retention commitment for connected telephone services.

4. Browser enquiries, microphone and local models

Anyone with a complete active enquiry link can view its approved public business facts and submit a request. After reviewing the details and confirming permission to be contacted, the customer sends the callback form to the business's private queue. Conversation alone does not save a callback. A saved receipt reports the request's recorded progress; it does not confirm a call, booking or completed repair. Keep the complete link and receipt private if you do not want others to use them.

The guided English/Hindi conversation prepares text locally in the current view. The prerecorded welcomes and complete callback guides are available in 11 languages: Indian English, Hindi, Bengali, Gujarati, Kannada, Marathi, Punjabi, Tamil, Telugu, Malayalam and Odia. They need no microphone or model download. These recordings do not establish live telephone speech in those languages; optional interactive speech is a separate English/Hindi feature with its own activation and consent notices. Revoking a link stops future access through it but retains existing requests for follow-up.

Optional on-device recognition and AI require a separate download. In those modes, microphone samples, prompts and generated speech are processed on the device; public model/runtime hosts receive file requests and ordinary network metadata. Model files can remain in your browser cache. Optional personalised on-device readback downloads about 415 MB after activation and acceptance of its model-use conditions.

If the separate hosted browser speech pilot is enabled, its consent notice applies before microphone audio leaves the device. Short recorded replies, relevant business facts and typed conversation can go to the operator's speech server for recognition and spoken replies. The supplied speech service processes these in memory without deliberately saving raw audio or conversation logs. The browser retains current-view conversation and private generated audio until the view is stopped or closed. Hosting infrastructure still handles transient request traffic and metadata. The optional self-hosted telephone bridge has its own temporary audio processing; its failed-delivery outbox can retain a structured request for up to seven days.

5. Access and security

Workspace access checks restrict records to the authenticated owner. Approved public facts are deliberately available through published enquiry links. The operator may process account and support information to maintain access, investigate abuse and respond to lawful requests; infrastructure and connected providers process the data needed to deliver their services.

The telephone-provider Auth Token is encrypted on the server with an owner-bound encryption scheme and is not returned to the customer interface. Submitting these credentials authorises read-only account and owned-number checks; current setup does not place paid calls or change routing. Protect the Auth Token and rotate it in your provider account if compromised, after checking other applications that use it. No system can guarantee absolute security.

Use only customer information you have permission to process. Disclose AI interaction and recording/transcription before live calls and obtain the required consent. Honour refusal, correction and requests for a person. Do not reuse a callback request as permission for unrelated marketing.

6. Retention and your controls

Platform test payment records are kept separately from operational workspace data for transaction verification and replay prevention. Deleting workspace data does not delete these account-linked test records, cancel a payment or request a refund. The existing operator contact and account-erasure limitations below also apply to these records; no live billing is activated by keeping a sandbox receipt.

Saved business, enquiry and follow-up records remain until removed using available controls; a general automatic deletion period has not been configured. Essential account and operator administration records can remain after workspace deletion. No fixed backup-erasure deadline or complete provider-erasure schedule has been verified. These limits must be resolved and disclosed before paid use; this policy does not promise immediate deletion from every system.

• Review and correction: review and edit the business records and settings available in your workspace. Customers should contact the business receiving their enquiry to correct request details.
• Revoke a public link: turn it off in enquiry setup to stop new access. Existing requests remain.
• Disconnect the telephone provider: remove the stored connection credentials and disable its HelloBollo assignments. Manage number rental, application routing, recordings, KYC and charges separately in your telephone-provider account.
• Delete workspace data: Settings → Advanced deletion removes workspace businesses, conversations, callback requests, enquiry links, proposals, bookings, invoices, settings and stored telephone connections. It does not delete the sign-in account, retained operator account profile/support notes, or copies held by external providers. This action cannot be undone.
• Retain your documents: available reports/documents can be downloaded or printed. There is no complete one-click account data export. Copies already downloaded or shared remain with their recipients.

Operational deletion, subscription cancellation, provider cancellation and full account erasure are separate actions. A full account/privacy request channel is not yet published. See the operator-contact notice before submitting sensitive information or paying for activation.

7. Updates and complaints

Policy changes will be published here with a revised date. New uses of information and material service/provider changes must be explained before activation. This notice does not remove privacy or consumer rights available under applicable law or claim certification under a particular law.

For an enquiry-related concern, contact the receiving business. For provider account, KYC, recording or payment concerns, contact your telephone provider through its own account support. Operator privacy/grievance contact details must be published before HelloBollo begins paid subscriptions.