Data handling
Understand the boundaries between your browser, gateway, and model provider.
Request path
Your application sends messages through the Unrefused gateway to the configured inference provider. Provider credentials are held server-side. The provider processes the content needed to generate a response.
Usage metadata
Usage records can include timestamps, model and key identifiers, token counts, request status, latency, and policy decision codes. These records support the usage dashboard.
Provider handling
Provider-side logging, retention, and data use must be confirmed for the launch configuration. Unrefused does not make an end-to-end zero-retention commitment in this preview.
Browser storage
Some workspace previews save state in your browser. Treat browser storage as local application data, and review the current privacy policy before sending sensitive information.
Privacy policy
The privacy page is marked as a draft while the service's final data-handling details are established.
Availability depends on your connected provider. Check service status and keep x-request-id with your diagnostics.