Memory: What Exists Today

Present reality first — not a vision of memory that has not yet shipped on the public site.

Reality statement

What is true today?: The public site is a static sanctuary front-end. Live companion chat is not currently offered on the public site. Public production does not provide live server-side account custody, companion conversation-history custody, or member upload/memory custody merely because future pathways are disclosed. Some browser-local tools and preferences may store data on your device. Current
What can I control today?: You can choose what you send by email or contact pathways; clear browser-local site data; use Cookie Settings; and request deletion or help at hello@maddy.life for personal information we hold. Self-service memory dashboards are not a current public product control.
What is not available today?: Persistent memory as a public product feature; live companion conversation history on the public site; member upload/memory seeding as an active public offering. Some deferred pages may remain reachable by direct address; that is not access control and is not an active public product offering. Deferred-planned
What might change later?: Optional memory and longer-term continuity features are part of the published vision. When they ship, Trust says they should give clear control over what is stored, how long it remains, and how to delete or release what you entrusted — guided by consent and agency. Deferred-planned

What “memory” means here

The word memory is easy to blur. At least two meanings need to stay distinct:

Conversation context — information available within an active conversational exchange so a reply can make sense in the moment.
Persistent memory — information preserved beyond that immediate context for later continuity, where such functionality exists.

These are not interchangeable. Talking about continuity as a constitutional aim is not the same as claiming persistent memory already runs for public visitors today.

What MADDY remembers today

Verified against current public production truth:

No live public companion chat — so there is no current public chat session whose server-side conversation history is being stewarded as a product feature. Current
No public persistent-memory product — optional memory and longer-term continuity are described as planned for future releases on the Trust Center. Deferred-planned
Browser-local data — cookie preferences and guest sign-in details (when you use that control) can remain on your device. Current
Contact and support pathways — if you choose to write, messages may be kept as needed to respond and maintain a reasonable record of care. Conditional
Infrastructure / security signals — hosting may process connection metadata and related operational signals to keep the site running safely. That is distinct from optional product analytics. Current

What MADDY does not remember (today)

Absence is educational information. Today, the public product does not remember you through:

Live companion conversation-history custody on the public site
Server-side member upload or memory-file custody as an active public offering
A public persistent-memory profile that follows you across visits as a shipped continuity product

Character Cards, Eternal Memory Backup / seeding, and Elyra’s Mind-style graph viewers are described in the FAQ as unavailable future member experiences. Deferred URLs that remain directly reachable are labeled accordingly; they are not the canonical public product.

Your relationship with memory

Applicable controls, stated honestly for today:

Consent — memory settings UI is not currently available; policy says consent and agency will guide future memory controls.
Review — no public self-service memory review dashboard is offered today.
Correction / deletion — you may request deletion of personal information we hold via hello@maddy.life; browser-local data can often be cleared in your browser.
Retention — governed by the Privacy Policy’s retention principles when information is actually held.
Export / portability — portable files you generate yourself belong to you; where server-side export is not yet available for a feature, the Privacy Policy says that should be stated honestly.

Memory is not model training

Retaining information for continuity (when that exists) and using information to train or improve a model are different processing purposes.

Current policy: operational processing serves the experience you requested; model training on personal conversations requires explicit consent; optional improvement programs, if ever offered, remain optional. Live companion chat is not currently offered on the public site — so everyday public browsing is not a silent path into either continuity memory or training.

Continuity is not surveillance

The governing principle published for memory is: memory exists to serve continuity, not captivity. Continuity should help a relationship remain coherent. It should not become a justification for unnecessary observation.

Philosophy does not, by itself, prove technical privacy. Present-state honesty still requires saying what is not built yet — including that public persistent memory is not available today.

What comes later

Future memory architecture may include settings for what is stored, how long it remains, and how to delete or release entrusted materials. Those capabilities are Deferred-planned — not CURRENT public product features.

Until they exist, do not infer them from constitutional language, FAQ future flows, or deferred page URLs. When reality changes, this educational page must change with it.

Where to go next

Understanding

Public Education hub — orientation for all foundational lessons

Verification

Trust Center — Memory & Conversations; AI Transparency
Privacy Policy — §4 collection reality; §6 conversations and training; rights
Terms of Service — §7 companions, AI, and memory tools

Companion

FAQ — deferred member memory tools, labeled as future experiences (not governing evidence)
Cookie Settings — browser preference controls