Purchase and key delivery
PRO purchases use Gumroad, and Gumroad emails the purchaser a license key. The final policy must explain the respective roles accurately.
Legal review template
Privacy Policy — OWNER-FILL
This review page separates documented product behavior from the privacy decisions the owner still needs to verify and finalize. It is not a completed privacy policy.
Owner information checklist
What must be decided.
Replace each placeholder only with accurate, reviewed wording that matches the product, website, storefront, and support process.
- □Data controller or owner identity and official privacy contact.
- □Complete website data inventory, including hosting and server logs.
- □Complete app, activation, licensing, and version-check data inventory.
- □Support-bundle and other diagnostic-data handling after a user shares it.
- □Discord/community and Gumroad storefront responsibilities and links.
- □Cookie, analytics, tracking, and consent behavior, if any.
- □Purposes, legal bases if applicable, recipients, and third-party sharing.
- □Retention and deletion periods for every data category.
- □Security practices stated without guarantees.
- □User rights, minors, international use, effective date, and update process.
Verified operational context
Current behavior the policy must match.
Activation behavior
Activation sends the license key and a machine fingerprint for machine binding and performs a version check. Background license re-checks can occur while online.
Local product data
The public source says benchmark scores, applied settings, and logs stay on the user's PC. Share My Score is created locally and shared only when the user chooses.
User-controlled diagnostics
Export Support Bundle creates a sanitized diagnostic archive. The user controls whether and when that archive is sent for troubleshooting.
Support and public sharing
Discord is a documented community/support route. Users should not post license keys, passwords, payment details, or other private information publicly. This template does not define Discord's or Gumroad's separate privacy practices.
Privacy outline
Sections awaiting verified policy details.
These prompts are deliberately incomplete. They do not claim whether the deployed site uses analytics or cookies, set retention periods, promise security, or assert GDPR/CCPA compliance.
OWNER-FILL
Data controller / owner identity
Add the responsible legal person or entity, jurisdiction, and official privacy contact. No identity or address is assumed.
OWNER-FILL
What the website collects
Inventory hosting logs, form submissions, traffic data, and any other website collection. Do not infer the answer from this static page.
OWNER-FILL
What the app collects
Confirm every app data category and network action against the current release before publishing the final policy.
OWNER-FILL
License and activation data
Define the purpose, recipient, handling, retention, and user choices for license keys, machine binding, activation, and version checks.
OWNER-FILL
Support bundle and diagnostics
Explain what happens after a user chooses to create and share a support bundle, including recipients, use, storage, and deletion.
OWNER-FILL
Discord and community data
Describe the owner's role, Discord's role, community visibility, moderation records, and the applicable external policy links.
OWNER-FILL
Gumroad and payment data
Describe Gumroad's role in purchases, key email, receipts, payment information, and refund requests. Do not claim the site receives or stores payment details without verification.
OWNER-FILL
Cookies, analytics, and tracking
State whether any are used only after the website stack and deployment are verified. Add categories, purposes, controls, and consent details if applicable.
OWNER-FILL
Log files
Document website, application, licensing, and support logs separately, including contents, purposes, access, and retention.
OWNER-FILL
How data is used
List each actual use and connect it to the corresponding data category. Do not add broad future uses.
OWNER-FILL
Sharing with third parties
Name verified recipients and purposes. Distinguish storefront, community, hosting, licensing, support, and legal disclosures as applicable.
OWNER-FILL
Retention
Add specific, accurate retention or deletion rules. No period has been supplied for publication.
OWNER-FILL
Security
Describe actual safeguards in measured terms. Do not promise encryption, absolute security, certifications, or audits without current evidence.
OWNER-FILL
User rights
Add rights, request steps, identity verification, appeal routes, and response timing appropriate to the owner's actual obligations.
OWNER-FILL
Children and minors
Set the applicable age approach and parental-consent rules after legal review. No age threshold is assumed here.
OWNER-FILL
International users
Address transfers, locations, and jurisdiction-specific disclosures only after the relevant facts and obligations are known.
OWNER-FILL
Contact and effective date
Add the official privacy contact, effective date, revision history, and notice process.
Finished public information
Use the product pages for current guidance.
These legal templates do not replace the current support, setup, safety, or product guidance.
Need current help?
Use Support or check the FAQ.
Until this template is finalized, use the finished help pages for product and account guidance. Do not send license keys, passwords, or payment details publicly.