Privacy Protection Policy
RCMContact ("we," "us," or "our") respects the security and privacy of our global enterprise clients, partners, and the individuals whose data cascades through our cloud communications networks. This Privacy Policy outlines how we gather, isolate, process, and protect datasets handled via our core cloud dialers, CRM data relays, and interactive voice response (IVR) matrices.
HIPAA & PHI Data Supremacy Note: When RCMContact handles data on behalf of covered healthcare entities or medical billing organizations, we operate exclusively as a Business Associate. All Protected Health Information (PHI) or Electronic Patient Ledger Rows are strictly governed by our Business Associate Agreement (BAA) and federal HIPAA security rules, superseding standard commercial data tracking policies.
1. Categories of Information We Process
To ensure fast, reliable telecom routing and platform accessibility, we segment processed data inputs into two distinct structures:
- Corporate Account Data: Name, professional work email, company name, phone number, and account credentials captured during demo configurations or workspace initialization.
- Telephony & Transmission Data (Call Detail Records): Inbound/outbound phone numbers, routing IP addresses, connection durations, transit time stamps, automated voicemail loop markers, and encrypted call recordings managed inside Client tenant environments.
2. Core Methodology of Data Utilization
We utilize information layers exclusively to manage, maintain, and upgrade our enterprise software delivery pipelines. Specifically, your parameters are used to:
- Maintain stable user sandbox configurations, API access networks, and softphone connectivity paths.
- Track transactional billing values, monthly carrier connections, and overage metrics.
- Enforce platform security protections, analyze carrier latency patterns, and stop fraudulent network activity.
- Run real-time Natural Language Processing (NLP) audio redaction tools to clean recording pathways according to client setup configurations.
3. Zero Data Monetization Guarantee
RCMContact enforces a strict zero-monetization framework across all operational teams. We do not sell, rent, swap, or trade corporate lead parameters, patient contact rosters, or call history logs with third-party marketing companies, brokers, or external advertising protocols. Information layers are shared only with downstream carrier lines and encrypted hosting sub-processors strictly required to complete communication transit tasks.
4. Technical Security & Isolation Guardrails
Our database architecture is designed according to SOC 2 Type II guidelines. All processed data rows are protected using active flight encryption protocols (TLS 1.3) and secure resting states (AES-256). Physical servers and data relays are located in heavily protected, tier-4 enterprise data facilities with continuous monitoring logs and strict access limitations.
5. Jurisdictional Rights & Compliance Controls
Depending on your localized geographical operating footprint, your enterprise or your consumers may preserve structural data governance parameters:
- United States (HIPAA/CCPA): Full compliance with patient access validation rules and immediate data remediation support.
- United Kingdom & Europe (GDPR): Standard contractual clauses, strict sub-processor isolation, and rapid data purges upon formal contract termination.
- India (TRAI/DPDP): Proper transactional telecom line identification boundaries and unalterable administrative log trails.
6. Privacy Policy Updates & Structural Contact
We modify this privacy layout periodically to align with changing international data transit rules or platform version upgrades. If structural shifts are pushed to our codebase, a global notice flag will display inside your admin panel cockpit. For further information regarding your account isolation parameters, reach out directly to our team at privacy@rcmcontact.com.