Skip to main content

Security Overview

Understand the measures tl;dv takes to keep your data secure, private, and compliant.

Written by Suellen Lorga

At tl;dv, protecting customer data is a core part of how we build and operate our platform. We use industry-standard security controls, privacy-first design principles, and secure infrastructure to help keep your meeting recordings, transcripts, and AI-generated insights protected.


Security at a glance

tl;dv is designed with security and privacy in mind:

  • SOC 2 compliant

  • GDPR compliant

  • Data encrypted in transit and at rest

  • Customer data is not used to train AI models

  • EU-based data hosting available

  • Single Sign-On (SSO) support

  • Secure software development practices

  • Vulnerability monitoring and disclosure processes


AI privacy

tl;dv uses AI to generate meeting summaries, notes, and insights.

Customer recordings and meeting data are not used to train AI models. When AI processing is required, tl;dv applies additional privacy controls, including metadata anonymization and processing safeguards designed to protect customer information.

For more information, see: AI Privacy and Data Usage


Data protection

All connections to tl;dv are encrypted using HTTPS, and stored data is protected using industry-standard encryption methods. tl;dv also maintains access controls and follows secure development practices to help protect customer information.

For more information, see: How tl;dv Protects Your Data


Compliance

tl;dv supports organizations with regulatory and security requirements through:

  • GDPR compliance

  • SOC 2 compliance

  • Data processing controls

  • Security documentation and trust resources

For more information, see: Compliance Certifications and Standards


Additional resources

For detailed security documentation, audit information, and compliance resources, visit the Trust Center.

If you have questions about security, privacy, or compliance, contact the tl;dv team through the Trust Center or support channels.

Did this answer your question?