Privacy follows the deployment boundary.

This product site stores browser preferences and local preview data. A configured server stores account-scoped records and accepted inquiries according to the policy below; model exchanges require current audit consent and encryption. If you click through to GitHub, GitHub's own policies apply. Repository metadata is requested from GitHub's public API; unavailable data may use a labelled build-time snapshot.

We do not invent a hosted analytics program here. If this deployment injects platform tooling outside MLAI's source, that tooling is not an MLAI product claim.

1. 1.Data collection

   The static preview stores browser preferences and local preview data. A configured server can store account data, field notes, chat consent and audits, inquiries, telemetry events, and workspace connection records according to the features used. These records have different storage and retention boundaries.

2. 2.Account and authentication data

   Protected account features use Better Auth. Supported social methods depend on configured credentials; passkey and email/password paths are defined in source. Server model-request builders do not automatically add your account email; content you submit may still contain identifying information.

3. 3.Model calls

   Console Chat, persona chat, configured desk requests, and workspace Ask Abbey can send submitted content to xAI or Gemini through Cloudflare AI Gateway, after the shared consent and audit checks. Desk requests include catalog excerpts. Workspace Ask Abbey sends the document title, its first 800 body characters, and your question; editing alone stays in this browser. An unconfigured desk answers from the catalog without a model call or conversation audit. Static preview functions do not call the website model server. The separate local Quasar service uses its own configured Anthropic provider.

4. 4.Security and retention

   Conversation audits and workspace refresh tokens are sealed with AES-256-GCM and bound to owner and purpose. The four website model surfaces refuse without audit encryption and current consent, and withhold a model reply if its audit cannot be stored. Audits have a 365-day expiry; automatic deletion requires the configured expiry endpoint and scheduler. Owners can inspect, export, and delete their audits. Contact inquiries are separate unsealed application fields.

5. 5.Inquiries, telemetry and connected sources

   On the static preview, contact requests an email draft and does not confirm delivery. The configured server can store inquiry name, email, project context, and message after its validation and rate-limit checks, with Turnstile when configured. Workspace connections store a sealed refresh token and connected account metadata. Disconnect and expiry behavior depend on the respective configured features.

6. 6.Deleting your account

   You can delete your account from your profile. That removes the account, its sessions, your field notes, chat consents, encrypted audits and workspace connections, and revokes any Google grant it held. Contact inquiries you sent are kept as business records, with your account detached from them.

7. 7.Contact

   For privacy requests, security questions, or data-handling reviews, contact cbkshadow@icloud.com or 813-755-0156.

• Local processing

  ABI, Abbey, and WDBX are built to run on operator-owned machines. Cloud backends are optional.

• Operator-owned memory

  WDBX stores, episodes, evidence payloads, credentials, and runtime data stay private to their owners. Public repos are source, not a hosted database.

• Controlled writes

  Persistence that is skipped or unavailable is not reported as a successful write. Admission checks reject replay and stale policy/consent bindings.

• Provenance

  Content addressing and signatures support later inspection. They do not make a stored statement true.

• Permissions

  The separate local Quasar service binds to loopback by default and requires a pairing token for its APIs. Non-loopback exposure requires explicit opt-in and an HTTPS public origin. Generated code runs as the operator; pairing is not an operating-system sandbox.

• Model selection

  Local models are optional. Live providers require stored credentials. This website does not broker them.