An API usage record and a conversation transcript answer different questions. When building uncensored chat with an uncensored LLM, keeping that distinction clear helps you understand what your application remembers and what an operational record can establish.
UncensoredLabs offers uncensored and abliterated AI models through an OpenAI-compatible API, with streaming chat completions, prepaid token billing, API-key spending limits, model allowlists and usage tracking. These are integration and accounting features. A usage entry should not be mistaken for a saved copy of the conversation.
Start with the question you are trying to answer
For an operational review, you might ask whether a request consumed usage, which application key was involved, or when the activity occurred. Inspect the fields actually available in your own account; a metadata record is useful evidence for accounting, but it does not show whether a model answer was correct or suitable for your users. Evaluate output quality in a separate, authorized test workflow.
For a conversation review, the question is different: can the user reopen the words they exchanged? UncensoredLabs states that its application servers process prompt and response content transiently for routing and streaming without storing it. Optional chat history stays in the browser. Its retention policy also distinguishes retained content-free request metadata, account security records and financial records. “Application content is not stored” does not mean that every operational record disappears.
Browser history needs its own cleanup decision
If you use optional browser chat history, that copy remains until you delete it or clear the site data. Disabling saving for an individual chat removes its stored copy; changing the default does not erase chats that already exist. Account deletion removes saved chats in the current browser, while copies in other browsers must be removed there. Treat each device or browser as a separate place to check.
For your own API client, decide explicitly whether your application saves conversations. Changing an API base URL does not automatically change your application’s database, analytics or logging configuration. Keep credentials out of examples and restrict access to any test records you choose to keep.
Understand the policy boundary
The published retention policy describes scheduled cleanup of content-free usage metadata older than 30 days by default; aggregate data and financial records can have different requirements. It also says that inference and network providers apply their own policies. This is an application retention statement, not proof of zero retention by every provider in the request path. Read the current policy rather than extending a short product slogan into a broader guarantee.
Try a small, deliberate evaluation
Eligible new accounts can receive a one-time $0.10 trial usage credit; verification may be required. Ordinary API usage is prepaid and paid, with no recurring free tier. Use the trial, if eligible, to check the integration and the records you actually need, without treating it as a performance benchmark or an unlimited allowance.
Explore the product: https://uncensoredlabs.dev/
Read the integration docs: https://uncensoredlabs.dev/docs
Check current retention details: https://uncensoredlabs.dev/retention
Privacy policy: https://uncensoredlabs.dev/privacy
Pricing: https://uncensoredlabs.dev/#pricing
This is a first-party UncensoredLabs guide prepared with AI assistance. The illustration is generated brand artwork; the landing-page image shows the product website, not a request-log screenshot.
