White-Label Addendum

Deeper branding rights, attribution controls, output customization, binary metadata, and minimum commercial commitments.

1. Purpose

This addendum governs deeper white-label rights for partners that require aisecurity.llc capabilities to appear under the partner’s product, platform, scanner, or service brand.

2. White-Label Rights

White-label rights may include:

custom product naming
custom report language
partner-branded output metadata
hidden customer-facing attribution
partner-specific packaging
custom documentation
custom commercial presentation
partner support handoff
custom binary name or metadata where approved

White-label rights must be explicitly stated and paid for.

3. No Transfer of Ownership

White-label rights do not transfer ownership of aisecurity.llc software, content, methods, schemas, binaries, rule packs, models, prompts, templates, or intellectual property.

4. Approved Use

The partner may use white-label rights only with the approved partner product, service, territory, customer segment, and deployment model stated in the order form.

5. Attribution

Attribution rules must be stated in the order form.

Possible attribution modes:

public powered-by attribution
attribution in legal notices
attribution in support and diagnostic output
internal-only attribution
no customer-facing attribution

6. Support Boundary

White-label partners usually provide first-line customer support.

aisecurity.llc provides partner-facing support according to the support addendum.

The partner must not imply that aisecurity.llc directly supports partner customers unless agreed.

7. Quality and Brand Protection

The partner must not use white-label rights in a way that harms aisecurity.llc, misleads customers, creates unsupported security claims, or weakens safe-use restrictions.

aisecurity.llc may require changes to inaccurate or unsafe white-label materials.

8. Output Integrity

White-label output may include partner branding, but should preserve:

finding identifiers
evidence references
scan scope
timestamps
version metadata
license metadata where appropriate
safety caveats
limitations
traceability fields

9. Anti-Theft and License Controls

White-label packaging must not remove:

license checks
signed license validation
usage metering
feature flags
revocation support
watermarking
output integrity metadata
partner-specific build metadata

10. Commercial Minimums

Full white-label rights should require:

annual minimum commitment
support addendum
security exhibit
audit rights
customer-org reporting
license control compliance
termination plan

11. Termination

Upon termination, the partner must stop presenting new aisecurity.llc-powered capabilities under the white-label brand unless wind-down rights are explicitly granted.

The partner must remove or disable white-label packaging in future distributions.

12. Suggested Order Form Fields

White-label terms should specify:

approved brand
customer-facing product name
attribution level
permitted outputs
permitted deployment models
support model
annual minimum
usage reporting
customer-org reporting
audit rights
wind-down period
prohibited claims