Privacy Policy

1. Information collected

Information may include account identifiers and email, profile details, prompts and project requirements, generated project source and build logs, deployment IDs and URLs, hosting status, usage/credit records, payment references and status, contact-form submissions, and relevant support communications. Do not submit secrets or sensitive personal information unless a feature specifically requires it.

2. How information is used

Information is used to authenticate users, provide Leo and plan-authorized builders, enforce usage limits, create and manage customer projects, verify payments, operate hosting, prevent abuse, provide support, and meet legal obligations. Customer prompts and requirements may be sent to configured AI providers to generate requested outputs.

3. Service providers and hosting

Depending on enabled features, LEO OS uses Supabase for authentication, database, and storage; OpenAI for AI and image generation; GitHub for customer project source repositories; Vercel for project builds, deployments, analytics, and Speed Insights; Paystack for payments; Sentry for application error monitoring when configured; and configured email providers for notifications. Each provider processes data under its own terms. Customer project repositories and deployments are separate from the LEO OS production application.

4. Operational and performance monitoring

When Sentry is configured, LEO OS sends sampled operational errors with stack traces, release/environment context, parameterized routes, and a random request correlation ID. The application disables default personal data collection and session replay, and removes request bodies, headers, cookies, user identity, error text, stack-local values, and non-navigation breadcrumbs before sending. The Sentry DSN is an ingestion address; source-map upload credentials remain server-side.

When Vercel Speed Insights is enabled for the deployed project, a 25% sample of browser performance events is sent to Vercel. Page query strings and workspace/project identifiers are removed or parameterized before submission. Vercel documents Speed Insights data as anonymous performance/device/network context rather than a cross-page user identity; see its Speed Insights privacy documentation. See also Sentry’s privacy policy.

These measurements are separate from synthetic Lighthouse/PageSpeed tests. No Leo conversation, prompt, generated code, payment details, API key, or webhook secret is intentionally sent to Sentry. Monitoring collection depends on provider configuration and deployment; it may be disabled when credentials or project settings are absent.

5. Security and retention

LEO OS uses authenticated access controls and provider security features, but no online service can guarantee absolute security. Account, project, build, deployment, and payment records may be retained while needed to provide the service, maintain operational history, resolve disputes, and meet legal obligations. Contact support to request deletion, subject to those obligations and provider retention limits.

6. Your choices and contact

You may request access to, correction of, or deletion of personal information, subject to legal and contractual requirements. Contact me at leonardudoh5@gmail.com or through the contact page on this site.

7. Updates

This policy may be updated when services or legal requirements change. The current version and its effective date will be posted on this page.