Genesis includes real accounts, secure sessions, optional linked wallets, payments, and user-authorized connections. This policy describes those current data flows directly.
Public browsing does not require an account. When you create an account or use a protected Genesis capability, Genesis processes the minimum account, payment, connection, and proof data needed to provide that capability and keep its state accountable.
If you create an email account, Genesis stores the email address and a one-way password verifier, not your plaintext password. Your account also has a Genesis identity and may include public wallet addresses you explicitly prove and link.
After you authenticate, Genesis uses a secure, host-scoped session cookie to keep protected requests bound to your account. The session is not exposed to page scripts and expires automatically.
When you choose card checkout, the configured payment provider receives the information needed to process the purchase. Genesis keeps the minimum payment and access state needed to reconcile what your account is entitled to use. A checkout return alone never activates access.
If you choose a wallet payment, Genesis processes your linked public address, selected network, transaction identifier, and the public settlement evidence needed to verify the payment. Genesis does not ask for or custody your wallet private key.
When you connect an outside service, Genesis processes the permissions and credentials required for that connection. Those credentials are used only to perform actions you authorize through the connected service and are not treated as authority merely because they exist.
Hosting and security infrastructure may record standard request information such as network address, route, time, status, and security events. Genesis also keeps the receipts and state required to reconcile access and verify consequential operations.
Examples can include hosting providers, Stripe for hosted card checkout, Google or GitHub when you explicitly choose those sign-in methods and they are configured, a public blockchain network when you choose wallet payment, and Google Fonts for typeface delivery. Their own policies govern information they receive directly.
Creating an identity does not authorize unrelated actions. Linking a wallet does not authorize a charge. Returning from a payment provider does not activate access; Genesis waits for authenticated payment evidence. Signing out clears the browser session. Where a self-service lifecycle control is not yet exposed, use the current Genesis contact channel for an account or privacy request.
Genesis does not require third-party advertising trackers to operate the account, payment, wallet, or connection flows described here, and Genesis does not sell personal data for advertising. If that product posture changes, this policy must change with it.
Enterprise or professional work may involve additional data, retention, security, residency, or processor terms defined by the engagement agreement. Those terms supplement this policy rather than silently expanding the public product's permissions.
Buy access or a scoped assessment by card. Access activates only after verified settlement — and every step returns a receipt.
Buy Genesis access → Buy the Assessment →