A generation platform should be able to ask whether this buyer may use this person’s face or voice for this exact request, then enforce the answer before a supported operation runs.
Model access, an uploaded asset and a buyer assertion do not establish permission from the real person. SocialGravity keeps the authority chain separate: verified identity, reviewed consent, the signed commercial scope, current status and the proposed use are evaluated together before a supported operation proceeds.
A positive CLEAR or PERMIT result means the described request fits the authority and supported controls evaluated at that time. It is not a blanket compliance certificate, permission for a different use or proof about an output that was never registered. An unresolved, expired, revoked or out-of-scope request does not proceed through the supported route.
The decision record can be joined to the buyer, permission version, protected operation and resulting release. A registered output can then carry checkable evidence linking the person, covered asset, signed scope, operation and current status without exposing private identity documents or the private agreement itself.
Permission is checked from current authority rather than copied once into a permanent allow-list. Expiry or revocation stops future supported use. Historical records remain records of what happened, while the agreement governs treatment of outputs already lawfully released.
Integration begins with one named workflow and the evidence it can actually enforce. SocialGravity does not advertise an unrestricted self-serve API here, claim that every generation provider is integrated or ask a platform to self-classify legal compliance. The first step is a supported workflow review covering the request fields, decision boundary, fail-closed behavior, evidence handoff and revocation path.
Discuss a platform integrationEvaluate the permission chain
This page describes SocialGravity’s supported product model and integration boundary. It is not legal advice, a universal compliance standard or a claim that an integration is already live.
It is the operational layer that connects a real person’s reviewed authority and signed scope to a decision about a proposed face or voice use, then preserves evidence and current status.
Not automatically. Platform terms govern the software relationship. Permission from an identifiable person for a specific use needs its own authority record.
It shows that the described request fit the authority and supported controls evaluated at that time. It does not authorize a different use or decide every legal question.
The supported operation does not proceed until the missing authority, scope or evidence is resolved. Uncertainty is not rounded into permission.
Not automatically. Revocation stops future supported use. The agreement separately governs treatment of outputs already produced or released.