Privacy Policy

What We Collect

The TLS Lane agent collects TLS handshake metadata from connections it observes. This includes:

Data	How stored
Domain (SNI)	Plaintext, transmitted over HTTPS
Cipher suite	Plaintext (e.g., "AES-256-GCM")
TLS version	Plaintext (e.g., "TLS 1.3")
Key exchange group	Plaintext (e.g., "X25519", "ML-KEM-768")
Action	Plaintext (monitor, spliced, passthrough, blocked)
Direction	Inbound or outbound
Timestamp	UTC timestamp of the connection
Error count	Number of agent errors (no error content)

Domain names are server identifiers in TLS handshakes, not personal data. They are sent in plaintext over HTTPS because hashing provides no real privacy — the domain space is small and any deterministic hash is trivially reversible via dictionary lookup. Plaintext domains are required for the crypto inventory to be useful.

What We Do Not Collect

• Application-layer payloads or HTTP content
• IP addresses of clients or servers
• Certificate private keys or TLS session keys
• User browsing history or behavior patterns
• Agent logs (unless you explicitly request retrieval and submit them)

Agent Log Retrieval

When you request agent logs from the Support page, your agent uploads its flight-recorder buffer (last 10 minutes, max 1000 entries). These logs may contain IP addresses, hostnames, file paths, or other operational data.

• Logs are only uploaded when you initiate a request — never automatically
• A redaction tool is provided to strip personal information (IPs, emails, tokens, paths) before submitting a support ticket
• Raw logs are stored in your account and are deleted when you delete your account
• Only the redacted version is attached to support tickets

Data Transport

All agent-to-server communication uses HTTPS. Event batches and log uploads are gzip-compressed before transmission. For full data sovereignty, deploy the management server on-premises.

Account Data

When you register, we store:

• Email address
• Password (bcrypt hashed, never stored in plaintext)
• Agent token (for authenticating your agents)

Data Retention

Connection events are automatically purged after your configured retention period (default: 90 days). You can change this in your account settings.

Data Portability

You can export all your data at any time via GET /api/account/export. This returns your account info, agent list, and aggregated event data as JSON.

Right to Erasure

You can delete your account at any time from the dashboard or via DELETE /api/account. This permanently and irreversibly deletes:

• Your account and email
• All agent tokens
• All registered agents
• All connection events
• All domain mappings
• All policy versions
• All retrieved agent logs
• All support tickets and replies
• All alerts and alert settings

On-Premises Deployment

For organizations that require data sovereignty, TLS Lane can be deployed on-premises. In this configuration, no data leaves your network. Point your agents to your internal management server:

tlslane --management https://tlslane-mgmt.internal.corp

Third Parties

We do not sell, share, or provide your data to third parties. The management server does not include third-party analytics, tracking scripts, or advertising.

Security

• All agent-to-server communication is over TLS
• Passwords are bcrypt hashed
• Agent tokens are cryptographically random (256-bit)
• Session cookies are HttpOnly with SameSite=Lax
• All database queries use parameterized statements

Changes

We may update this policy. Material changes will be communicated via the dashboard or email. Continued use after changes constitutes acceptance.

Contact

Privacy questions: Contact us.