Minimum necessary
The receptionist asks for identity, a callback number and the concern. It does not fish for anything else, and it never diagnoses or advises.
Security
Built for a practice that is accountable for every record. The receptionist collects what a call needs, keeps it where it belongs, and leaves a trail.
Data location
Callinzo's team is in Gurugram, India. For practices in the United States, patient data is stored and processed in the United States.
Call records, transcripts, recordings where a practice turns them on, tasks and the schedule for US practices live in US cloud regions. They are not copied to India or anywhere else.
Where a practice allows learning, de-identified records go to a storage bucket in the practice's own country: a US bucket for US practices. Records never cross regions.
Callinzo staff open a practice's records only for support the practice requests. Every read of a transcript is written to the audit log the practice can see.
Each service that touches call audio or records works under an agreement that covers this use. The current list comes with your BAA.
| Feature | Who processes it | What it handles | Where |
|---|---|---|---|
| Hosting and database | Call records, transcripts, tasks, schedule | US cloud regions | |
| Voice and speech | Call audio and its transcription | US regions, under agreement | |
| Text messages | Confirmations and secure links, no clinical details | US carrier, under agreement | |
| Learning storage | De-identified records, only where allowed | US bucket for US practices | |
| Website and contact form | Visitor and demo requests; no patient data asked for | Global edge network |
The receptionist asks for identity, a callback number and the concern. It does not fish for anything else, and it never diagnoses or advises.
Appointment confirmations omit the clinical reason. Escalation alerts contain an expiring link; clinical summaries remain behind access controls. Review message content and delivery settings with your practice.
Data is encrypted in transit and at rest. Every read of a transcript is written to the audit log with who, when and which call.
Recording is off by default. Where a practice turns it on, the caller is told, and the policy is enforced per call.
Real calls feed the learning set only after de-identification to the Safe Harbor standard, and only for practices that allow it in writing. Retention is 365 days; a record can be erased on request.
Staff sign in by email code and a second factor. Front desk, on-call, manager and reviewer roles see only what they need; a role that should not see a screen is told it does not exist.
A BAA is part of onboarding for every practice, and the platform is deployed so that call audio and records stay with providers covered by it.
The dashboard holds operational call records, tasks, and its schedule. EHR connections are validated during onboarding. Document what is synchronized and what your staff must reconcile.
Your privacy and security leads should review the agreements and the configured service together.
Review the BAA, permitted uses, incident reporting, and the vendors that handle audio and records. HHS explains the obligations of business associates and their subcontractors.
Confirm staff roles, second-factor sign-in, and who can open transcripts or recordings. Ask to see an access event in the audit log.
Document the region, recording policy, retention periods, and deletion procedure for your deployment. Confirm whether learning is enabled and what written permission covers it.
Approve the escalation protocol and verify every destination with a test call. A compliance claim does not replace your review of the service, its agreements, and your operating procedures.
Review the Business Associate Agreement, which vendors process call audio and records, where data is stored, staff access, audit logs, recording policy, retention, deletion, and incident reporting. Callinzo's onboarding includes a BAA and practice-specific configuration. Compliance depends on the agreements, deployment, and operating procedures together; a website label or encryption alone is not enough. Your privacy and security leads should review the actual arrangement before patient calls begin.
For practices in the United States: in the United States. Call records, transcripts, recordings where a practice turns them on, tasks and the schedule are stored and processed in US cloud regions, and de-identified learning records, where allowed, stay in a US bucket. Callinzo's team is based in Gurugram, India; staff access is limited to support the practice requests, and every transcript read is logged.
Only roles the practice allows, and every access is logged. Where recording is off, there is nothing to listen to.
Yes. Records can be erased from the learning set on request, and the practice controls retention of call records.
Every control above is visible in the dashboard: the audit log, the recording policy, the learning consent and the retention window.