Privacy Policy
Last updated: 19 July 2026
1. What we collect
Account data
Your name, work email, username, organisation name, role and password hash. We never store your password in readable form.
Customer content
The call recordings, transcripts, quality parameters and SOPs you upload, and the audits generated from them — including transcripts, translations, scores, evidence quotations, sentiment analysis and coaching notes.
Usage and billing data
Credit balance and deductions, audit counts, processing times, AI token usage, payment records and invoices. We also keep standard server logs such as IP address, browser type and timestamps for security and debugging.
2. How we use it
- To run audits and deliver results to your workspace.
- To meter credits and process payments.
- To secure the service, investigate abuse and diagnose faults.
- To send transactional email — verification, password reset, receipts and low-balance alerts.
We do not sell your data, and we do not use your call content to train our own models.
3. Sub-processors
Delivering the service requires sharing data with the following providers:
- Google (Gemini API)— call audio and transcripts are sent to Google's generative AI service to produce transcription, translation, scoring and analysis. This is the core of the product: audits cannot be produced without it.
- Razorpay — payment processing for credit purchases. Card details are handled by Razorpay and never reach our servers.
- Email delivery — our SMTP provider sends transactional messages.
- Hosting and infrastructure — the servers and databases the application runs on.
TODO: confirm the hosting region and whether data leaves India, and name the SMTP and hosting providers explicitly. Enterprise buyers routinely ask for this in a Data Processing Agreement.
4. Personal information in transcripts
Calls frequently contain personal information. As each transcript is produced, the system is instructed to mask identifiers including phone numbers, postal addresses, email addresses, card numbers, CVV and expiry, bank account numbers, Aadhaar, PAN, UPI IDs, IFSC codes, dates of birth, OTPs and passwords. Speaker names are deliberately left readable so audits remain usable.
This masking is best-effort and is not a guarantee. It is performed by the AI model during transcription rather than by a deterministic redaction pass, so it can miss identifiers or mask imperfectly. If you operate under a strict regulatory regime, evaluate it against your own requirements before relying on it, and avoid uploading content you cannot risk being retained in readable form.
5. Retention
Customer content is retained for as long as your workspace is active, so that historical audits stay available for trend analysis and coaching. You can request deletion of specific audits or of your whole workspace at any time by contacting us. Billing records are kept for as long as tax and accounting law requires.
TODO: confirm a specific retention period for call audio and for deleted-workspace backups.
6. Security
- Traffic is encrypted in transit over HTTPS.
- Each tenant's data is isolated, and access is enforced by role-based permissions on every request.
- Passwords are stored only as salted hashes.
- Payment card data is handled entirely by our payment provider.
No system is perfectly secure. If we become aware of a breach affecting your data, we will notify you without undue delay.
7. Your rights
Subject to applicable law, including India's Digital Personal Data Protection Act, you may request access to, correction of, or deletion of your personal data, and may withdraw consent where processing rests on it. Because we process call content on your instructions, requests from people recorded on your calls should be directed to you as the controller; we will assist you in responding.
To exercise a right, email support@assureqai.com.
8. Changes
We will post updates to this policy here and, where the change is material, notify you directly.