BADLAMB

Last updated: May 26, 2026

Privacy Policy

BADLAMB MVP

Information we collect

Account information from Supabase Auth, including email address and OAuth profile metadata.

Campaign inputs such as business description, website URL, sales direction, generated decks, leads, email drafts, approvals, and send events.

User-provided integration credentials, including Resend API keys, stored encrypted on the server.

How we use information

To create sales decks, discover leads, draft outreach, enforce plan usage, process membership billing, and deliver user-approved emails.

To cache contact emails so BADLAMB can avoid repeated provider lookups while keeping each user's campaign and send history separate.

Service providers

BADLAMB uses Supabase for auth and Postgres, GCP Storage for deck files, Firecrawl for website extraction, Hunter for email discovery, Gemini for generation, Paddle for billing, and Resend for user-connected delivery.

Retention and control

Campaign data, generated outputs, cached contact records, and usage events are retained while needed to operate the product.

Users can request deletion or export of their account and campaign data by contacting BADLAMB support.

Security

API credentials are encrypted before storage. Access to account data is gated through Supabase-authenticated API requests.

No platform-wide Resend key is used for customer outreach; sending requires the user's own connected Resend credential.

Contact

For privacy requests, contact the BADLAMB operator through the support channel provided in the product.