> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadblanc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy, Security & Compliance

> How Leadblanc protects customer conversations, personal data, and business privacy.

At Leadblanc, customer trust and data security are architectural imperatives, not afterthoughts.

## Core Commitments

1. **Zero Model Training on Customer Data**: We **never** train foundation AI models or allow third-party model providers to train on your business knowledge base, customer chat transcripts, or uploaded proprietary documents.
2. **Strict Tenant Isolation**: All customer records, vector embeddings, and conversation histories are segregated using PostgreSQL Row Level Security (RLS) policies. No tenant can ever access another workspace's data.
3. **Data Residency & GDPR**: Primary storage and telemetry are provisioned in secure EU regions (`eu-west-1` / `eu-central-1`) to comply with the European Union General Data Protection Regulation (GDPR).
4. **Data Minimization & Redaction**: Sensitive personally identifiable information (PII) such as passwords, bearer tokens, and credit card numbers are automatically masked before logging or telemetry ingestion.

***

## Encryption Standards

* **In Transit**: All API traffic and browser sessions enforce TLS 1.3 with strict `HSTS` (HTTP Strict Transport Security) preloading.
* **At Rest**: Database tables, file storage, and vector indexes are encrypted using AES-256.

***

## Payments & Merchant of Record

All subscription billing, currency conversions, and global sales tax calculations are handled through **Dodo Payments**, our Merchant of Record.

* Leadblanc never stores raw debit/credit card numbers or CVVs on our servers.
* All checkout activations occur via cryptographically signed, replay-protected server-to-server webhooks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.