A trustworthy clinical workflow should be explainable before adoption.
This page brings together public information for an initial assessment by practices and professionals. It does not replace the contract, Privacy Policy, or your organization’s legal and technical review.
Reviewed on
Controller and processor roles depend on actual decisions.
Legal classification does not come from the software name. It depends on who determines purposes, essential means, access, retention, and disclosure in each operation.
| Participant | Typical operational role | What must be defined |
|---|---|---|
| Practice or professional | Defines the care purpose, who may access data, and how the final version enters the medical record. | Legal basis, patient information, roles, retention, data-subject rights, and incident response. |
| Zello Life | Processes data to provide contracted features and maintains the product’s technical controls. | Instruction scope, support, deletion, subprocessors, data return, and termination. |
| Infrastructure and service suppliers | Perform limited parts of hosting, AI, or billing. | Data involved, purpose, applicable configuration, and contractual obligations. |
In a B2B relationship, the practice generally makes the central care decisions while the platform operates within the contracted scope. The final classification must be confirmed against the contract and real workflow.
Not every data category follows the same path.
Map each category separately. Access needed to bill a subscription is not the same access needed to generate a clinical draft.
| Category | Examples | Use in the workflow |
|---|---|---|
| Account and identity | Name, email, role, and practice membership. | Authentication, account administration, and access control. |
| Clinical content | Visit context, transcript, notes, and corrections. | Generating and editing the draft requested by the professional. |
| Audio | A recording or voice stream used for transcription. | Transcription and requested reprocessing where available. |
| Documents and attachments | Templates, PDFs, reports, and visit files. | Organization, review, export, and authorized sharing. |
| Billing | Customer identifiers, plan, and subscription status. | Checkout, billing portal, and plan reconciliation. |
| Technical records | Access events, failures, and relevant changes. | Security, support, abuse prevention, and incident investigation. |
Four points to validate before using real voice data.
- 01
Authorized capture
The organization selects the applicable basis, informs the people involved, and first tests with a fictional scenario.
- 02
Protected transmission
The authenticated session sends the audio needed by the transcription service configured for the workflow.
- 03
Editable draft
The transcript feeds content that remains subject to the professional’s verification and decision.
- 04
Retention and deletion
Periods, reprocessing, and deletion must follow available settings, the contract, and the organization’s policy; validate them during the pilot.
The public page does not promise one universal retention period. The correct answer depends on the data type, contracted product, and policy applicable to the account.
Services currently identified in the architecture.
This list describes function—not certification, physical location, international transfer, or a specific contractual condition.
Production infrastructure and AI endpoints configured for product features.
Model technology used by AI features under the applicable service configuration.
Billing, subscriptions, and the payment portal; Zello Life works with the identifiers and statuses needed for the account.
Before contracting, request current documentation to confirm regions, terms, measures, and subprocessors applicable to your case. This page creates no additional warranty.
What a practice should test with fictional data.
- Account creation, recovery, and session termination.
- Inviting, changing roles, and removing team members.
- Separation between professionals, accounts, and practices.
- Draft review before approval, export, or sharing.
- Link creation, expiration, and revocation when that feature is used.
- Export and deletion through the workflows available to the account.
- Procedures for transcription errors, downtime, and incidents.
- The responsible channel for data-subject requests and contract termination.
Answers that start due diligence rather than close it.
Does Zello Life provide a DPA?
Do not assume this page serves as a DPA. The availability, content, and signature of a data-processing agreement must be confirmed during the commercial and contracting process.
Is clinical data used to train models?
The published product has no feature that turns customer visits into a training dataset. The practice should still require written confirmation of the terms applying to each supplier and configuration before a pilot.
Who is the data controller?
In a care workflow, the practice or professional generally determines the central purposes. Each party’s role still depends on actual decisions and should be stated in the contract.
Does the platform replace physician review?
No. Transcription and generation create editable content. The professional reviews, corrects, decides, and approves it before clinical use or sharing.