Security & trust

Security is a product principle, not a badge wall

This page lists what is true in the product today — enforced in code, schema, and configuration. We are early, and we would rather show you exactly what holds than imply more: if something is not on this page, do not assume it.

Where your data lives

Data residency

Your data is stored in the EU. Launchpad's database and file storage run on Supabase infrastructure in Frankfurt, Germany.

Infrastructure

Launchpad runs on Supabase — an open-source, Postgres-based platform with built-in authentication, row-level security, and enterprise-grade infrastructure.

For exactly what we store and why, read our Privacy Policy.

Tenant isolation & access control

Row-level security on every table

Access control is enforced in the database itself, not just in the application. Every table in the product database carries row-level security, so a request can only ever reach the rows it is entitled to.

Workspace isolation

Everything you create — coworkers, teams, sessions, canvases, memory, knowledge — is scoped to your workspace, and workspace roles decide what each member can see and do.

Partner isolation

When a partner platform invokes a Launchpad team, that work runs memory-isolated from customer workspaces: a partner invocation cannot reach into your workspace’s memory.

Secrets & credentials

Held in Vault, by reference

Upstream credentials — AI provider keys, integration secrets, partner secrets — are written to Supabase Vault and referenced from there. The raw secret is never stored in a database row, returned in a response, logged, or committed to code.

One controlled write path

Credentials are added and rotated only through an admin-only settings surface, and at most the last four characters are ever shown back.

AI safety & honesty

One gateway for every AI call

Every AI model call the product makes — chat, embeddings, classification — goes through a single gateway where it is metered and accounted. There are no side-channel calls to model providers.

Memory is governed

What a coworker remembers is not a free-for-all: every durable memory carries an explicit scope and authority, enforced by guards in the database — and personal, account-level memories are saved only with your explicit approval.

Writes need approval

Integrations that can write into your systems — Fortnox is the first — only do so behind explicit approval. Launchpad keeps no standing copy of your accounting ledger; data is read live, and the only accounting content held at rest is the change awaiting your approval, until you decide.

Empty beats fake

If a feature is not ready or not wired, the product says so. We do not fake AI activity, counts, or saved state — an honest empty state over a convincing fake, every time.

Your rights & privacy

Export and deletion, built in

You can export your data and delete your account from inside the product — your GDPR rights are product features, not a support ticket.

Consent, recorded

Your consent choices are recorded when you sign up and kept in a consent ledger. The Cookie Policy below is the published record of what we set and why.

This site counts events, not people

Analytics on this marketing site are cookieless: no cookies, no visitor identifiers, no personal data. We count page events in aggregate — never people.

The full legal record: Terms of Service · Privacy Policy · Cookie Policy.

Sub-processors

Published straight from our GDPR processing register — who processes data on our behalf, and what for.

  • NetlifyFrontend hosting and CDN delivery of the web application. draft — confirm with legal (what request data / logs are processed).
  • SupabasePrimary backend infrastructure: managed Postgres database, authentication, and file storage. Processes essentially all platform data. draft — confirm with legal (incl. hosting region / project region).
  • AnthropicAI model inference (Claude) for coworker conversations and AI workers. Processes the content sent to the model at generation time. draft — confirm with legal (API data-retention / no-training terms).
  • OpenAIAI model inference for coworker conversations, knowledge synthesis, and other AI workers. Processes the content sent to the model at generation time. draft — confirm with legal (API data-retention / no-training terms).
  • StripeSubscription billing and payment processing. Processes billing identity and payment-method data. draft — confirm with legal.
  • PostHogProduct analytics: usage and demo events to understand how the product is used. draft — confirm with legal (region: EU vs US cloud, and what identifiers are sent).
  • FortnoxSwedish accounting SaaS the workspace connects via OAuth. On the user's authorization LAF reads/writes the workspace's accounting data as a TRANSIENT CONDUIT and does NOT persist that data LAF-side — a user-authorized integration, not a LAF-side store. EU (Sweden). draft — confirm with legal (data-flow wording: user-authorized, transient, no LAF-side persistence).

Something to ask — or to report?

Security questions and reports go through our contact form and reach the people who build the product.