Privacy Policy

Effective date: 10 September 2026 · Applies to naadham.ai, the Naadham customer console, APIs, and the Naadham AI voice/messaging services.

We may change this Privacy Policy at any time, including without prior or individual notice to users. The current version is the one posted on this page. Continued use of the Services after a change is posted is acceptance. See §11.
The two-role summary. Naadham has two very different privacy roles: (1) for customer accounts and website visitors we are the data fiduciary / controller — we decide how that data is used; (2) for callers and end-users of our business customers (call audio, transcripts, bookings and service requests) we are a data processor / service provider — the customer business is the controller/data fiduciary and we act only on its instructions under our Data Processing terms. Callers: your first point of contact for privacy requests is the business you called; we support every request they pass to us.

1. Who we are

Naadham is operated by Vistraal Private Limited, a company incorporated in India ("Naadham", "we", "Vistraal"). Contact: [email protected]. Grievance Officer (India DPDP Act 2023 & IT Act 2000): reachable at [email protected], postal address as above — we acknowledge grievances within 24 hours and resolve within applicable statutory timelines.

2. What we process, and why

2.1 Website visitors (we are controller)

DataPurposeLegal basis
Demo call/chat content, mic audio during a browser demorun the live demo you startconsent (you start it)
"Call me" form: name, phone, interest, consent record, IPplace the demo call you requested; abuse preventionconsent; legitimate interest (fraud/abuse)
Contact form: name, email, messagerespond to youlegitimate interest / consent
Technical logs (IP, user-agent, timestamps), rate-limit counterssecurity, abuse prevention, debugginglegitimate interest

2.2 Customer businesses and their staff (we are controller)

DataPurposeLegal basis
Account: work email, organisation name, hashed password, roleprovide the service, authenticationcontract
Configuration: agent persona, FAQs, schedules, directory, phone numbers, documents you uploadoperate your AI receptionistcontract
Billing: plan, subscription term, minute balance, usage metering, payment referencesbilling and receipts (card data is held by our payment processors, never by us)contract; legal obligation (tax)
KYC/verification documents and statustelecom-compliance and account verificationlegal obligation / legitimate interest
Support communicationssupportcontract

2.3 Callers of customer businesses (we are processor on the customer's instructions)

DataPurpose
Call audio (processed in real time), optional call recordings when enabled, transcripts, caller phone number and name, call metadata (time, duration, outcome, brief call summary)answer the call, take bookings or service requests, and show transcripts/recordings/summaries to the customer
Booking / enquiry details: name, phone, service, preferred time, notescreate or request the appointment or enquiry the caller asked for
WhatsApp/SMS/web-chat messages with the customer's AIrespond on the customer's behalf
Consent and do-not-call records for outbound callslawful-calling enforcement (see §7)

Sensitive or health information. Conversations may incidentally include health or other sensitive information a caller chooses to share. We process it solely to provide the service to the customer, apply strict access controls, and our AI is instructed and designed not to provide medical diagnosis or treatment advice. The customer remains the controller of caller/patient data.

3. AI processing — the honest specifics

4. Service providers & recipients

We share data only with infrastructure, telephony and AI providers needed to run the Services — never for advertising, and we do not sell or "share" (as defined by the CCPA) personal information. We may change, add or replace those providers at any time as operationally required, without individual notice to users, except where mandatory law that cannot be waived requires otherwise. We may also disclose data when required by law or to protect rights, safety, or the integrity of the service, and in a merger, financing or acquisition (with continuity of this policy's protections to the extent required by law).

5. Where data lives & international transfers

Application compute for production voice and the customer portal runs primarily in India (Google Cloud, asia-south1). Application database hosting may use managed Postgres (currently including Neon in Singapore) and certain AI/telephony providers may process data in the US, EU or other regions. For customers in the UK/EEA we offer the UK IDTA/Addendum and EU Standard Contractual Clauses (2021) as part of our Data Processing terms where those terms apply. Hosting and provider locations may change as we operate and expand the service.

6. Retention

DataRetention
Live call audioprocessed in real time to operate the call
Call recordings (when enabled)stored by the telephony carrier (e.g. FreJun for India) under that carrier's retention; Naadham stores an authenticated recording reference and proxies playback to the authorised customer account — we do not permanently re-host a second copy of the audio file
Transcripts, bookings, enquiries, contacts, QA scores, call summariesfor the life of the customer's account, or until the customer deletes them (self-service deletion tools are provided)
Consent recordsup to 3 years after last activity (legal defence of lawful-calling)
Do-not-call entriesindefinitely as a suppression record (removing them would risk calling you again)
Account/billing recordsas required by tax law (typically 7–8 years in India)
Website demo/lead dataup to 12 months
Security logsup to 12 months

7. Your rights & choices

Everyone: opt out of automated calls permanently at any time — tell the AI to stop calling, or use the do-not-call endpoint/form; the number is suppressed on every outbound path.

India (DPDP Act 2023): access, correction, erasure, grievance redressal, nomination. Contact the Grievance Officer (§1). EEA/UK (GDPR): access, rectification, erasure, restriction, portability, objection; complain to your supervisory authority (or the ICO in the UK). California (CCPA/CPRA): know, delete, correct, opt out of sale/sharing (we do not sell or share), non-discrimination. Other regions: we honor the strongest applicable rights in practice.

How: customers exercise rights in-product (export and deletion tools in the console) or by email; callers contact the business they called (the controller) — and we act on that customer's instruction, or forward your request to them if you contact us directly. We respond within 30 days (or shorter statutory periods). Identity verification is required for requests. We may refuse or limit requests that are manifestly unfounded, excessive, or that would compromise security, other people's rights, or records we must keep by law.

8. Cookies & similar technologies

The website and console use no advertising or analytics cookies. We use: (a) localStorage for your sign-in session and interface preferences (functional, not shared); (b) Cloudflare Turnstile for bot protection on public forms (may set its own functional cookie under Cloudflare's policy); (c) our payment processors' scripts during checkout; (d) a first-party visit counter on public pages, which keeps a "seen before" flag in your browser's storage and sends us only the page path and referring site — we store hourly totals, never an identifier or IP address. Because we use no non-essential trackers, no cookie-consent banner is required; if that changes we will add one.

9. Security

Per-tenant isolation enforced with database row-level security; passwords stored as salted PBKDF2 hashes; session tokens and API keys stored only as hashes; stored provider secrets encrypted at rest (Fernet/AES); TLS in transit; constant-time credential comparisons; role-based access (staff logins are read-only); rate-limiting and abuse guards on all public endpoints; infrastructure access limited to authorized operators. No method is 100% secure; we notify affected customers and authorities of personal-data breaches as required by law. For our Indian operations that means reporting covered cyber incidents to CERT-In within six hours of noticing them, as its 2022 directions require; where GDPR applies, the supervisory authority is notified within 72 hours; DPDP notifications follow the Data Protection Board's rules as they come into force.

10. Children

Our services are B2B and not directed to children. A caller of a customer business may be a minor whose parent/guardian books on their behalf; the customer controls such data. We do not knowingly collect children's data for our own purposes.

11. Changes

We may change this Privacy Policy at any time, including without prior or individual notice to users. The current version is the one posted on this page with its effective date. It is your responsibility to review this page periodically. Continued access to or use of the Services after a revised Privacy Policy is posted constitutes acceptance of the updated policy. Where a mandatory law that cannot be waived requires a specific form of notice, we will comply with that law only to the minimum extent required.

12. Contact

Privacy requests: [email protected] · General: [email protected] · Grievance Officer (India): §1. EU/UK representatives will be listed here once appointed.