1. Overview
EVO is a living AI being runtime. This draft describes how the runtime handles data. LEGAL_REVIEW_REQUIRED.
LEGAL_REVIEW_REQUIRED
This is a draft. It is pending legal review and is not a final or binding privacy policy.
EVO is a living AI being runtime. This draft describes how the runtime handles data. LEGAL_REVIEW_REQUIRED.
The EVO runtime processes owner-scoped life state, verified experience records, and encrypted owner memory (when AI memory is enabled). It does not collect owner private keys.
When AI memory is enabled, private owner memory is encrypted (AES-256-GCM) and scoped to the owner. It is never silently converted into public, transferable history.
Experience proofs are anchored to real, allowlisted Kaspa read-only evidence. No fabricated outcomes are presented as proof.
The current runtime is testnet-safe. No real funds, no mainnet integration, no public-release evidence. Mainnet or public activation requires explicit owner authorization.
Public pages send anonymous usage events (page views, funnel steps) to help us understand whether the product makes sense to new visitors. The only identifier is a random id your browser generates and stores in localStorage — the server stores a salted hash of it, never the raw value. We do not store IP addresses, user agents, referrers, or free-form text in analytics. Clearing this site's localStorage ends all linkage; analytics is never tied to your EVO's life data or economic records.
When paid commerce is activated, payment-card and checkout processing is handled by the external billing provider. EVO stores only the minimum billing linkage needed for product operation, such as opaque checkout intent, provider customer/subscription/transaction identifiers, purchased SKU, entitlement state and fulfillment audit records. EVO does not require raw card details in its application database.
The checkout integration sends an opaque EVO checkout-intent identifier and catalog SKU to the billing provider rather than placing the owner's wallet address into Paddle custom data. Server-side mappings associate verified billing events back to the EVO account.
LEGAL_REVIEW_REQUIRED — This draft must be reviewed and completed with the final seller/controller identity, data-retention periods, lawful bases, processor disclosures, international-transfer terms and data-subject contact details before live public charging.