Skip to main content

Security overview

L
Written by Levon Adamyan
Updated this week

Cleanlist implements industry-standard security measures to protect your data and your contacts' data.

Infrastructure security

  • Encryption in transit - All data is transmitted over HTTPS/TLS. HTTP requests are rejected.

  • Encryption at rest - All stored data is encrypted at rest.

  • Cloud infrastructure - Hosted on secure cloud infrastructure with regular security patches.

Authentication and access

  • Clerk authentication - User authentication is handled by Clerk, providing enterprise-grade identity management.

  • OAuth 2.0 for integrations - CRM connections use OAuth 2.0. Your CRM passwords are never stored by Cleanlist.

  • API key security - API keys use the clapi_ prefix and are only displayed at creation time. Up to 10 active keys per organization.

Application security

  • Error monitoring - We use Sentry for real-time error tracking and incident response.

  • Session management - Sessions are securely managed with proper expiration and revocation.

  • Input validation - All user inputs are validated to prevent injection attacks.

Data handling

  • Enrichment results are stored in your organization's workspace and are not shared with other customers.

  • API keys and credentials are stored with encryption.

  • We do not sell your data or your contacts' data to third parties.

Reporting security issues

If you discover a security vulnerability, please report it to [email protected]. We take all reports seriously and will respond promptly.

Did this answer your question?