Security and likeness safety
Creator Likeness and Platform Agreement version 2026-09 — source dated 14 September 2026
Updated 14 September 2026. This page explains our safeguards and the limits of what we can control.
Access to information
We check account permissions before allowing access to private records. Campaign team members receive the access assigned to them; access to campaign records does not let them sign for a person or change payout details. Identity documents are handled by the verification provider, currently Stripe. Clause 9 of the licensing agreement requires Australian 100-point identification at onboarding; a completed Stripe check alone should not be read as a statement that every document combination meets that standard. We retain necessary verification references, results, minimum attributes and audit evidence. AI Character face, voice and movement models are separate likeness assets, not identity-verification records.
Files and backups
Uploaded files pass through security checks before release. A failed or inconclusive check keeps a file restricted. We use HTTPS for our public services and encrypt backup exports. We restrict access to backup and operational records. These measures reduce risk, but no online service can guarantee that every attack or loss will be prevented.
Likeness permissions
The Creator Likeness and Platform Agreement version 2026-09 permits persistent AI Characters, training on authorised Creator Materials and opted-in Linked Account Content, project licensing and separately opted-in Licence Programmes. These permissions do not apply retrospectively to an earlier signed agreement. Signing the platform agreement alone does not opt a person in to a programme. Campaign records connect licences with final-content reviews and reported placements. New scripts, claims or material changes need the approvals required by the agreement. An expired term, missing approval or safety hold is a reason to stop and review use.
AI performances and product claims
An authorised AI performance does not by itself establish that the person has used a product or personally endorses every claim about it. The company is responsible for substantiating its claims and obtaining approval for the statements and context attributed to the person. Translation, voice generation and AI disclosure belong in the project review.
Suppliers and copies
Approved suppliers may handle material only within the permissions and equivalent restrictions required by clauses 3 and 7. Raw identity documents are never licensed to companies and raw Creator Materials may not be resold as standalone assets. Their access and permitted uses should be recorded in the signed project scope. We can restrict files served by HyperKnown; disabling a link does not delete a copy already downloaded by another party. A team’s report that an ad was removed is recorded separately from independent verification.
Security concerns
We assess reported incidents, record containment and recovery work, and determine whether affected people or authorities must be notified under the applicable law. We preserve relevant evidence and limit access to the investigation. We keep operational configurations and details that could compromise an investigation private.
Your choices
You can review your project records, manage authorised access and submit a privacy request. Leaving the marketplace, disconnecting a linked account, opting out of a programme and ending an existing licence are separate processes. Already licensed, commissioned or in-production commitments continue under clauses 6 and 10; lawful retention is restricted to the relevant purposes. We assess safety concerns even if the person reporting them cannot access an account.
Report a safety or security concern. For personal-information questions, read our Privacy Notice or contact privacy@hyperknown.ai.