Mad Fish Elements
HomeTrust CenterData handling

Data handling

What enters the platform, where credentials and authorization records are stored, and how requests move through the MCP gateway.

Data lifecycle

Mad Fish Elements stores the minimum control-plane data needed to connect an account, authorize a user, and synchronize policy to the MCP gateway. Connected-service data is requested on demand and is not copied into a general-purpose training corpus.

Customer administrators control which platforms are enabled and which connections each member can see. Capability settings are synchronized to the gateway and take effect on subsequent requests.

01

Authorize

A user completes provider OAuth or an administrator saves a scoped provider credential.

02

Store

Raw secrets go to Key Vault; the portal retains references and configuration metadata.

03

Synchronize

Organization, user, token-hash, platform, and capability state is pushed to the MCP control plane.

04

Execute

The gateway validates identity and policy before a connector calls its provider API.

Stored data by layer
LayerDataProtectionLifecycle
Portal databaseOrganization, user, connection metadata, capabilities, OAuth client records, token hashesRole-based portal accessAccount and audit lifecycle
Azure Key VaultProvider access tokens, refresh tokens, API keys, and credential setsEncrypted secret storage and managed identityVersioned; deleted or replaced on detach/rotation
MCP cacheToken hashes, organization/user mappings, and scoped capability configurationPrivate service access and expiring entriesRefreshed by portal synchronization
Provider request pathTool arguments and provider responses required for the selected operationTLS and provider authorizationProcessed for the request; logs are redacted

OAuth and key handling

Only hashes are persisted for MCP credentials

OAuth access tokens and portal-issued API keys are synchronized and looked up by SHA-256 hash. Raw OAuth access tokens are returned to the client at issuance and are not stored in plaintext in the OAuth token table.

Short-lived access, rotating refresh

OAuth access tokens expire after 28,800 seconds (8 hours). Refresh tokens expire after 7,776,000 seconds (90 days) and are single-use when rotated.

Detach and revoke

Explicit revocation disables the token immediately. Detaching a provider removes its active credential path and schedules the updated organization state for synchronization.