Privacy and access

Your organization controls access to its deployments. Boardwalk keeps usage records without storing 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. Sharing serving infrastructure does not grant another organization access to your model.

Private and gated Hugging Face weights are read through your connected account. Boardwalk stores the serving artifacts it needs; your Hugging Face token is not passed to inference workers.

Inference data

Prompts and completions are processed to serve the request. Boardwalk does not persist their content in request history or operational logs, or use it to train general-purpose models.

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.