Understand how your data will be handled.
Review conversation storage, access and processing before rollout. Find the topics and available information to support your security review.
Editor's note
This page is maintained by TalkSonar to answer common security and privacy questions about the platform. It is app-owner content, not an independent certification or verification.
- Call audio and transcripts
- CRM context
- Extracted analysis outputs
- CRM notes and summaries
- Dashboard metrics
- Sales-led onboarding
- First project scoping
- Provider configuration
- Validation before expansion
- Security and procurement review during rollout
Explicit boundaries in requests and background work.
These controls are present in the application code. Infrastructure topology, identity provider, storage settings, retention, and contractual requirements remain specific to each deployment and must be confirmed during implementation.
Authenticated and role-restricted access
Protected application routes require an authenticated principal; administrative routes apply explicit role checks.
Organization-scoped data access
Customer-data routes carry organization context and use organization-scoped database sessions with row-level policies.
Organization context in background work
Customer task messages, provider limits, caches, and processing artifacts carry organization scope instead of relying on a global default.
Privileged-action audit events
Cross-organization administrative actions are recorded with the acting principal, target organization, action, and correlation context.
Organization-aware access. Provider-aware configuration.
TalkSonar is designed around organization-aware access and implementation-specific provider configuration. Exact deployment and data-handling details are reviewed during rollout planning.
Reviewed in the implementation process.
Customer data-use terms, AI provider settings, retention, deletion, and training-related language must be reviewed in the implementation and legal process.
Provider categories TalkSonar can route through.
The provider names below are examples of options for project review and agreement. Whether any option is selected or used depends on the project scope and deployment configuration and must be confirmed for that deployment.
- Speech-to-text
Potentially transcribe call audio for analysis, subject to project agreement and deployment confirmation.
- Soniox
- Deepgram (roadmap)
- Whisper (roadmap)
- Yandex SpeechKit (roadmap)
- LLM routing
Potentially run analysis prompts through an agreed language model, subject to project configuration.
- OpenRouter
- OpenAI (roadmap)
- Anthropic (roadmap)
- Local gateway (roadmap)
- CRM
Potentially read CRM context and publish notes or summaries back, subject to agreed scope and configuration.
- AmoCRM
- Bitrix24 (roadmap)
- HubSpot (roadmap)
- Salesforce (roadmap)
- Telephony
Potentially provide call recordings and metadata, subject to project configuration.
- Sipuni
- Twilio (roadmap)
- Storage
Potentially store call audio and derived artifacts during processing, subject to deployment configuration.
- S3 / MinIO
Names marked as roadmap are planned options, not current availability. Region-, residency-, and DPA-specific constraints and any provider operations must be confirmed during rollout planning.
Questions we hear.
- What data does TalkSonar process?
- Depending on project configuration, TalkSonar may process call audio and transcripts, agreed CRM context, and analysis outputs. CRM context is read only when a connection is confirmed and included in the agreed project scope; agreed notes or summaries may be sent to that CRM under the same conditions.
- Can we review providers and subprocessors?
- Provider names shown here are examples of options for project review and agreement. Any subprocessors in use must be confirmed for the specific deployment during implementation.
- Does TalkSonar sign a DPA?
- DPA terms are reviewed during the implementation and legal process.
- What retention options exist?
- Any retention settings available for a deployment should be confirmed during rollout planning against your data-handling requirements.
- Is TalkSonar SOC 2 or ISO 27001 certified?
- TalkSonar does not publish certifications it has not completed. Certification status and roadmap can be reviewed during procurement.
- Can TalkSonar support region-specific constraints?
- Provider and storage choices are evaluated during the implementation conversation.
Talk to us about your security review.
We will share what we can up front and route procurement-specific questions to the right path.