every model spec’d & versioned · Concordance-tested changelog →

Legal

White-Label Addendum

Effective date: August 29, 2026 · Version 2026-08-29 · Accepted via POST /api/v1/legal/accept before the first tenant-configuration write

1. What this addendum covers

This White-Label Addendum (the “Addendum”) forms part of the Terms of Service and governs the White-Label Services: tenant configuration (your brand name, theme, disclosure additions, domain allowlist), tenant-bound embeds and embed tokens, and — on plans that include it — removal of Worthune attribution. It applies from your first tenant-configuration write; the API asks for your acceptance before that write is possible.

2. Your brand, our engine — honestly presented

White-labeling changes who the experience looks like it comes from; it must not change what the numbers are or what is disclosed about them. Two things are enforced by the platform itself and are also your contractual commitments:

Disclosures are append-only. Your firm’s paragraphs render after the engine’s core disclosure and each run’s own stated limitations. There is no supported or permitted way to remove, truncate, or override the core disclosure, and you agree not to attempt to.

Accessibility is gated at write time. Theme overrides must pass the WCAG AA contrast checks or the write is rejected. You agree not to circumvent the gate by re-styling rendered output into inaccessibility.

3. Your responsibilities to your clients

What your clients see under your brand is your communication, made with our tooling. You are responsible for: (a) your regulatory obligations for client communications — including, where they apply to you, FINRA Rule 2210/2214 review and recordkeeping of communications your firm distributes; (b) the accuracy of the disclosure additions, assumptions, and household data you supply; and (c) presenting the experience truthfully — you may brand the experience, and you may not claim to your clients that the computations are your own proprietary engine when asked directly who computes them.

Worthune remains responsible for what the engine computes and for the integrity of the core disclosure and evidence records — “every number can be traced, re-run, and verified against a published spec” holds under your brand exactly as under ours.

4. Domains and tokens

Tenant embeds render only inside origins on your domain allowlist, behind tokens signed with your tenant secret. You control the allowlist and are responsible for keeping it to origins you operate or authorize; treat embed tokens and the tenant secret as credentials. If a token or secret is exposed, tell us and we will rotate with you.

5. Attribution

Attribution removal is available on the plans that include it and is enforced at configuration time. On plans without it, Worthune attribution remains part of the rendered experience and this Addendum is not a license to remove it by other means.

6. Trademark, term, and effect of ending

You license us nothing beyond what rendering requires: your brand name and theme are displayed inside your own tenant’s experience and nowhere else without your consent. We license you no Worthune trademarks; unbranded output is unbranded, not re-brandable as endorsement.

This Addendum runs with your subscription. When your subscription ends or white-label features leave your plan, tenant embeds fail closed — they stop rendering data rather than rendering it unbranded or misbranded — and stored tenant configuration is handled as Customer Data under the DPA.

7. Order of precedence and changes

If this Addendum conflicts with the Terms, this Addendum controls for the White-Label Services. Material changes bump the version shown below; the API will ask for re-acceptance before your next tenant-configuration write.

Questions about this Addendum: support@worthune.com.