Security & trust
Boring by design,
where it counts.
You're putting your prospect data and your brand in our pipeline. Here's how we treat both.
Tenant isolation at the database layer
Every workspace's data is isolated with row-level security enforced in Postgres itself: not in application code. A cross-tenant test suite runs in CI; a failing isolation test fails the build.
Encrypted secrets
Connector credentials and API keys are encrypted at rest with per-secret ciphers. Service-role credentials never reach the browser or the marketing site.
Least-privilege access
Role-based access control per workspace. API keys are scoped, revocable, and carry monthly spend caps so a leaked key has a bounded blast radius.
Static page serving
Generated prospect pages are static renders: no app server, no database in the request path. Less attack surface, and nothing sensitive to leak.
First-party tracking only
Page analytics are first-party: no cross-site tracking, no fingerprinting, no data brokers. Engagement data belongs to the workspace that generated the page.
AI guardrails
Per-prospect generation never executes generated code: it fills declared template slots and nothing else. Research runs in sandboxed pipelines with spend limits per workspace.
Working through a security review? We'll complete questionnaires and walk your team through the architecture , contact us. SOC 2 Type II is on our compliance roadmap; ask for current status.
Your next thousand prospects
are about to feel famous.
Build a template this afternoon. Generate your first fifty pages free. Watch the intent signals decide tomorrow's call list.
2 minutes. No signup. Watch a page build itself for a real company.