Privacy

If you create an account, Supabase Auth stores your email and authentication records. Passwords are handled by Supabase and are never stored by this application in plaintext.

The site may collect basic product analytics such as page visits, CTA clicks, signup flow events, copied code snippets, demo play events, and campaign attribution values such as UTM parameters or a click id when analytics are enabled for the deployment.

Remaind ledgers, resume packets, handoff bundles, raw events, artifacts, model profiles, and startup prompts created by users stay on the user's machine unless the user chooses to move, publish, or share them. The hosted website is not a hosted memory service.

Account data is processed by Supabase. Analytics are processed by PostHog when analytics are enabled for the deployment. Environment variables control those integrations; local development must provide its own Supabase project and does not silently fall back to a production project.

You can request account deletion or analytics deletion by contacting the project operator through the channel where you received access. If analytics environment variables are unset, analytics capture is disabled.

Deployers are responsible for any consent banner or regional privacy controls required by their jurisdiction before enabling analytics.