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
Database access controls
Launchpad uses database row-level security and permission checks to govern access to stored content. Workspace membership alone does not describe all permissions: rooms and personal memories have narrower access rules.
Workspace isolation
A workspace is the tenant boundary for your organisation. Rooms organise projects within it. Workspace roles, room access and content scope govern who may use material; personal memories have their own access rules.
Partner isolation
Partner invocations are bound to an authorised workspace and calling identity. Using a shared team does not itself grant a partner access to another customer’s private memories; retrieval must follow the invocation’s permissions and scope.
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
Access scope and containment determine who may use a memory; authority distinguishes a rule, guidance or observation. Protected rules and reusable shared learning require human review; some low-authority observations can be saved automatically.
Personal memory and coworker learning
Portable personal memories require your approval. A coworker can also automatically retain screened professional observations about you, limited to you, that coworker and the workspace where you worked together. You can turn future learning off in Settings; doing so does not remove memories already saved.
Recall is selective
Coworkers can draw on saved memories across sessions. Recall selects a limited amount of relevant context and can miss a saved fact, so confirm important constraints in the current brief.
Screening supports your review
Screening helps identify sensitive or client-specific material, but it can make mistakes. Review a proposed lesson and its intended readers before making it shared knowledge.
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
Data export and account deletion controls are available inside the product. Account deletion and archiving a memory are different actions; an archive removes a memory from active use and is not proof that every retained copy has been erased. Retention and data rights are described in the Privacy Policy.
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.