‹ Newsroom

Support ·

Clarity support on the web. Prepared for launch.

The web interface for support cases, consent and responsibility is prepared. New cases remain disabled until legal and backend approval.

Legal and backend approval remain mandatory before publication
A support specialist listens carefully during a case review
01

One case, one visible route.

After approval, you should be able to choose the topic and support route deliberately. With consent, the system can then answer the current case autonomously; without consent, the case is routed to the team. A new case may be stored only when the support legal version, minor rule and backend contract clearly agree.

02

People remain responsible for the system.

Audecius support is presented as a shared team route, not as an unverified list of individual staff. The team is responsible for the way it works and should monitor and review operations. A particular answer may be described as human-reviewed only when that review status was actually stored.

  • AI assistance visibly labelled
  • Human hand-off available on request
  • Consent can be withdrawn
  • Previous cases are not currently used automatically as AI context
03

Support remains separate from the Help Centre.

The website is built for the support tool: open cases, read replies, change route and reach legal information. Until approval, a new case shows its locked status and cannot be submitted. Knowledge articles or guided sessions are not presented as support cases.

Technical source status · 11 August 2026

The specification behind this update.

These registers show which product statements are substantiated, presented as preview or not yet approved.

Audecius Account

What the web account genuinely manages today.

Support, sessions and account data share the same identity. Inactive management routes remain marked as preview or locked.

Web sign-inOne-time email code for existing Audecius AccountsAvailable
Web sessionHTTP-only cookie; browser scripts cannot read access or refresh tokensAvailable
Plan and billing sourceServer-verified in the web accountAvailable
Clarity SpacePersonal, server-verified meter with categoriesAvailable
Name and profile languageEditable in the web accountAvailable
Devices and MFANo active web management yetPreview
Export and deletionCurrently a direct email-request route, not automatic self-service executionNot yet approved

Human boundary

Helping autonomously does not mean taking responsibility autonomously.

The consequence model limits what kind of answer or action a support route may prepare.

C0 · ObserveReads or displays. Changes nothing.No execution route required.
C1 · SuggestClassifies and recommends a next step.The person decides and acts.
C2 · After your yesPrepares a real change.Preview and explicit approval before execution.
C3 · Within your boundaryMay act only within a previously defined, reversible boundary.Daily budget, live permission, receipt and Undo; never for another person.
C4 · Human onlyPayment, medicine, law, identity or particularly sensitive security.Clarity may prepare, but may not execute autonomously.

Context

What this update does not claim.

  • The technical provider-call ceiling is documented as a safety maximum. Actual output tokens, tool and reasoning budgets, usage and traffic are not published as sales figures.
  • Community, Club, Marketplace and Creator are not part of the first public release scope.
  • Outlook, public production access and native SDKs remain Private Preview; the Sandbox API, sandbox keys and Webhook Lab are available to approved developers.
  • A shared Family storage pool and end-to-end seat assignment will be described as live only after complete server and app verification.
  • New web-support cases and the Legal Centre remain locked or non-indexable until the legal version and minors approval are unambiguous.

Official. Dated. Verifiable.

Every Clarity update remains available in the Newsroom with its product status and verified timeframe.

Clarity support on the web: cases and responsibility — Audecius