Trust center

Trust

A lightweight overview of how Hydracept handles security, credentials, and data. It describes purposes and mechanisms, not a certification program. Hydracept is operated by Zencode Consulting Inc. The public service is reachable at api.hydracept.com and hydracept.com.

Security architecture

Hosted service boundaries

• Consumer products and agents reach Hydracept through the public API at api.hydracept.com and the public surfaces built on it (CLI, SDKs, MCP). This keeps credentials, provider configuration, job status, cost, and execution records in one place.
• When Hydracept owns execution, work should go through Hydracept capabilities and jobs from trusted tooling or your server, rather than through direct provider SDK calls.
• Provider keys and Hydracept API keys must not be embedded in shipped game clients or other public code. For player-facing apps, call Hydracept from your server.

Provider credential handling

• Provider credentials (BYOK) are stored encrypted at rest. Hydracept validates a credential when it is created and binds it to the project and environment that may use it at execution time.
• Credentials are used for the project and environment you authorize. The plaintext credential is not exposed in public discovery or receipts.
• Recommended practice is least privilege: bind a provider credential to the project or environment that needs it, and use separate machine credentials for CI and production where you can.

Project and workspace scoping

• Work is scoped to an organization and a repository project, with an environment (normally development for a new local project). Every capability job carries that context.
• Provider credential bindings decide which project and environment may resolve a given credential at execution time.

Transport security

• All public API traffic uses HTTPS (https://api.hydracept.com).

Storage model

• Execution produces artifacts and a durable execution record. Artifacts are stored and referenced by identity; provider sources, processed variants, and derivatives are kept as immutable artifacts.
• Provider sources, generated artifacts, and processing derivatives are tracked so a result can be reviewed and reproduced.

Audit records

• Every execution leaves a receipt: a durable record of the request, the execution, the provider response, and the resulting artifact. A receipt records who requested it, which provider, model, and native API were used, the exact request and parameters, whether anything was rewritten, retried, or fell back, and what the provider returned, what it cost, and which artifact resulted.
• Related receipts can be grouped into a run manifest and summarized by an AI lockfile for reproducibility checks. Wallet transactions are kept as an immutable transaction log.

BYOK

Bring your own provider credentials and pay your provider directly. Hydracept adds a 0% Hydracept fee for BYOK inference.

• Where credentials are stored: organization-scoped provider credential records, stored encrypted at rest.
• How they are scoped: a credential is created for an organization and attached with bindings to the specific project and environment that may use it.
• Which process can access them: credentials are resolved at execution time only for the project and environment they are bound to.
• Whether they appear in output: the plaintext credential is not exposed in public discovery or receipts, and it is not exposed to coding agents, MCP panels, project files, or normal command output. Do not place provider secrets in shipped clients or public code.
• Revocation: you can remove a provider credential, which revokes it and removes its bindings, and credential rotation is available.

Data and retention

• Inputs and rights: you retain your rights in prompts, files, reference assets, and other material you submit. You grant Hydracept a limited license to process those Inputs and the resulting Output as reasonably necessary to provide, secure, support, and operate the service and to comply with law.
• Payload retention: retained payload bytes and history retention are plan limits. Published plan history retention is 30 days on Free, 90 days on Builder, and 180 days on Team; Enterprise can discuss custom retention. See pricing for current plan details.
• Artifact retention: job-history and artifact retention can vary by plan, capability, and project configuration. Retain your own copies of important outputs.
• Deletion handling: you can update account information and remove provider credentials where those controls are available. To request access, correction, or deletion of personal information, contact support@hydracept.com. Some information may be retained where the law permits or requires it.
• Private content: generated artifacts and execution records belong to your workspace. Do not submit material to a capability unless the provider and data-handling terms for that capability are acceptable for that material.
• Diagnostics and logging: Hydracept processes API requests, prompts and files you submit, generated output, job metadata, usage and billing records, diagnostic logs, and configuration data needed to operate the service. The public website offers optional analytics that loads only if you accept it. See the privacy policy for the full description.

Providers and subprocessors

• Managed capabilities invoke external model and service providers to perform requested work. The provider used for an accepted managed job or quote is identified by that quote or job contract. Provider availability, models, output, and terms can change and are outside Zencode's control.
• BYOK connections let you use provider credentials you control; those providers process your material under your direct provider relationship. Supported BYOK providers in the current product include OpenAI, ElevenLabs, and Meshy. The exact provider set can change.
• Billing is processed by Stripe when you purchase a paid plan or add managed credit.
• Third-party infrastructure and inference providers may process Inputs and Output as subprocessors or independent service providers under their own applicable terms and privacy commitments. The current list varies by capability; the provider for a given accepted job is identified in that job's contract.
• Third-party license notices that ship with the repository are recorded in THIRD_PARTY_NOTICES.

Status

Hydracept does not currently publish a separate status page in this repository. The public API exposes a health endpoint at https://api.hydracept.com/healthz, which is also used by python -m hydracept doctor. When a dedicated status page is available, it will be linked here.

Compatibility

Changelog · compatibility and stability policy for the public consumer contract.

Certifications

Hydracept does not claim SOC 2 or ISO certification. Do not treat this page as evidence of an audit, certification, or compliance attestation that does not exist.

Security contact

Report security issues to support@hydracept.com. If you believe your account or keys have been compromised, notify us promptly.

← Hydracept home