Data Handling
AlphaBase is local-first, but a local runtime can send workspace content and conversation context to services you connect. The exact recipients and retention period depend on the selected provider and deployment. Check the effective configuration before using sensitive workspaces.
| Workflow | Data that may leave the runtime | User control |
|---|---|---|
| Model inference | Prompts and selected context, including file excerpts and tool results | Choose a provider and model with an acceptable data policy; avoid attaching sensitive content |
| MCP and external tools | Tool arguments and any context sent in a tool call | Review servers, credentials, and per-tool permissions; disconnect services you do not need |
| Session sharing | Session metadata and messages needed to render a public link | Use manual sharing or set share to disabled before creating new shares |
| Hosted runtime or gateway | Session and execution data handled by that deployment | Confirm the operator’s location, access, retention, and deletion policy |
| Optional learning or synchronization | Eligible knowledge or session-derived data when enabled | Check whether the deployment enables it and obtain its consent and deletion terms |
Disabling a feature may stop future transfers without deleting data already sent. For existing shares, provider records, hosted sessions, or synchronized data, request the applicable retention and deletion procedure from that service’s operator. AlphaBase cannot promise a single retention period or deletion path for every external provider and deployment.
See Share, Providers, MCP Servers, and Security.