Account-tied work
Saved sessions, study sets, and exports are organized around signed-in user workflows.
Security and privacy controls
Security controls for clinical speech-language workflows.
ConductSpeech is designed for teams that handle sensitive speech, language, school, and clinical records. This page summarizes the controls we use to protect analysis workflows in production.
Minimum necessary details
Teams can use participant, student, or clinic IDs instead of placing names in transcripts.
Reviewable outputs
Clinicians can inspect transcript edits, analysis results, and export readiness before sharing.
Deletion support
Saved sessions can be deleted by the user or handled through a support request.
Protected workflow
The protected sample path
A simple view for procurement and care teams to understand how samples move from intake to review, export, or deletion.
1
Add an authorized sample
Use a recording, transcript, or saved session that your team is allowed to analyze.
2
Review before relying on results
Confirm speaker turns, identifiers, and transcript edits before using the analysis.
3
Use controlled outputs
Reports, study sets, and exports stay tied to your ConductSpeech account workflow.
4
Keep only what you need
Use participant IDs where possible and delete saved work when it is no longer needed.
Protected workflow
- Clinical samples move through a controlled ConductSpeech analysis path.
- Users review transcripts and results before relying on generated outputs.
- Teams can keep identifiers limited to the details needed for the workflow.
- Compliance review is available before regulated production use.
Data protection
- User sessions and product connections use encrypted web traffic.
- HIPAA-ready workflows are designed around protected ConductSpeech processing.
- Saved sessions can be deleted by the customer or by support request.
- Customer samples are not sold or used to train external models.
Access controls
- Team workflows support admin and member roles.
- District accounts can manage seats and membership centrally.
- API workflows use account-level keys designed for approved integrations.
- Email sign-in links reduce password handling for everyday users.
Release care
- Customer-facing releases are checked before and after launch.
- QA checks cover sample analysis, saved sessions, exports, and browser access.
- Major privacy and security changes are documented for review.
- Procurement teams can request a product walkthrough and questionnaire support.
Security review language for procurement teams
ConductSpeech uses protected workflows, encrypted product connections, controlled access, deletion support, and team-level permissions. We can provide a product walkthrough and answer security questionnaires during procurement.
Compliance support
Need a privacy or security review?
We can walk your team through account access, sample handling, deletion support, and the agreement path before production use.