Security and data handling, as built.
What the product actually does with credentials, payments and personal data, and who helps it do that.
How does LaunchSurface protect my data?
LaunchSurface runs on Cloudflare: the application on Workers, data in Cloudflare's D1 database and R2 storage. Credentials for accounts you connect, such as mailbox OAuth tokens, SMTP logins and API keys, are encrypted with AES-256-GCM before they are stored. Payments go through Stripe Checkout, so card numbers never reach our servers, and Stripe's webhooks are signature-verified. Email outreach goes out from your own mailbox through a send gate that enforces unsubscribes, bounces and complaints. The services that process data for us are listed below, derived from the integrations our code actually calls. We do not claim any security certification on this page.
Encryption applied to connected-account credentials before they are stored.
Reach LaunchSurface's servers. Payment details are entered in Stripe Checkout.
How are accounts and requests secured?
Encrypted credentials
Mailbox OAuth tokens, SMTP credentials and third-party API keys are encrypted with AES-256-GCM before storage and decrypted only when a request needs them.
Least mailbox access we can use
Google mailboxes are connected with the gmail.send and gmail.readonly scopes, Microsoft 365 with Mail.Send and Mail.Read: enough to send outreach and find the replies to it. Read access cannot change or delete mail.
Payments stay with Stripe
Subscriptions are paid through Stripe Checkout. Card details go to Stripe, not to us, and every Stripe webhook is verified against its signature before it is processed.
Signed tracking links
Open, click and visit tracking uses HMAC-signed tokens. A token that fails verification is rejected and records nothing.
Abuse controls
Anonymous URL submissions are checked with Cloudflare Turnstile, and the ingest and general API endpoints are rate limited, with limits published on response headers.
Traceable requests
Every API error returns a correlation ID, the same ID is on the X-Correlation-ID header, and requests are traced end to end, so an incident can be followed from one ID.
How is personal data handled?
Outreach compliance is enforced in code
Every outreach email carries an unsubscribe link and one-click List-Unsubscribe headers (RFC 8058). Unsubscribes, hard bounces and spam complaints go on a suppression list that the send gate checks before every send, and a spam complaint suppresses the address across every LaunchSurface venture.
Beacon identifies only people you emailed
The Beacon script acts only on visits that arrive through a signed link from your outreach. It sets no cookies, keeps its session in the tab's sessionStorage, and does nothing when Do Not Track is on.
Prospect data
Information about prospects comes from public sources and the data providers listed below, and is processed to run the service for you. For that data you are the controller and LaunchSurface acts on your behalf; the Privacy Policy explains the split.
Access, correction and deletion
Requests go to privacy@launchsurface.ai. Retention and your rights are set out in the Privacy Policy.
Which third parties process data for LaunchSurface?
We disclose our providers by category, as our Privacy Policy states. The categories below cover every third-party service our code calls, as of September 2026. Some are used only when the feature that needs them is enabled for a venture. When you connect a Google Workspace or Microsoft 365 mailbox, LaunchSurface sends and reads through that provider's API on your behalf. Those providers are yours, not our subprocessors.
| What it does for us | Data it receives |
|---|---|
| Infrastructure | |
| Application hosting (Workers), database (D1), file storage (R2), queues, Durable Objects, bot checks (Turnstile), page rendering, and custom hostnames with SSL | All service data |
| Payments | |
| Subscriptions, checkout, invoices and wallet top-ups | Billing contact and payment details (held by Stripe) |
| Email delivery | |
| Sign-in links, account email, and fallback outreach sending when no mailbox is connected | Recipient addresses and message content |
| Alternative outreach sending provider, when a venture is configured to use it | Recipient addresses and message content |
| AI models | |
| Routes language-model requests to model providers (including DeepSeek, Anthropic, Google and Moonshot AI) for research, targeting and writing | Prompts containing venture, targeting and prospect context |
| Structured yes-or-no judgments, such as whether a prospect fits your ideal customer | Prospect and targeting context |
| Radar asks your tracked prompts to each engine directly | Tracked prompts |
| Collects Google AI Overviews results for Radar, and web data for research | Tracked prompts, search queries and URLs |
| Contact and company data | |
| Finding and verifying work email addresses | Names, company domains and email addresses |
| Company and person enrichment | Company names and domains, person names and titles |
| Web research | |
| Web search, page extraction and entity discovery | Search queries, URLs and domains |
| Collecting public community, launch and local-business data | Search queries and public profile URLs |
| Domain and subdomain lookups | Domains |
| Observability and analytics | |
| Traces and logs for debugging and incident response | Request metadata, identifiers and error details |
| Metering calls to the paid providers above | Provider hostname, status, latency and token counts |
| Product analytics on this site and the app | Page views, product events and device metadata |
| Marketing-site analytics | Page views and device metadata |
| Internal operational alerts to the LaunchSurface team | Error summaries and identifiers |
Reporting a problem
Report a vulnerability to hello@launchsurface.ai with “Security” in the subject line. Privacy and data requests go to privacy@launchsurface.ai. See also the Privacy Policy and Terms of Service.