Usage records make an AI talent license more understandable after a client request is approved. Contributors should be able to see the relevant client, use category, date, terms version, and payment information without exposing unrelated personal data.
Record a meaningful event
A usage record should identify the licensed asset, client, project or request, category, territory, date, and applicable license version. If a job reaches generation, distinguish the actual event from a request, preview, failed attempt, or provider result.
Use consistent event names so a contributor does not have to decode internal engineering language. Provide enough detail to recognize a use while limiting unnecessary exposure of client confidential information or sensitive prompts.
Separate use from earnings
A generation event, an approved license, an invoice, an accrued amount, and a completed payout are different states. Display them separately so a user knows whether a payment is estimated, owed, processed, or returned.
Show the rate, deductions, platform fee, and timing that apply to a specific use. Do not convert a usage chart into an earnings promise. Demand varies, and earnings are not guaranteed.
Give contributors a way to question a record
A contributor should be able to flag an unfamiliar use, report suspected misuse, and receive a confirmation that the issue is being reviewed. The workflow should link the report to the correct event and avoid exposing one contributor's data to another.
Keep a dated history of reviewer actions and outcomes. A reported event should not be silently removed from the record simply because it is under investigation; its status can change while the audit trail remains intact.
Protect the audit data
Usage records can contain sensitive details about people, clients, and creative projects. Limit access, define retention, and document which fields are necessary for accounting and dispute resolution. Avoid copying identity documents or biometric payloads into a general usage table.
Approved.video's product direction includes traceable asset and usage records for integrated workflows. Accurate, persistent usage depends on the authorized generation provider returning the relevant event data and on a live talent license.
CLARIFICATIONS
Questions & answers
Should contributors see prompts from every AI video generation?
A program should define the useful level of detail while protecting client confidentiality and personal data. Counsel and privacy reviewers should approve the policy.