Skip to Content
Security & PrivacyData handling overview

Data handling

This is a technical overview. Legal terms remain in the Privacy Policy .

Tenant and access

API keys, connections, routing policy, budgets and request evidence belong to an organization. The main navigation shows the active tenant. Switching changes the scope of subsequent operations.

Members can inspect their own usage. Owners/admins inspect tenant usage and configuration history. Prompt-content access has additional role restrictions; request metadata access does not automatically grant access to every transcript.

Retained data

  • Identity, membership, authentication and configuration required to operate the tenant.
  • Policy decisions, usage attempts, attribution, tokens, cost, timing and durable correlations.
  • API transcript/Response content, sanitized request/response snapshots (including policy-denied requests), and generation/tool snapshots under configured expiry. Request evidence is retained independently of the Responses API’s store flag.
  • Safe file metadata and provenance; no retained file bodies, base64 originals, recoverable original URLs or object storage.
  • Transcription uploads produce observed size/digest metadata; audio bytes are omitted from retained evidence, while text/transcripts follow content retention.

Content retention defaults to 30 days: request/response evidence expires from the routing decision’s creation, sessions from the last message, and stored Responses from creation. Generation/tool snapshots have their own creation/request-based expiry. Expiring content does not erase the decision/usage ledgers. Tenant privacy erasure and organization lifecycle follow separate operator workflows.

See Activity and evidence export for content access and download permissions.

Provider egress

The configured routing policy and key restrictions are evaluated before inference. Your application supplies sensitivity declarations; Steinkauz does not certify their accuracy.

Allowed prompts and live multimodal inputs go to your configured provider. You are responsible for its terms, destination, logging and retention. A provider’s no-training or zero-retention setting is not a Steinkauz certification.

Steinkauz Cloud is EU-region shared hosting. Private Deployment places the software in the agreed customer environment; the inference destination can still differ from the application host.

Steinkauz does not train its own models on customer content or resell inference.

Encryption at restUsage Budgets