Privacy notice
A transparent draft of what the current marketing, creator, and licensed-delivery paths store—and the decisions still required before production launch.
- Effective
- Not yet effective
- Last revised
- September 3, 2026
Scope
This draft describes the current development marketing website and contact inquiry path. It is not an effective production privacy notice and must be reviewed against the final company entity, hosting regions, subprocessors, analytics, payment providers, support tooling, and launch jurisdictions.
Information currently collected
The contact form stores the name, email address, optional company, selected topic, and message that a visitor submits. Marketplace creator applications store the submitted name, email address, proposed seller name, website and portfolio links, intended product type, and experience statement. These forms also store keyed one-way fingerprints derived from the request address and browser identifier for abuse prevention; raw IP addresses and raw browser strings are not retained in the form records.
Marketplace customer accounts store a display name, email address, slow password hash, account and lockout state, organization purchase role, and digest-only session evidence. Checkout requests store the selected listing and immutable version, amount, currency, organization, provider state and an idempotency key. Passwords and session tokens are never stored in plaintext.
Licensed marketplace delivery stores a one-way digest of the license key rather than the submitted key itself. It also records the related order, listing and package version, delivery status and timestamps, and keyed request fingerprints needed to apply rate limits and investigate abuse.
Why it is used
Submitted contact details are used to classify and respond to product, agency, marketplace, developer, or security questions. Creator application details are used to review marketplace eligibility and, when approved, create the associated seller account. License and delivery records are used to verify purchase rights, provide packages, prevent replay, and maintain an audit trail. Keyed fingerprints are used to enforce bounded submission and download rates and detect repeated requests.
Storage and retention
Contact inquiries, creator applications, license records, delivery grants, and their audit events live in the private control-plane database. Marketplace package archives remain in private storage and are released only through short-lived, single-use grants. A production retention schedule, deletion workflow, backup lifecycle, and regional storage policy must be approved before launch; this draft does not invent those commitments.
Sharing and processors
No production processor list is asserted yet. Before launch, this notice must identify every enabled hosting, email, analytics, payments, media, search, support, security, and infrastructure provider and explain the relevant data flow.
Choices and rights
Production contact details and jurisdiction-specific access, correction, deletion, portability, objection, and complaint instructions will be added after the operating entity and launch regions are approved.
Security
Current controls include data minimization, keyed request fingerprints, bounded validation, rate limiting, private database storage, and server-side handling. No system can promise absolute security, and this draft is not a certification.
Changes and contact
This page will receive a real effective date, policy owner, contact channel, company identity, and revision process before production launch.