Security & Data Protection

Your sales calls and meetings deserve privacy. Here’s how we keep your data safe inside the EU.

Encryption

HTTPS everywhere; data at rest encrypted with AES‑256.

Data Residency

All customer data is stored in Azure France Central (EU), with encrypted daily back‑ups in West Europe. AI processing runs in EU regions only (Azure OpenAI France Central, Google Vertex AI EU), with no retention and no training. System emails are delivered via Resend (USA).

Access Control

OAuth 2.0 / OIDC sign‑in with short‑lived JWT tokens.

Data Retention

Audio 30 days by default, transcripts and analyses per customer policy, both set per workspace. Backups kept 7 days. Access logs up to 2 years. Delete-on-request.

Encryption & Infrastructure

All traffic between your browser and Teneks is protected with HTTPS/TLS encryption. Data stored on our servers is encrypted using AES-256 encryption. We host our platform on Microsoft Azure in the France Central region, which provides built-in security features including DDoS protection. Daily backups are automatically replicated to West Europe for data protection and kept for 7 days.

Transcription runs on our own self-hosted speech model on Azure. Summaries and analyses use Azure OpenAI (France Central) and Google Gemini models through Google Cloud Vertex AI EU endpoints. Both providers are configured with zero data retention: inputs and outputs are not stored, logged or used to train models.

Data Masking & Anonymisation

Teneks can automatically detect and mask personally identifiable information (PII) in transcripts. When masking is enabled for a workspace, it is applied to the stored transcript as soon as transcription is complete, so it covers the platform and all exports, not only exported files.

Current PII Protection

  • Email Addresses: Automatic detection and masking in stored transcripts and exports
  • Phone Numbers: Recognition of various phone number formats
  • Names: Basic name detection and redaction capabilities
  • Credit Card Numbers: Financial data protection for sensitive conversations

For platform improvements, we use only fully anonymised and aggregated usage data, such as feature‑usage patterns, page views and session durations, that describes how users interact with the platform interface. We never use customer content data (audio, transcripts, conversation analytics) for platform improvement. All usage data is aggregated so that it cannot be traced back to any individual or organisation (GDPR Recital 26).

Planned Enhancements

  • Pseudonymised retention: Removing the link between transcripts and personal identifiers for customers who want to keep de-identified transcripts longer
  • Enhanced Detection: Improved accuracy and additional PII types
  • Export Controls: Granular options for what to redact per export

Access Control & Application Security

Users sign in securely using Google or Microsoft accounts through OAuth 2.0. This means we don't store your passwords - authentication is handled by these trusted providers. All API requests are protected with JWT tokens to ensure only authorized users can access your data.

Who Can Access Customer Data

Access to customer content data (audio recordings, transcripts, conversation analytics) is strictly controlled:

  • Your Organisation: Users within your organisation, scoped by role‑based permissions (User, Manager, Admin).
  • Teneks Founder / CEO: Only at your request or to investigate a reported issue, under strict confidentiality obligations. Every access is logged.
  • Designated Account Manager: If assigned in the future, bound by NDA. You will be notified before any assignment.

Teneks employees do not have access to your audio recordings, transcripts or conversation analytics. Technical infrastructure access is limited to system administrators who can only view anonymised metadata for operational purposes.

Confidential calls: on Meetings and Talent plans, the person who recorded a call can mark it confidential. It then opens only for them. Their manager, your workspace admins and Teneks support cannot open it, and it cannot be shared.

Our application follows secure coding practices and we regularly update dependencies to address any security vulnerabilities. Azure provides the underlying infrastructure security including network protection and access controls.

Data Retention & Logging

  • Audio: 30 days by default (customisable).
  • Transcripts, summaries and analyses: retained per customer policy, with their own retention period set per workspace.
  • Deleting a recording: removes everything derived from it (transcript, summary, analyses and search index).
  • Backups: kept for 7 days, so deleted data is gone from backups within 7 days.
  • Technical access logs: retained for security and audit purposes for up to 2 years, or longer only where needed to establish, exercise or defend legal claims.
  • Content access log: every time someone opens a call or reads its transcript or summary, we record who, when and from which IP address. Audio playback links and meeting PDF downloads are recorded too. Retained for up to 2 years, or longer only where needed to establish, exercise or defend legal claims.
  • Deletion on request: customers can trigger secure erasure at any time.

Incident Response

Platform health is monitored continuously; security alerts are reviewed by an on‑call engineer. We commit to acknowledging any critical vulnerability report within 24 hours, and we notify affected customers of a personal data breach within 48 hours of becoming aware of it.

Compliance Roadmap

Our compliance roadmap prioritises EU regulations first, followed by internationally recognised certifications.

StandardStatusTarget DateScope
GDPR✅ OperationalOngoingData protection & privacy
EU AI Act (limited-risk)✅ AlignedOngoingAI transparency & safety
ISO 27001🛠️ In preparationH1 2027Information security management
SOC 2 Type II📋 PlannedFutureSecurity, availability & confidentiality
OWASP Top 10📋 PlannedFutureApplication security testing
Cyber Essentials Plus📋 PlannedFutureBasic cyber security controls

Sub-processors & Third Parties

We use a small number of vetted sub-processors, each bound by a data processing agreement under GDPR.

VendorServiceData LocationData Types
Microsoft AzureCloud hosting & storage, self-hosted transcription model, Azure OpenAI language models (zero data retention, no training)France Central (EU); backups West Europe (EU)All platform data
Google Cloud (Google Cloud EMEA Limited, Vertex AI)Gemini language models for transcript post-processing (zero data retention, no training)EU regions (Vertex AI EU endpoints)Transcripts and derived summaries and analyses
StripePayment processingIreland (EU)Billing & payment data
Resend (Plus Five Five, Inc.)Transactional email delivery (account emails, coaching and report emails, meeting reminders)USA (primary processing); sends from the EU region (Ireland). Keeps email content and metadata for up to 30 days in the USA, for delivery and troubleshooting. Transfers under the EU–US Data Privacy Framework and Standard Contractual ClausesRecipient email addresses and names, email content
Google (sign-in)OAuth authenticationEU regionsEmail & profile data only
Microsoft 365OAuth authenticationEU regionsEmail & profile data only

We notify customers by email at least 30 days before adding or replacing a sub-processor, and customers may object. Customer data is never shared with marketing or advertising platforms.

Sub-processor list last updated: 30 October 2026.

Security Monitoring & Testing

We use Azure Monitor and automated dependency scanning to detect security issues early.

  • Infrastructure Monitoring: Azure Monitor and application error alerting surface system anomalies and operational issues
  • Access Logging: API access and administrative activity is recorded in technical logs (user, route, timestamp)
  • Dependency Scanning: Automated alerts for known vulnerabilities in our codebase dependencies
  • External Security Testing: OWASP Top-10 penetration testing planned ahead of the ISO 27001 audit

Platform health is monitored continuously; security alerts are reviewed by our engineering team. We commit to acknowledging any critical vulnerability report within 24 hours and will provide customer notification for any incident affecting data security.

Business Continuity & Disaster Recovery

Our infrastructure runs on Microsoft Azure with built-in redundancy and backup across two EU regions.

  • Automated Backups: Daily backups to Azure Geo-Redundant Storage with 7-day retention
  • Geographic Redundancy: Data replicated between France Central and West Europe regions
  • Azure Availability Zones: Infrastructure distributed across multiple zones for resilience
  • Database Failover: Automatic failover capabilities through Azure SQL Database
  • Incident Communication: Customer notification within 24 hours for service-affecting incidents

As a growing startup we continue to strengthen our disaster recovery. Azure's managed infrastructure gives us a strong baseline for data protection and service continuity.

Security White Paper

The detailed Teneks Security White Paper is not publicly available. It is available upon request for qualified security, procurement, and legal reviews. Contact security@teneks.ai.

Responsible Disclosure

Found a vulnerability? Email security@teneks.ai. We'll respond within one business day.

Data protection contact: Arne Niitsoo, data@teneks.ai.