What this policy covers

This policy covers the current public site at Headcanon Generator, including the homepage, blog, contact page, and the character headcanon generator.

What information the site collects

• Basic page visits and interaction data when analytics is enabled
• The text and options you submit when you use the generator
• Your Google-linked email address when you choose to sign in
• The information you choose to include when you send an email

Analytics and measurement

The site can load Google Analytics for Firebase when the public Firebase web config is present, including values such as NEXT_PUBLIC_FIREBASE_API_KEY, NEXT_PUBLIC_FIREBASE_APP_ID, and NEXT_PUBLIC_FIREBASE_MEASUREMENT_ID. That measurement layer can collect page views, route changes, generator submits, share intents, and blog-to-generator clicks so the product team can measure funnel drop-off.

The site can also load Microsoft Clarity through the public environment variable NEXT_PUBLIC_CLARITY_PROJECT_ID. When that value is present and not set to disabled, Clarity may collect interaction data such as clicks, scroll behavior, browser details, and device-level usage patterns for replay and heatmap analysis.

If the Firebase config is absent, Firebase Analytics does not initialize from this site. If Clarity is disabled, that script does not run from this site.

Generation requests

When you submit the workbench form, your request is sent to this site's server endpoint and then forwarded to OpenRouter so the selected model provider can return a response. That request can include your character name, angle, tone, canon distance, optional details, and avoid terms.

The current product also saves successful generation records on the backend. Before login, those records sit under an anonymous browser session stored in an HttpOnly cookie. After Google login through Supabase Auth, those same records may be attached to your user id.

When Firebase Analytics is enabled, the site can also associate measured events with an internal logged-in user id after authentication. That id is used for product measurement and audience continuity, not as a public profile.

How information is used

• To render the site and measure whether pages are being used
• To generate the headcanon output you explicitly request
• To maintain your login session and merge anonymous records into your account
• To respond if you contact the site by email

Who information is shared with

The site uses third-party infrastructure and service providers to operate. In the current version, that includes analytics through Google Analytics for Firebase and Microsoft Clarity when enabled, model routing through OpenRouter for generation requests, and login through Supabase Auth with Google as the identity provider. Those providers receive the information needed to perform their part of the service.

Retention and storage

Successful prompts and results can be stored on the backend under an anonymous session identifier stored in an HttpOnly cookie, or under a logged-in user id after authentication. The current public product still does not offer a user-facing history page, saved library, or permanent public profile.

When you sign in, the current browser's anonymous records may be attached to that account so the same generation history can follow you forward. Long-term retention promises should be treated as product policy, not assumed from the presence of storage alone.

Children's privacy

The site is not built as a service for children. If you think a privacy issue needs attention, email w847738646@gmail.com.

Questions about privacy

If you have a privacy question about the current site behavior, email w847738646@gmail.com. If the product later adds public history, billing, or consent tools, this policy should change with the implementation.