Privacy & cookies
A clear description of the data used by this customer platform. The final controller details, retention schedule and legal bases require review before launch.
Draft for review
This page describes the planned service and outstanding policy decisions. It must be finalized for the operating business before paid sales begin. Checkout remains disabled until the launch requirements are completed.
Account and purchase data
This platform stores names, email addresses, password hashes, verification state, sessions, order records, payment status, license records, support messages and audit events. Passwords are hashed; they are not sent by email. It does not need your broker password, AI provider API key or wallet seed phrase for a software purchase.
Installation privacy
Device licensing uses an installation-generated public key and an optional device name. It does not collect motherboard identifiers, disk serial numbers or MAC addresses. Activity timestamps and activation history help manage license access and detect abuse.
Essential cookies
A session cookie keeps you signed in. Production cookies use Secure, HttpOnly and SameSite protection. The current platform does not include advertising trackers or analytics cookies. Additional non-essential tracking should not be enabled without a reviewed consent and disclosure plan.
Service providers and security
The deployment can use a database host, private file storage, a transactional email service and a crypto payment processor. Email includes account links; payment verification includes invoice and order references. Actual providers and transfer locations must be listed for the final deployment. Rate limiting uses keyed hashes of request identifiers where configured.
Your account and requests
Use account settings to update your name, change your password and manage sessions. Contact support for other access, correction or deletion requests. Accounting, abuse investigation and transaction records may require different retention periods; the final policy must state them.
Information required before launch
Data controller identity and contact; privacy contact; purposes and legal bases; actual sub-processors; retention periods; international transfers; rights and request handling; incident contact. No jurisdiction-specific rights or legal conclusion are fabricated here.
Need help?
Use the support area for account and order questions.