How Tenali Handles Your Data

Tenali processes meeting context to generate real-time assistance and post-call outputs while enforcing role-aware access controls.

Data Flow Overview

1. Desktop runtime captures approved in-call context using explicit OS permissions.
2. Context is processed to generate transcript segments and answer assistance.
3. Outputs are stored in workspace surfaces (summaries, question views, action items).
4. Source retrieval uses connected knowledge assets to ground responses.
5. Authorized integrations can receive selected outputs via user/admin actions.

Processing Boundaries

• Access is scoped by workspace role and resource ownership.
• Source ingestion scope can be user-level or organization-level.
• Integration actions require explicit connection and authorization.

Operational Safeguards

• Permission gating at desktop layer
• Role-based access boundaries in web/workspace surfaces
• Controlled source refresh/delete controls
• Reviewable sync outcomes for downstream integrations

Customer Guidance

For procurement or security questionnaires, pair this page with:

• Data Retention and Deletion
• Encryption and Key Management
• Access Controls and Auditability
• Subprocessors and Vendors