Skip to main content
Audact
See the offer

White-label scope

What your end-client sees, exactly.

White-label here means the caller experiences your end-client's brand from the first second to the last. The agent identifies itself as an AI assistant acting for your end-client, and the AI disclosure names your end-client: the brand is theirs, the fact that it is an AI is not brandable. The receipt records the verdict, the policy version, the configuration seal, the input and output hashes and the link to the record before it. It names no issuer and no principal. Your agency operates everything from one console that your end-clients never log in to. Below, per element, what runs today and what is in development; no date is set.

What runs, and when

The caller hears your end-client's brand: the agent identifies itself as an AI assistant acting for your end-client, in their wording and voice.
In controlled testing
The AI disclosure names your end-client, in the caller's language, at the position the country policy requires.
In controlled testing
The receipt records the verdict, the policy version, the configuration seal, the input and output hashes and the link to the record before it. It names no issuer and no principal.
Working today
Call recording and transcript download in the interface, so your end-client keeps the call itself and not only the record of the decision.
Planned
The production export of a set of receipts, measured on browser calls rather than over a telephone line.
Working today
The monthly evidence package: what you hand to your end-client's data protection officer. It is not in the offer; it is Under validation: an evidence artefact we have not tested ourselves does not go into the offer.
Under validation
One isolated sub-account per end-client, so each client's agents, policies and receipts stay apart.
In controlled testing
Re-billing through Stripe Connect: you invoice at your own rate and receive one invoice from us.
Planned · not in the current production offer · no date is set
One console for your whole portfolio: you log in, your end-clients do not. The address and the credentials are sent with the kick-off e-mail; there is no public console address yet.
Working today
The console on a domain you control, with your logo, colour theme and system-email templates.
Planned · not in the current production offer · no date is set

The wall

What stays on your side of it.

  • The Audact name in the call. The caller hears your end-client — not your agency, and not us.
  • Your margin and the rate you pay Audact. Billing stays on your side; your end-client sees your invoice, at your price.
  • Other agencies' and other end-clients' data. Sub-accounts are isolated from each other.
  • The agency console. End-clients do not have a login to it; what they need is handed to them rather than looked up by them.

Data processing

White-label changes what the caller hears, not who processes the data.

In the processing chain your end-client is the controller of their callers' data, your agency is their processor and in some setups a controller in its own right, and Audact acts as your processor and as sub-processor towards your end-clients, under a data processing agreement. Which of the two roles your agency holds is fixed per deployment in that agreement, not by this page. That chain is written down precisely so your end-client's data protection officer can see who touches the data and where it sits.

Each agency remains responsible for its own agreement with its end-clients, naming Audact as sub-processor where that is required. Primary application hosting is Frankfurt; the full subprocessor list, with location and safeguards per entry, is in the Trust Center.

General information, not legal advice. Your own agreement governs the specific terms.

Roles

Who carries which role.

White-label puts one brand in front of the caller and leaves several parties behind it. Three separate bodies of law each cut the same setup a different way, so a role under one of them says nothing about a role under another: provider and deployer come from the AI Act, manufacturer from the product liability directive, controller and processor from the GDPR.

  • Role
    Represented organisation
    Who carries it in a white-label setup
    Your end-client. Their brand is what the caller hears, and the AI disclosure names them.
  • Role
    Principal
    Who carries it in a white-label setup
    The organisation whose mandate the agent acts under. Your end-client, unless your agreement puts it with your agency.
  • Role
    Provider (AI Act)
    Who carries it in a white-label setup
    On most readings your agency, because it sells the system under its own name. Which side of the line a setup falls on depends on how it is configured, modified and marketed, and we map that role with you before go-live.
  • Role
    Deployer (AI Act)
    Who carries it in a white-label setup
    The party that puts the system to use under its own authority. Which of you that is follows from the same mapping, and it is settled before the first call rather than after it.
  • Role
    Manufacturer (product liability)
    Who carries it in a white-label setup
    A party that puts its own name on a product is treated as its manufacturer, software included, under Directive (EU) 2024/2853 from 9 December 2026. It is a directive, so transposition runs per member state.
  • Role
    Tenant and payer
    Who carries it in a white-label setup
    Your agency. You hold the account, you set your own rate to your end-client, and you receive one invoice from us.
  • Role
    Controller (GDPR)
    Who carries it in a white-label setup
    Your end-client, for their callers' data.
  • Role
    Processor (GDPR)
    Who carries it in a white-label setup
    Your agency towards your end-client, and in some setups a controller in its own right. Fixed per deployment in the data processing agreement, not here.
  • Role
    Sub-processor (GDPR)
    Who carries it in a white-label setup
    AUDACT AI LIMITED, Ireland, CRO 822514, the operating company. Which Audact company is party to your contract is set in the order form you sign; the DPA, section 1, states the position.
  • Role
    Further sub-processors
    Who carries it in a white-label setup
    Our own vendors, each listed with location and safeguards in the Trust Center. Primary application hosting is Frankfurt.
  • Role
    Technical issuer of the receipt
    Who carries it in a white-label setup
    Deliberately not identified on the receipt. It evidences that the record is intact, never who wrote it, and the sample file says so on its face.
  • Role
    Evidence custodian
    Who carries it in a white-label setup
    Audact, on the primary application hosting. Handing a copy to your end-client runs through the export: The export returns the receipts. That is not the same as an outsider being able to check the export: the export envelope refers to a key of ours, and that key is not published.

Portability

Your brand and your record stay yours.

Your agents, your call records and your configuration are exportable, and off-boarding keeps access for the window in the refund policy (30 days; see /legal/refund-policy). Who holds which role, and which rights follow from it, is fixed per deployment in the agreement you sign. Where the production export stands today is in the list above, under "What runs, and when".

Under the EU Data Act, switching and data-portability rights have applied since 12 September 2025; from 12 January 2027 no switching charges may be levied (Art. 29).

What you can hand over

What your end-client can check today.

Per sub-account, a receipt is visible in the product for that client's governed interactions.

On any receipt, three fields can be recomputed by anyone today: the input hash, the output hash and the link to the receipt before it. No key, no account, no access to our systems. A fourth, inclusion in the Merkle root, is checked against the published root with the inclusion proof from the call's Article 50 report. That is what makes it a document your end-client can take to their own advisers rather than a promise they have to take from you.

Questions

Does the caller ever hear the word Audact?
No. The agent identifies itself as an AI assistant acting for your end-client, and the AI disclosure names your end-client. Your agency name is not spoken either. So the caller hears the brand they expect, and that they are speaking with an AI: under Article 50 that disclosure is a duty on the provider under Article 50(1), and for a white-label deployment that role is agreed per deployment, which makes it the one element white-label does not cover.
Can my end-client log in and look around?
The console is the agency's. What the end-client gets is handed to them rather than logged in for. That keeps the account relationship with you and keeps the other sub-accounts out of view.
When can I put the dashboard on my own domain?
Custom CNAME, agency logo, colour theme and the system-email templates are planned; they are not in the current production offer, and no date is set. The console runs on a domain of ours; the link is sent with the kick-off e-mail.

Apply for the agency tier

Caller-side white-label runs in controlled testing and a receipt is written for each governed segment. We configure the first agent with you.

Apply for a founding seat

Related