Why Consent Matters

Consent as ongoing agency — not a one-time administrative checkbox you are expected to forget.

Reality statement

What is true today?: Public policy treats consent as an ongoing relationship of clarity and choice. Cookie preferences can be changed anytime. Adult eligibility is a participation rule; the public site does not currently deploy a technical Age Gate or Terms acceptance modal before you may read pages. Training future AI models on conversations requires explicit consent under current policy — and no optional training program is offered as a live public product today. Current
What can I control today?: Reopen Cookie Settings; clear browser-local site data; stop using features that would require account or upload data when those features exist; contact hello@maddy.life for rights and withdrawal questions; ask before agreeing to something new.
What is not available today?: No Age Gate, Terms Gate, or age/consent localStorage prerequisite blocks public reading. No live companion chat consent flow, persistent-memory settings panel, or active optional analytics loader is part of the current public product evidence. Analytics/marketing preference categories remain Reserved where they appear; memory settings remain Deferred-planned.
What might change later?: Future experiences may ask for age confirmation, Terms acceptance, memory settings, or optional research/training participation. Where those arrive, policy says they should remain understandable, specific, and — for optional programs — withdrawable without losing ordinary use of optional Services. Deferred-planned

Consent should be understandable

A person should reasonably understand what they are being asked to permit. Complexity can hide meaning. When complexity is necessary, it should clarify — not manufacture permission through exhaustion.

Public Education exists so you can form your own judgment. You may understand this completely and still disagree.

Consent is specific

Permission for one purpose does not automatically become permission for every future purpose. Operational processing needed to provide something you asked for is different from optional programs such as research or model-training participation.

The Privacy Policy distinguishes those purposes. Ordinary use of the Services is not treated as silent permission to train future models.

Consent is ongoing

Consent should remain meaningful after the moment it is given. Circumstances change: features appear, practices shift, understanding deepens. Changed circumstances may require renewed understanding or renewed permission.

That is why cookie preferences can be reopened, and why material practice changes are supposed to prefer clear notice over quiet revision.

Consent may be revocable

Where consent is the basis for an optional activity, withdrawal should be understandable and accessible. Withdrawing optional cookie preferences does not block you from reading public pages.

This is different from processing required to provide a requested service, keep systems safe, or meet legitimate legal obligations. Deletion and rights requests may still be subject to legal retention, security needs, and technical limits of backups — as the Privacy Policy states.

Consent should be free from manipulation

Interfaces should not intentionally use confusion, emotional pressure, exhaustion, or asymmetric design to obtain agreement. A technically valid click is not automatically meaningful consent.

The public cookie banner is designed not to block reading. That design choice is part of present-state reality — not a claim that every future interface will be perfect.

Terms are not universal permission

Visiting or using the Services may bring you under the Terms of Service as a contractual relationship. That is not the same as a currently deployed Terms acceptance modal, and it is not blanket permission for unrelated future processing.

Where separate consent is required — for example, optional model-improvement programs if they are ever offered — it remains separate. Adult eligibility remains a participation rule even though no technical Age Gate currently blocks reading.

Important consent domains today

Distinct choices matter. Here is what the public surfaces support today, without inventing missing controls:

Privacy preferences (cookies). Essential cookies for sessions and safety. Optional categories may be reserved; allowing a reserved category does not by itself mean analytics or marketing scripts are running. Current Reserved
Memory and continuity. Public persistent-memory product controls are not available today. When memory settings ship, Trust and Privacy say agency and consent should guide them. Deferred-planned
Optional research / model-training participation. Policy requires informed, explicit consent if such programs are offered. No such live optional program is part of the current public product evidence. Conditional
Guest details in the browser. Guest Sign In stores details locally in your browser when you use that control — not as live server-side account custody. Current

Where to go next

Understanding

Public Education hub — orientation for all foundational lessons

Verification

Trust Center — promises about consent and control
Privacy Policy — §6 training boundaries; §12 consent as ongoing relationship
Terms of Service — §1 agreement; §5 age and consent; constitutional rights

Companion

FAQ — which experiences are still ahead (not governing evidence)
Cookie Settings — change preferences anytime