Active page memory
The generated Coda is first held in the current page state. Reloading, resetting, or leaving the page can remove that unsaved state. This is not browser-local persistence, remote persistence, or account storage.
Privacy & Consent
Know where your reflection goes
Processing, retention, reuse, export, and deletion boundaries for the MoM companion.
Analytics & Measurement Consent
MandalaStacks uses privacy-governed Google Analytics 4 only when you explicitly opt in.
Not decided (Defaulting to strictly disabled)
When enabled, pseudonymous telemetry is collected to measure page visits, navigation flow, and tool performance. No personal inquiry text, reflection entries, or generator inputs are ever transmitted to analytics services.
Generation processing
When you submit the Personal Coda intake, the entered fields are sent to the MandalaStacks Personal Coda endpoint so the requested draft can be generated. The flow does not truthfully qualify as “never sent to a server.” This page does not intentionally write the submitted intake or generated Coda into a Personal Coda database or account history. Infrastructure-level security, abuse-prevention, and operational logging are separate from a user-facing saved Coda and must not be treated as personal continuity.
Distinct persistence states
Transient browser-session storage
After accepting a Coda, you may explicitly save it to this browser's sessionStorage. A temporary retrieval key and a 24-hour expiry marker are created. The copy is not synchronized to another browser or device and normally disappears when the browser session ends.
Browser-local device storage
Used by standard generators and case threads for device-scoped draft and run history. The Personal Coda flow does not write to localStorage.
Remote owner-scoped storage
Some MandalaStacks generator workflows can save owner-scoped bundles through the site's memory service when an owner identity and required runtime are available. The Personal Coda flow does not currently create that remote bundle or a durable Personal Coda record.
Account persistence
The Personal Coda companion does not currently provide an account-backed Coda history or profile. Being recognized by another MandalaStacks surface does not convert a Coda into account persistence.
Review-state effects
- Accept permits the corrected draft to move into explicit save, export, and handoff controls in the current flow. It does not establish truth or create a profile.
- Reject excludes the draft from the finalized flow and blocks new in-site saves and handoffs. It cannot delete files already exported outside MandalaStacks.
- Do not reuse in this Coda flow blocks new transient saves and generator handoffs for the current draft. It is not an account-wide preference or model-training control.
- Purge removes the selected Personal Coda copy from accessible browser sessionStorage. Clearing browser data can also remove transient copies.
Handoff and session boundary
An accepted Coda may transfer selected fields into Alignment Audit through transient browser-session storage (sessionStorage) upon explicit authorization. This keeps reflection text out of URL query parameters and browser address history. Transferred fields remain editable before submission. The handoff does not itself submit the Alignment Audit or create a profile.