Legal · Privacy
Privacy Policy
Last updated August 2026 · Your keys stay yours. Your data is never for sale.
1. The short version
We store the minimum needed to run the service — your account, your projects, your files, and your encrypted API keys. We never sell your data, we never train on your private projects, and your API keys are encrypted with AES-256-GCM and decrypted only on the server at generation time.
2. What we store
Account (email + OAuth identity via InsForge auth), projects (prompts, build status, design choices), project files and build logs, LLM key vault entries (encrypted key + fingerprint, never plaintext), and LLM profiles (provider + model names). Uploaded images live in private storage buckets and are referenced by URL during generation only.
3. What we never see
Your raw API keys after save — they are encrypted before storage and only decrypted server-side to call your chosen provider. We do not see your provider-side billing, and requests go directly from our generation worker to the provider you selected (e.g. OpenRouter) with no logging of key material.
4. Cookies + sessions
Authentication uses an access-token cookie and an httpOnly refresh-token cookie to keep you signed in and refresh sessions. No third-party advertising cookies, no cross-site trackers.
5. Who processes your data
Infrastructure: InsForge (Postgres, auth, storage, realtime) hosts the backend. AI inference: whichever provider you configure — OpenRouter, OpenAI, Anthropic, or Gemini. Deploy/export (optional): Vercel and GitHub, only when you trigger them. Each acts under its own policy for the data it touches.
6. Your controls
Delete a project and its files, logs, and stored memories go with it (cascade delete). Remove a vault key and it cannot be used for future generations. Export your code at any time — it is yours. Self-host the entire platform if you prefer your data never leaves your infrastructure.
7. Retention + security
Realtime event retention is zero by default — live streams are ephemeral. Build logs persist with your project until you delete it. Keys are encrypted at rest, sessions refresh over httpOnly cookies, and database access is scoped by row-level security so users can only read their own rows.
8. Changes
Material privacy changes will be noted in the changelog before they take effect. If a change ever requires broader data use, we will ask first — silence is not consent.
Privacy question or deletion request? Open a GitHub issue — private matters can go to the maintainers directly.