Data boundaries (plain English)

Principle

Your team’s data stays your team’s data. We will be explicit about what is stored, what is sent to models, and how you can export or delete.

What we store (v0 intent)

• Workspace content you intentionally create/import (notes, decisions, provenance links, artifacts).
• Minimal account/workspace metadata required to operate the service.
• Optional telemetry/analytics only if enabled (to improve reliability and UX).

This is directional for v0; specifics will be finalized before we onboard paying teams.

Early access form data

When you submit the early access form, we collect:

• Email address — to contact you about early access.
• Optional fields — company size, role, pain points, and current tools (only if you provide them).
• IP address and browser info — processed by Cloudflare and Turnstile for delivery, spam prevention, and abuse detection. These details are not stored with your signup record.

We will never sell your email or share your information with third parties. To request deletion, email privacy@digitalmeld.io.

Landing site analytics

Digital Meld uses its self-hosted OpenPanel service to record page paths, page titles, a stable BrainMeld landing identifier, and limited interaction events such as early-access, booking, and social-link clicks. Analytics events never include early-access form values, URL query strings, or URL fragments.

Microsoft Clarity also runs on the landing page to help us understand aggregate use and usability. It may process ordinary browser, device, and interaction details under Microsoft's terms.

What we may send to models

When AI assistance is used, we may send only the minimum necessary context to generate the requested output. We’ll make this explicit in product UX (what’s being sent and why).

• We will prefer provider configurations that avoid training on customer data where available.
• We’ll add workspace controls so teams can restrict or disable model calls by policy.

What we will never do

• Sell your private workspace content or documents.
• Share your workspace content with other customers.
• Hide data handling in vague language — we’ll keep this page updated as reality changes.

Export and delete

Teams need an exit ramp. We intend to support export and deletion flows early.

• Export: structured formats (JSON/Markdown) where feasible.
• Deletion: workspace-level deletion with clear confirmation.