Who is responsible
LaunChad is the controller of the personal data described here. Company details are on the Company page. For privacy questions or requests use the contact form; a person answers by email.
What we store
- Account: your email, name and sign-in data (including optional two-factor secrets and sessions).
- Waitlist application: your email, name, company, role, what you are building, expected request volume and team size. We use them only to decide who gets access first; they are deleted with your account.
- Usage metadata: for each API call the model, provider, status, latency and token counts. Prompts and answers are not stored in the usage log.
- Agents: agent definitions, run steps, results and session messages you create, so runs can be shown and conversations continued.
- Security checks: a hash and a short display form of the indicator, the verdict and the vendors used.
- Audit log: who changed which setting and when, with the IP address when available. Secrets are never recorded.
- Secrets: provider, vendor and tool keys are encrypted at rest and never shown again.
Why we use it (legal basis)
- To provide the service you signed up for (account, keys, requests, agents, billing): performance of a contract.
- Security and abuse prevention (sign-in protection, rate limits, audit log, blocking attacking networks): legitimate interest in keeping the service and its users safe.
- Waitlist review: your request to join; we use the answers only to decide who gets access first.
- Browser notifications and optional emails: your consent, which you can withdraw in the dashboard at any time.
Who receives data
Prompts you send are forwarded to the model provider that serves the request. Indicators you check are sent to the security vendors you configured. Connected apps are called with your permission. Hosting and database providers process data on our behalf.
Where data is processed
The application is hosted by Vercel and the database by Neon in the USA; email is sent through Proton in Switzerland. Transfers outside the EEA rely on the safeguards these providers offer, such as the EU Standard Contractual Clauses or the EU–US Data Privacy Framework. The full list of services is available on request.
Keys and secrets
API keys are stored only as a hash and shown once. Provider and vendor keys, Slack, Discord and webhook URLs and tool headers are encrypted at rest and never shown again.
Alert channels
If you turn on browser notifications we store the push endpoint your browser gives us; the Atom feed uses a private token stored as a hash. Alert text contains only titles and limits, never prompts or answers. If the operator configures an SMTP relay, alert and invite emails go through it.
Retention
Usage and audit rows are kept for 400 days, then deleted. Opt-in cached responses (x-launchad-cache: on) are encrypted and expire after 10 minutes.
Cookies
Only what is needed to sign you in and remember your active workspace and environment. No advertising cookies.
Your rights
You can ask for access to your data, correction, deletion, a portable copy, restriction of processing, and you can object to processing based on legitimate interest. Ask through the contact form; we answer within one month. You can also complain to your data protection authority (in Slovenia: Informacijski pooblaščenec, ip-rs.si).
Your choices in the dashboard
You can delete keys, agents, tools and vendor keys in the console. The workspace owner can export everything as JSON and delete the account under Account; deletion starts a 7-day grace period you can cancel, after which the workspace data and sign-in record are removed.
Changes
When this policy changes materially we tell account owners by email before the change takes effect. The date at the top shows the current version.