Privacy Policy & Data Security

Ringfence is engineered and operated by AHANAI Pvt. Ltd. ("AHANAI," "Company," "we," "us," or "our"). This policy details our protocols regarding call audio streams, transcripts, encryption standards, and user data governance. It applies to enterprise subscribers and individuals whose calls are audited on a customer's behalf.

1. Zero Model-Training Guarantee

Call audio, transcripts, and metadata are strictly confidential. They are never utilized to train, fine-tune, or benchmark any public or foundation machine learning model — whether operated by AHANAI or any third party. This guarantee applies unconditionally to all enterprise accounts, growth tiers, and trial evaluations. Your call telemetry is processed solely to execute the deterministic rule checks you have established and generate your compliance audit records.

2. Categories of Information Collected

2.1 Call Content & Audio Telemetry

• Audio streams ingested via webhooks or SIP dialer feeds (read-only parallel streams)
• Encrypted verbatim machine transcripts generated during real-time processing
• Operational metadata: call length, timestamp, caller ID hash, agent configuration tag

2.2 Account & Configuration Data

• Contact name, organizational email, and enterprise billing credentials
• Compliance rule definitions, offer sheets, and regulatory disclosure clauses
• Supervisory audit history: manual flag clearing, legal escalations, and reviewer notes

3. Data Retention Windows

Standard retention for transcripts and isolated deviation audio clips is 90 days (Starter), 1 year (Growth), or custom retention periods up to 7 years (Enterprise). Full call audio beyond flagged deviations is retained only when explicitly configured by the customer. Upon account termination, audit data remains available for self-service export for 30 days, after which it is permanently purged from production databases within 14 days.

4. Encryption & Security Architecture

• All data in transit is encrypted using TLS 1.3 with modern cipher suites
• All persistent call records and audio snippets are encrypted at rest with AES-256
• Engineering staff have zero standing access to customer call audio; access requires logged, time-boxed operational authorization
• We undergo third-party penetration testing annually and maintain SOC 2 Type II attestation reports available under NDA

5. Contact & Governance

For data protection inquiries or to request BAA execution, contact our data governance team at privacy@getringfence.online. For operational assistance, contact support@getringfence.online.