Trust Center

Enterprise-Grade Security Architecture

FramerSend is built from the ground up to protect your sensitive CRM credentials and ensure compliance with global data privacy standards.

How we protect your data

AES-256 Encryption at Rest

When you save a CRM API key in FramerSend, it is immediately encrypted using industry-standard AES-256 encryption before being stored in our database. Your raw API keys are never exposed in plaintext.

Strict No-Log Policy for PII

We act strictly as a secure router. When a visitor submits a form on your Framer site, the payload (names, emails, messages) is held in memory just long enough to deliver it to your CRM. We do not store personal identifiable information (PII) in our database.

Server-Side Execution

All API requests to third-party CRMs are executed from our secure backend environment on Vercel's Edge Network. Your frontend Framer code only contains a public Form ID, eliminating the risk of client-side key scraping.

PostgreSQL RLS Security

Our database utilizes PostgreSQL Row Level Security (RLS) policies. Even if the application logic were compromised, the database engine enforces that users can only access their own encrypted credentials.

Data Flow Architecture

1. Framer WebsiteVisitor submits form (Public Form ID only)
FramerSend Secure APIDecrypts API Key • Processes in-memory • Sends payload
3. Your CRM (Mailchimp, Klaviyo...)Receives data securely via Server-to-Server API
Best Practice: Always generate restricted API keys with write-only permissions when connecting third-party services to any platform, including FramerSend.