Privacy Policy

Effective July 18, 2026

This is a starting-point template. Have it reviewed by a professional for your jurisdiction before relying on it.

The short version

Local Site Engine is built around a simple promise: site generation runs in your browser with your own OpenRouter API key, and we never receive, proxy or store that key. We collect only the account and usage data needed to run the service.

What we collect

  • Account data — your email, name and authentication details (via Supabase Auth, or Google if you use it).
  • Project data — the wizard configurations you save (business details, services, areas, design). These never contain your API key.
  • Build metadata — counts, niche, scope, model name, page count and ZIP size for usage tracking and analytics. We do not store the generated page content.
  • Generated ZIPs — stored privately in your account so you can re-download them. Only you can access them.

What we never collect

  • Your OpenRouter API key. It stays in your browser during generation and is never transmitted to us.
  • The AI-generated text of your sites (only metadata such as counts and model name).

How we use your data

To provide and secure the service: authenticate you, save and reload your projects, enforce plan limits, store your ZIPs for re-download, and produce aggregate analytics. We do not sell your personal information.

Third-party processors

  • Supabase — authentication, database and storage.
  • OpenRouter — the AI provider you call directly from your browser with your own key, under their terms.
  • Stripe — payment processing for paid plans (when enabled).
  • Vercel — application hosting.

Data retention & your rights

You can delete your projects and account at any time; deleting your account removes your profile, projects, build metadata and stored ZIPs. To request access, correction or deletion, contact us at support@localsiteengine.com.

Changes

We may update this policy; material changes will be reflected by a new effective date on this page.