Account data
Fabus stores the identity, workspace, billing, and usage metadata required to operate balances and API access.
PRIVACY
/ FABUS.
How identity, payment, and usage data move through the routing fabric.
Request content
Raw prompts are not stored by default. Optional retention features, when enabled, are presented as explicit workspace controls.
Usage ledger
Usage records can include timestamps, model routes, token counts, latency, key identifiers, and response status for accounting and diagnostics.
Payment records
Payment references and transaction identifiers are retained where necessary to reconcile token credits and prevent duplicate settlement.
Service providers
Infrastructure, authentication, payment, and model providers process only the data required for their part of a request.
User control
Workspace owners can revoke API keys, rotate access, and request account support using the verified identity attached to the workspace.