Privacy & Data Handling Disclosures

How your inputs, generated drafts, browser storage, and persistence boundaries operate across MandalaStacks.

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.

1. Core Privacy Baseline

MandalaStacks is designed as an applied workflow application for guided reasoning, mandala-based synthesis, and structured inquiry.

No sale of personal data: We do not sell, rent, or trade your personal information, inquiry text, or generated artifacts.
No mandatory account or registration: You can use the generators, inspect outputs, and export drafts without creating an account or providing an email address.
No silent cross-site tracking: We do not deploy third-party advertising cookies or cross-domain behavioral tracker networks.
Consent-governed analytics: Google Analytics 4 operates under Google Consent Mode v2 and is strictly disabled unless you explicitly grant analytics consent.

2. Generation Processing & Server Transmission

When you submit an intake form in any MandalaStacks generator, send a message in the interactive Guide chat (/guide/chat), or generate a Personal Coda, the information you enter is transmitted to application server endpoints to execute generation, format structured outputs, and evaluate concept integrity.

By contrast, initial pathway recommendations on the Guide landing page (/guide) evaluate deterministically in your browser without transmitting your question to a server.

The application does not claim that generator inputs “never leave your device.” Submissions require backend processing to produce the requested draft.

3. Five Distinct Processing & Storage Tiers

MandalaStacks distinguishes five separate tiers of data handling and storage:

Tier 1: Active Page Memory

During an active session, your entered form fields, interim state, and newly generated results are held in active React component memory. Leaving the page, closing the tab, or reloading clears this state unless it has been saved to browser storage, saved as a remote bundle, or exported.

Tier 2: Transient Browser-Session Storage (sessionStorage)

Used for short-term, single-tab continuity:

Transferring authorized intake values between tools (such as Guide to Clarity, Clarity to Decision Mandala, or Personal Coda to Alignment Audit).
Optional Personal Coda transient saves (retained under a temporary key with a 24-hour expiry marker).
Temporary draft redirection keys.

sessionStorage is isolated to the current browser tab and is cleared when the tab or browser window is closed.

Tier 3: Browser-Local Device Storage (localStorage)

Persisted locally in your browser on the current device:

Explicit Drafts: Drafts saved when you click “Save Version” or “Save Draft” (ms.generatorDrafts.v1).
Local Run History: Browser-local generated run history written when no owner identifier exists (ms.generatorNoOwnerRunHistory.v1).
Local Draft Bundles: Standardized local draft bundle mirrors (ms_bundle_*).
Saved Guide Cases: Cases you explicitly choose to save from the Guide (ms.guide.caseThreads.v1).
Guest Device Identifier: A randomly generated guest identifier (ms.deviceId.v1 / ms.guestId.v1) stored locally to identify sessions.
Analytics Consent State: Your explicit consent decision (ms.analyticsConsent.v1).

This data does not synchronize to other devices or browsers. You can clear it via in-app purge buttons or by clearing your browser storage.

Tier 4: Remote Owner-Scoped Storage (Memory Bundles)

When an owner identifier (including an automatically assigned guest owner ID) is present, generators attempt to save owner-scoped draft bundles to the server memory service (/api/memory/bundles).

Tier 5: Account Continuity & Authentication Boundaries

MandalaStacks does not currently offer a public user registration or cloud profile system for casual visitors. Self-issued guest identities provide continuity on a single device; they are not verified global user accounts and do not provide cloud account persistence.

4. Automatic Save Behavior in Generators

Generator runs attempt remote saving when an owner identifier—including a guest identifier—is present. Without one, runs use browser-local history. Standardized results may also be saved as local draft bundles. A failed remote save does not guarantee a successful local save.

Remote Memory Bundle Save Attempt: When an owner identifier (including guest identity) is active, the generator attempts to persist an owner-scoped memory bundle to the server memory API (/api/memory/bundles).
Local Run History: If no owner identifier exists, runs record to browser-local history (ms.generatorNoOwnerRunHistory.v1). A failed remote save does not write to this no-owner history.
Local Draft Bundles: Standardized generator outputs may also be saved to browser storage under ms_bundle_*.
If remote saving fails or is unavailable, the output remains visible in active page memory, and you can export your work directly as Markdown or PDF.

5. Personal Coda & Book Companion Privacy Boundaries

The Personal Coda tool operates under specific privacy and review boundaries:

No Automatic Remote Save: Generating a Personal Coda sends intake fields to the Personal Coda endpoint to produce a provisional mirror draft. It does not write your intake or output to a permanent remote database.
Explicit Transient Save: After accepting a Coda, you may optionally save it to browser sessionStorage. This creates a temporary key with a 24-hour expiry marker.
Review States:
- Accept: Moves the draft into explicit save, export, or handoff controls.
- Reject: Excludes the draft from the finalized flow and blocks in-site saves or handoffs.
- Do not reuse: Disables transient saves and downstream generator handoffs for the draft.
- Purge: Clears the saved Coda from browser sessionStorage.
Session Handoffs: Cross-tool transfers (e.g., from Guide or Personal Coda to Alignment Audit) use ephemeral single-session browser storage upon explicit user action rather than URL query parameters, keeping reflection text out of URLs and browser address history.

6. Data Retention, Export & Deletion Controls

We describe only implemented retention controls without inventing speculative guarantees:

Exporting: You can download generated drafts, mandalas, and reports directly to your local file system as Markdown (.md) or PDF at any time.
Local Storage Deletion: You can clear browser-stored drafts and run histories via in-app controls (such as the Run History modal and Personal Coda purge) or by clearing your browser site data.
Unresolved Terms & Server Logs: Standard web hosting infrastructure logs (IP addresses, user-agent strings, request paths, and error traces) may be recorded for security, abuse mitigation, and operational diagnostics. Retention periods for operational server infrastructure follow hosting provider defaults; we do not promise instantaneous deletion of transient server logs.

7. Contact & Privacy Inquiries

If you have questions, corrections, or concerns regarding data handling or privacy on MandalaStacks, please contact:

Email: hello@winmedia.com

Website: winmedia.com/contact

Note: The hello@winmedia.com address is maintained for general project correspondence and inquiries. It does not constitute an SLA-governed 24/7 dedicated support desk.