Trust Center

SealRoute AI Hub Trust Center

Review current SealRoute AI Hub capabilities, data boundaries, and verifiable records. We only state protections that are implemented and reviewable.

Current statusLoading

Current Status

Current capability status

Waiting for updateThis is a current capability snapshot, not historical uptime or an SLA.
Loading public status

Model Status

Current trusted-model status

Waiting for detection dataStatuses come from point-in-time probes, not continuous uptime or an SLA.
0Recommended
0Observing
0Paused
0Pending
0Current probes
0Expired probes
0Freshness unknown
0Provider models
Loading trusted-model status
Sign in to choose a model

Security Boundary

Clear boundaries enable correct use

SealRoute AI Hub focuses on

Keys, intermediary routes, and call records

  • The local Client isolates provider keys from AI tools.
  • Secure envelopes protect requests and responses across intermediary distribution layers.
  • Call records expose Token, route, latency, format, and Proof without prompt or response text.
The boundary to understand

The final model provider processes request content

  • A model must read content to perform inference; SealRoute AI Hub does not claim otherwise.
  • For direct official-key access, SealRoute AI Hub adds key isolation, budgets, policy, and audit.
  • KMS, HSM, TEE, and private deployment are enterprise options verified by contracts and deployment evidence.

Data Handling

How one call is handled

  1. 01
    AI tool

    The user sends a request from WorkBuddy, Codex, Cherry Studio, or another compatible tool.

  2. 02
    Secure entry

    The cloud entry or local Client verifies identity; local mode encrypts on the device.

  3. 03
    Final model

    The selected provider processes the request under its data policy and returns a response.

  4. 04
    Sanitized record

    Token, status, latency, and Proof are recorded without prompt or response text in normal call details.

Verifiable Records

Every call can leave a reviewable record

RequestTime, model, and call status
Secure routeSanitized path and protection status
ResponseInput/output Token, latency, and format
ProofAccount-scoped audit-proof status

Report a security issue or request enterprise security material:

security@sealroute.aiView my call records

Public Timestamp

Publicly verifiable audit anchors

SealRoute AI Hub uses Merkle Tree and OpenTimestamps to create publicly verifiable audit proofs for AI calls. Audit summaries are anchored to Bitcoin through public timestamp calendars, while business content and user data stay off-chain.

LoadingProof state is separated into local integrity, public timestamp submission, and Bitcoin confirmation.
01 · Local integrityVerifyingRecord hash → Merkle Root
02 · Public timestampLoadingOpenTimestamps Calendar
03 · Bitcoin time proofLoadingPublic block-time anchor
Proof protocolMerkle Tree + OpenTimestamps
Latest batch-
Records in latest batch0

Recent public anchors

Showing recent records by default

Loading public anchors

Only aggregated hashes are anchored publicly. A timestamp proves that an audit root existed before a point in time; it is not a judicial certificate or third-party confirmation of the underlying call content.