Trust center
Privacy and cookies
Last updated: July 30, 2026. This plain-language implementation summary is an informational template, not legal advice, a privacy notice for every jurisdiction, or a compliance certification.
Information Aevum currently receives
Aevum may receive account details, email and marketing-consent records, general-wellness context submitted in the Snapshot or Blueprint, manually added or uploaded health-data context, referral codes, partner inquiry details, and product-use events. Do not submit emergencies or information you do not want used for the requested experience.
Why it is used
Information is used to provide the requested account or educational wellness experience, record newsletter or early-access interest, maintain verified referral attribution, deliver transactional confirmations, improve the product, and review aggregate growth signals. The founder analytics view is designed not to show customer names, emails, or individual assessment responses.
Cookies and analytics choice
Essential authentication and security cookies may be used to provide requested site functions. When configured, PostHog analytics is optional: the site presents an analytics choice before initializing PostHog or recording optional client analytics. You can keep optional analytics off or clear the site preference in your browser to see the choice again. Read the Cookie Policy for the current technical scope.
Newsletter, referrals, and communications
Newsletter and early-access forms use a separate checkbox for newsletter, product, and promotional communications. A confirmation email is transactional; promotional communications depend on that form choice. Referral attribution is recorded only for the early-access program and remains subject to the stated referral terms. You can opt out of marketing communications by replying to an Aevum email.
Access, export, and deletion requests
Self-serve account deletion and data export are not implemented. You can request reasonable access, export, correction, account removal, or deletion assistance through Aevum's working contact flow; include the email used with Aevum and the request type. Aevum will review requests through its existing contact process. Response timing, identity verification, retention exceptions, and jurisdiction-specific rights procedures still require operational and legal review.
Third parties and future integrations
Aevum uses MadeThis-supported infrastructure for supported transactional notifications. Wearable, laboratory, marketplace, advertising, and provider integrations are not represented as live unless stated at the point of use. Any future integration requires its own implementation, disclosures, and review.
Questions
Review the Terms of Use and AI and Health Disclaimer before using Aevum.