Privacy Policy
An honest account of how data is handled across the AVAM website and personal AI ecosystem.
This website (avam.buzz)
This website is a static publication. It does not use analytics, session cookies, tracking cookies, or any third-party monitoring scripts. No personal information is collected, processed, or stored by this website.
Contact form
The contact form on this website does not currently transmit personal information to any server or third party. Form submissions are not processed or stored. This policy will be updated if a working submission service is activated.
The AVAM personal AI system (Larry)
Larry is a private, single-user personal AI system. It processes personal data belonging to Mike Oh, including:
- Calendar information (read-only from a connected calendar service)
- Email content (read and draft only—messages are never sent autonomously)
- Health and biometric data (from wearable devices and a connected health platform)
- Financial context (from manually maintained records and public market data)
- Journal and task records (created directly by Mike within the system)
- Conversation history (archived nightly as episodic memory)
This data is stored in a private database accessible only to the AVAM system and Mike Oh. It is not sold, rented, or shared with any third party.
External AI and service providers
Larry uses external AI model providers to generate responses, perform analysis, and synthesise research. These providers handle data according to their own published privacy and retention policies.
AI call observability
AI call metadata is logged by an observability tool running on a self-managed private server operated by Mike Oh. This logging is used for monitoring, debugging, and cost tracking only.
Health and biometric data
Health and biometric data is stored in Larry's private database. It is not shared with any third party beyond the AI model providers required to generate health summaries or threshold alerts.
Community data (Max)
Max handles information relating to Mike's community initiatives and mentoring relationships in a separate data context, governed by confidentiality as a founding constraint.
Data retention
No data is retained longer than operationally necessary. A memory hygiene job runs weekly to purge orphaned records from the knowledge base.
Security
The AVAM system applies TOTP multi-factor authentication, session expiry, CSRF protection, webhook secret verification, and TLS encryption for production endpoints. Full details are in the Principles section.
Your rights
If you believe you have a privacy concern related to information held in this system, please contact Mike Oh via the Contact page.
Changes to this policy
This policy will be updated when material changes occur to data collection, processing, or the activation of new services.
See also: Disclaimer · Our Principles · Contact