🐕 Super Intelligence Dog
sign in

Security and trust

What SID does with your data and credentials, how an agent run is isolated, and where we actually stand on compliance. This page describes controls that exist today; it does not claim a certification we have not earned.

Data in transit and at rest

Traffic between your client and the gateway, and between the gateway and a model provider, uses TLS. Provider keys you connect are encrypted at rest with an authenticated cipher and a server-held key, and are never returned in plaintext. SID API keys are stored as a one-way hash; the plaintext key is shown once, when it is created.

Execution isolation

Agent runs execute inside an isolated microVM sandbox, not on the gateway host. The agent proposes a bounded plan, you approve what it may touch, and it never commits or pushes on its own. The independent review and the security scan run before any result is returned as a receipt.

Model routing and the data path

Open-weight models run on hosted third-party endpoints; we never call them private or local. Closed-lab models are bring-your-own-key and are never resold: your request goes to the provider you connected, under your key. The full data path, including how to select or pin a model, is documented in the API docs.

Retention

Request metadata and run receipts are stored for billing and routing quality. Run receipts are kept in our server database with nightly backups kept 14 days; nothing auto-expires today, and you can ask us to delete yours. The Privacy Policy is the authoritative statement.

Payments

BellerCreatives is the merchant of record and hosts checkout. SID never stores your card details.

Compliance posture

Status

Live operational status is published at /status. The model catalog and per-model prices are published at /models.