Enterprise & agencies
Onboard an entire roster in one move — managed keys, bulk registration, and licensing your team controls.
- Bulk-register clients & talent
- Delegated org signing key
- Domain-verified organization
What PRAMPTA proves, what it does not, and how to tell the difference. The most dangerous thing a trust layer can do is promise more than it can prove — so the limits are on this page too, at the same size as the guarantees.
| Attempt | What happens |
|---|---|
| Alter a licence's terms after it was signed | Signature reconstruction fails — refused |
| Replay one authorization for many generations | One-time nonce; a decision redeems once |
| Reuse a decision from one product on another | The decision binds product, project, channel and territory |
| Claim a celebrity by self-registration | Self-attested can never reach commercial; review required |
| Register a near-duplicate of an existing subject | Surfaced as a possible duplicate for a human to judge |
| Type someone's account id to impersonate them | A hand-entered id is an unverified claim, not an identity |
| Extract a provider secret from a web page | No secret or runtime token is ever sent to the browser |
| Claim "already paid" to mint a free licence | Only a payment PRAMPTA itself confirmed ever counts |
| Keep generating a subject under dispute | A dispute pauses free licences at once; only paid ones continue |
| Licence a likeness for video, then train on it | Training is a separate right — refused unless granted |
| Mark a child as low-risk to unlock commercial use | Only an operator can lower a risk flag; owners may only raise |
If anything in our product, docs or marketing ever sounds stronger than this page, this page is right and that is wrong — please tell us at legal@prampta.com.