Launchstack

Privacy Policy

Effective October 2, 2026.

Who operates Launchstack

Launchstack is operated by Andrew Sepeczi in the United States. For privacy questions or requests, contact drewsepeczi@gmail.com.

Information we process

  • Account information such as name, email, profile image, username, and authentication records.
  • Connected-account identifiers, authorization tokens, and repository information needed for the integrations you enable.
  • If you connect Gmail, email messages, recipients, attachments, and draft or send content accessed for the tasks you request, plus records of approvals and action results.
  • If you connect Linear, issue details and search results accessed for your requested tasks, plus records of action results.
  • Prompts, attachments, repository files the agent reads, generated code, messages, command output, session history, and usage records.
  • Operational information such as request logs, errors, device/browser information, and site usage analytics.
  • Support correspondence and, when paid subscriptions open, customer, order, subscription, and billing-status records.

Do not include secrets or sensitive personal information in prompts or repository files unless needed for your task and you are authorized to share them.

How we use information

We process information to authenticate users, run coding tasks, maintain session history, connect repositories, measure usage, troubleshoot issues, prevent abuse, respond to support requests, and meet legal and billing obligations. We do not sell your personal information.

Connected Gmail data is used to carry out your requested email tasks. Draft creation and sending require your approval in Launchstack. Review the displayed recipients and message before approving.

Service providers and sharing

Hosting and cloud execution involve Vercel and, depending on the configured sandbox backend, CodeSandbox. Account and session records are stored in our PostgreSQL database hosted by Neon. Connected GitHub and Vercel accounts are used according to the permissions you grant.

Optional Gmail and Linear actions use Composio to connect accounts and execute the actions you authorize. Connection credentials remain with Composio. Retrieved email and issue content may enter the conversation context sent to the selected model provider. Connect an account only if you are authorized to share the information needed for your tasks.

If you connect Codex, we encrypt and store the login file you import, including subscription authorization tokens. Tokens are used temporarily in your isolated workspace and refreshed by the official Codex CLI. Disconnecting deletes the saved connection. Codex tasks send relevant prompts, code, and conversation context directly to OpenAI under your account.

Prompts, relevant code, attachments, and conversation context may be sent through OpenRouter to the selected model provider to produce responses. These providers have their own processing and retention policies. Do not assume that all model providers have identical data-use practices.

Vercel Analytics processes website usage information. When paid subscriptions open, Creem will handle checkout, payments, tax, receipts, and its customer portal as merchant of record. We do not receive your full payment-card details. We may also share information when legally required or necessary to protect users and the service.

Cookies, browser storage, and public sharing

Authentication uses session cookies. Browser storage keeps preferences such as your selected theme. You can clear browser storage or cookies, but this may sign you out or reset preferences. If you enable a public session share, anyone with its link may view the shared content; review it before sharing and disable the share when no longer needed.

Retention and security

We retain account and session information while needed to provide the service. We may retain some records afterward for billing, security, dispute resolution, or legal obligations. Copies may remain in backups until those backups expire. We use access controls and protections for authentication credentials, but no online service can guarantee absolute security.

Your choices and requests

You can manage connected accounts and public shares within Launchstack. Contact support to request access, correction, export, or deletion of your personal information or account. We may verify your identity before processing a request and explain any legal or technical limits. Rights vary by location; where applicable, you may also object to processing, request restriction, or complain to your local data-protection authority.

International processing and updates

Our providers may process information in the United States and other countries. Applicable privacy protections can differ. This policy may change as the service develops; the effective date above identifies the current version.