Privacy Policy

Introduction

This starter Privacy Policy describes the data paths available to a deployed site. The operator of each deployment must update this template for its identity, configured providers, retention requirements, and applicable law before publishing it.

Information We Collect

Depending on the features you use, the site can collect:

• Account and contact information, such as your name, email address, sign-in records, and messages you send to support.
• Content and service records, such as prompts, uploads, generated results, usage, credits, and operational logs needed to provide the requested service.
• First-party acquisition information, including an anonymous browser identifier; validated source, medium, campaign, landing, and referrer fields; an affiliate fallback; and recognized advertising click identifiers such as gclid, gbraid, wbraid, fbclid, or msclkid.
• Checkout and order attribution, which preserves an immutable copy of the applicable first marketing touch and affiliate value when checkout begins and associates it with the resulting payment when possible.
• Payment and transaction information returned by the configured payment provider. The site does not need to store full payment-card details when those details are handled by the provider.
• Device and security information, such as IP address, browser details, request timestamps, and signals used to protect the service.
• Optional-service data produced only by third-party analytics, support, or referral services that are actually configured and allowed to run.

Raw advertising click identifiers are kept in the site's database rather than the browser attribution cookie. The compact attribution metadata sent with a provider checkout is limited to the internal snapshot ID, source, medium, campaign, and affiliate value; raw click identifiers are not projected to the payment provider.

First-Party Attribution and Optional Services

The site records its own acquisition and order attribution globally, including for visitors in Europe, before and independently of the optional-services choice. This first-party record supports internal acquisition measurement and preserves the source attached to a later account, checkout, or order. A first marketing touch is retained for up to 30 days and is not replaced by a later direct or organic visit during that period.

Optional third-party services follow a separate runtime rule:

• In the EEA, United Kingdom, Switzerland, or when the region is unknown, they wait for Allow all.
• In other regions, they can follow the regional default until you make an explicit choice.
• Only essential or a later withdrawal prevents optional third-party services from loading in every region. Global Privacy Control prevents them only outside the consent-gated regions. In the EEA, United Kingdom, Switzerland, or when the region is unknown, the current site choice controls loading, so Allow all permits configured optional services even when GPC is enabled.
• Same-origin, self-hosted, cookieless Umami can be treated as first-party aggregate measurement and run outside that gate; cross-origin or protocol-relative configurations fail closed.

Changing the optional-services choice does not delete first-party acquisition already associated with an account or preserved in an immutable checkout or order snapshot.

How We Use Information

The deployment can use information to:

• provide, secure, troubleshoot, and improve the requested service;
• manage accounts, credits, subscriptions, checkouts, and support;
• prevent fraud, abuse, duplicate grants, and unauthorized access;
• measure first-party acquisition, registration, first-generation, checkout, and purchase outcomes;
• preserve an auditable source for orders without letting a later visit rewrite prior order attribution;
• comply with legal obligations and enforce applicable terms; and
• operate configured optional services when their runtime rule permits it.

Sharing and Service Providers

Information can be shared with service providers that operate hosting, authentication, storage, email, AI generation, support, or payment functions for the deployment. Optional analytics and referral providers receive data only when they are configured and allowed to run under the rule above.

Payment providers can receive server-owned operational metadata needed to create and reconcile a checkout. Attribution authority remains the site's immutable database snapshot; provider metadata is a compact projection and recovery link, not a second source of truth.

The deployment operator must list the providers it actually uses and describe any additional disclosures required for that deployment.

Retention

The browser's signed first-touch attribution copy and an unassociated first marketing touch are retained for up to 30 days. Platform click records can expire independently under the same bounded acquisition model. Attribution already preserved with an account, checkout, payment, or financial record can be retained with that record for the deployment's operational and legal retention period.

Other account, content, security, support, and transaction records are retained only as long as needed for the purposes described by the deployment and applicable requirements.

Security

The starter uses controls such as signed HttpOnly attribution storage, server-side validation, database ownership checks, immutable order snapshots, and restricted provider metadata. No system can guarantee absolute security, and each deployment remains responsible for its infrastructure, access controls, and incident procedures.

Your Choices and Rights

You can use Cookie settings, where shown, to control optional third-party services. Global Privacy Control is honored for runtime loading only outside the consent-gated regions. In the EEA, United Kingdom, Switzerland, or when the region is unknown, the current site choice controls loading, so Allow all permits configured optional services even when GPC is enabled. These controls do not erase the site's internal first-party acquisition or order records.

Depending on where you live, you may also have rights to request access, correction, deletion, restriction, objection, or portability. Contact the deployment operator to make a request. The operator must adapt this section to the rights and verification process that apply to the deployment.

Changes to This Privacy Policy

We may update this Privacy Policy when the deployed data practices or service providers change. The current version and date will be posted on this page.

Contact Us

If you have questions or a privacy request, please contact us.