Privacy Policy

Who this policy covers

This Privacy Policy explains how Ankaavi Technologies Private Limited handles personal data through KnownSense Intelligence, including the public website, the public demo upload flow, and customer workspaces used for call quality monitoring.

• KnownSense Intelligence is a business product for call quality, script review, coaching, reporting, and operational oversight.
• For customer workspaces, the customer normally decides what call data is provided and why it is processed. KnownSense acts as a processor or service provider under the signed customer agreement.
• For the public website and public demo, Ankaavi controls the limited data needed to provide the website, run the demo, protect the service, and respond to inquiries.

Data we may process

• Account and contact data, such as name, business email, organization, role, login details, and support communications.
• Call and QA data submitted in a customer workspace, such as recordings, transcripts, summaries, scores, flags, scorecards, coaching notes, agent identifiers, call metadata, and review actions.
• Public demo data, such as the uploaded audio file, file metadata, temporary demo result, browser fingerprint or security token, IP-derived request context, and abuse-prevention signals.
• Usage and security data, such as device type, browser, session events, audit records, diagnostics, consent choices, and feature usage events.
• Billing and vendor onboarding data where applicable, such as business identifiers, invoices, payment status, and tax details once provided.

How we use data

• To provide call transcription, QA scoring, review queues, dashboards, reports, coaching workflows, account access, and support.
• To run public demo evaluations for users who choose to upload authorised sample, synthetic, anonymised, or otherwise lawful audio.
• To secure the service, prevent abuse, investigate incidents, preserve audit trails, and enforce usage limits.
• To improve reliability, user experience, and product operations using privacy-conscious analytics where consent or another lawful basis applies.
• To comply with law, customer contracts, valid requests from authorities, and internal governance obligations.

Public demo upload limits

The public demo is a lightweight evaluation flow. It is not intended for sensitive, regulated, confidential, or production customer recordings.

• Do not upload financial account information, payment card data, government ID numbers, health data, child data, policyholder disclosures, third-party confidential information, or any audio you are not authorised to process.
• Demo audio is deleted after processing or expiry. Demo results are temporary and may be retained only for the configured result window needed to show the evaluation and protect the service.
• The demo result is indicative only. It is not a compliance decision, legal opinion, employment decision, or final QA determination.

Customer call data

Customer recordings and derived QA outputs should move to KnownSense only under a signed customer agreement, proof-of-concept agreement, data protection schedule, or equivalent written arrangement.

• We process customer call data only for agreed business purposes, such as call review, scoring, reporting, coaching, troubleshooting, security, and support.
• Customer agreements should define the permitted call types, business lines, retention period, subprocessors, breach process, and exit or deletion procedure.
• Unless expressly agreed in writing, customer recordings, transcripts, scorecards, and coaching outputs are not used to train, fine-tune, or improve models for other customers.

Retention and deletion

• Public demo audio is intended to be deleted after processing or expiry. Public demo results are temporary.
• In customer workspaces, normal recordings are deleted after analysis unless a customer agreement or flagged-review policy requires a longer review window.
• Flagged recordings, transcripts, analyses, reports, coaching records, billing records, audit logs, and security records may follow different retention periods as described in the product, customer agreement, or legal requirements.
• When the agreed purpose ends, we delete or return customer personal data according to the applicable agreement, unless retention is required by law, security, billing, dispute, or audit obligations.

Subprocessors and service providers

KnownSense may use vetted vendors for hosting, storage, security, analytics, communications, AI processing, and support operations. The actual subprocessors for a customer proof of concept or production deployment should be disclosed in the signed agreement or diligence pack.

• We do not authorise subprocessors to use customer call data for their own independent marketing or unrelated product training.
• Where customer data is processed by a subprocessor, we aim to bind that provider to confidentiality, security, purpose limitation, and retention controls appropriate to the service.
• Customer-specific subprocessor restrictions should be handled in the data protection schedule before live recordings are shared.

Security and incidents

• We use access controls, tenant-aware product design, secure transport, restricted administrative access, operational logging, and deletion workflows to protect the service.
• No public statement on this website should be read as a claim that Ankaavi currently holds ISO 27001, SOC 2, or an equivalent certification unless that certification is expressly published or provided in writing.
• Security incidents and personal data breaches should be reported to us at the contact address below. Contracted breach-notification timings may be stricter than this public policy.

Your rights and contact channel

Where applicable, individuals may request access, correction, completion, updating, erasure, grievance redressal, or withdrawal of consent under the Digital Personal Data Protection Act, 2023 and related rules once in force.

• For privacy, grievance, legal notice, or security communications, email admin@knownsense.ai.
• If your data was submitted by one of our business customers, we may route the request to that customer because they control the purpose and scope of processing.
• We may need reasonable information to verify and process a request, protect other users, or comply with legal obligations.