Privacy and access

Your organization controls access to its deployments. Usage records contain metadata, never prompt or completion content.

Private models

Every model you deploy is private, including models from public repositories. Only API keys belonging to your organization can call it.

• One organization per card. A GPU card serves one organization while it is held. Its memory is wiped and scanned before another organization uses it.
• Your own engines. Your requests run in engine processes that serve only your organization, and never batch with another organization’s.
• Your own copies. Stored weights, copies in host memory, adapters, and parked conversation caches are yours alone. Another organization’s copy of the same public files is never shared with yours.
• Explicit code execution. Deploying weights never runs repository code on a GPU host. Tokenizer code is converted in a sandbox with no network. Custom engine builds run only within their checked, isolated serving configuration.
• US only. GPU hosts and stored weights stay in the United States.

Private and gated Hugging Face weights are read through your connected account. Your Hugging Face token never reaches a GPU host, and revoking the connection stops future pulls without stopping what you have deployed.

For hardware no other organization touches, reserved capacity can be placed on dedicated hosts. Contact us.

Inference data

Synchronous prompts and completions are processed without being stored. Boardwalk does not put inference content in request history or operational logs, or use it to train general-purpose models. Engine logs are never exposed. On catalog models, the prefix cache is salted per organization, so no cache hit crosses organizations.

Batch uploads opt into private, encrypted storage for processing and result downloads, with automatic expiry and API deletion.

Receipts retain request identifiers, model revisions, token counts, rates, costs, timings, and status. Deployments retain model artifacts, configuration, and qualification records.

API keys

Keep keys in server-side secrets or environment variables. Create separate keys for each application, choose the minimum permissions, and revoke keys you no longer use. Keys are shown once; Boardwalk stores their hashes.

The privacy policy covers account information, service providers, retention, and deletion. For access or data questions, contact us.