Two signatures.
One truth.

BentBox Is Not a Party to the Shoot

There is a habit, on platforms like ours, of slipping into one of two postures. The first is creator-first: the photographer uploads the work, the platform trusts the upload, and the model’s position is treated as a downstream concern handled by a paper release the platform never reads. The second is model-first: every depicted person is treated as a potential complainant, every photographer is treated as a potential infringer, and the platform sides reflexively with whichever party speaks loudest.

Neither posture survives contact with reality, and neither is the one BentBox occupies. We are not the photographer’s lawyer. We are not the model’s advocate. We are the marketplace where their agreement is published and sold, and our obligation is to the agreement itself — that it exists, that it is current, that it is verifiable by both sides, and that what is listed on the platform falls inside what was actually consented to.

That is the only way a marketplace of this kind can stand up. A platform that takes the photographer’s word for it ends up defending releases it has never seen. A platform that takes the model’s word for it ends up unpublishing work on accusations it cannot evaluate. The only durable position is to require a record that both parties have signed, that both parties can see, and that neither party can quietly alter.

What We Owe the Photographer, and What We Owe the Model

Both sides arrive on BentBox with a legitimate need, and those needs are not symmetrical. Treating them as identical would be its own kind of unfairness. The platform’s job is to satisfy each, on its own terms, without making one contingent on the goodwill of the other.

These are not competing goods. A photographer with a verified, scoped release is in a stronger position, not a weaker one. A model with visibility into her own consent record is less likely, not more likely, to escalate to a regulator. The two needs are met by the same mechanism, which is the point.

How ProntoTag Actually Works on BentBox

ProntoTag is a model-release service developed on the ProntoID identity infrastructure. It is integrated into the BentBox creator dashboard. A photographer preparing a Box for publication can issue a ProntoTag request for each depicted person directly from the listing interface; the request lands in the model’s ProntoID account, where she can review the proposed scope, confirm or refuse, and sign.

There are four things worth understanding about how this is wired into the platform:

1. Identity is verified once, against a source

Both the photographer and the model verify their identity through ProntoID’s standard flow. That verification is done against the issuing authority of the document — not by uploading a photocopy of a passport to the platform. BentBox never sees the raw ID. We see only that the identity has been verified and which verified identity is attached to the release.

2. Consent is scoped, not blanket

A ProntoTag release is bound to specific content (which Box, which videos), specific media types (stills, video, behind-the-scenes), and specific usages (display on BentBox, downloadable purchase, inclusion in community boxes, AI processing). It is not a single signature waving the rest of someone’s life away.

3. Both parties hold the same record

The signed release lives in both the photographer’s and the model’s ProntoID accounts. Neither party can quietly alter the other’s copy. If the platform is ever asked to demonstrate the consent chain — by a regulator, a publisher, a downstream buyer — the same record is produced from either side, independently.

4. The release is revocable, within structure

A model can later withdraw consent. She cannot rewrite history — past sales are not undone, royalties already paid stand, the photographer’s underlying authorship of the file is unaffected — but the listing is moved into a review state. The mechanism is structured precisely so revocation is meaningful without being weaponisable.

Three Things Photographers Say, and What the Platform Has to Reply

When BentBox introduces a ProntoTag requirement, a particular set of objections surfaces from the photographer side. They are predictable, they are sincere, and they are wrong. The platform owes its creators a clear, calm response to each.

When a Loose Release Turns Into a Dispute, the Photographer Pays the Cost

It is worth being concrete about what happens when a release is loose, undated against the actual shoot, or silent on media type. These are not theoretical risks. They are the recurring shape of every model-release dispute that reaches the platform, and the cost almost always exceeds what the photographer earned from the sale that triggered the complaint.

A vague release is not a strong release. It is an invitation to argue — later, expensively, and on the model’s timeline rather than the photographer’s.

Two patterns recur. The first is scope creep: a release that says “photographs from the shoot” gets stretched to cover behind-the-scenes video, or one that names a specific magazine gets reused to license the same images to a third-party marketplace. The model, looking at the listing months later, says — reasonably — that this is not what she signed. The second is date drift: a release dated for one session is later attached to content from a different session, sometimes with the same model, sometimes shot months apart. The release exists. The signature is real. But it does not, in fact, cover the file being sold.

The pattern repeats across categories. A release that does not specify revenue-sharing terms leaves the photographer exposed when the model later argues she should have shared the proceeds. A release that names “the website” without specifying which one leaves room to argue that distribution to a marketplace was never authorised. Each ambiguity is, individually, small. Aggregated across a working career, they are the surface area on which every model dispute lands.

Where revenue share is part of the deal

For shoots where the model is a revenue-share recipient — an arrangement increasingly common on creator marketplaces — the strength of the release matters more, not less. ProntoTag lets the photographer specify the revenue-share percentage directly on the release the model signs. The model is signing not just to the use of her likeness but to the commercial terms attached to it. When the first payout cycle arrives, there is nothing to argue about. When the listing keeps selling for two years, the split that was signed at the start is the split that continues. The release is not just permission — it is the contract that makes the ongoing economics defensible.

A Dashboard, Not a Phone Call

For the model, the practical experience of managing her likeness on a platform like ours has, until recently, been remarkably bad. If she wanted to know what was being sold under her name, she had to ask. If she wanted something amended or removed, she had to find the photographer — sometimes years after the shoot, sometimes after a career change on either side — and hope he answered. If the photographer did not answer, she had to escalate to the platform and hope the platform read her email charitably. Every step depended on someone else’s goodwill.

ProntoTag ends that dependency, on purpose. Every Box and every video tagged to a model appears in her ProntoID dashboard, scoped to what she actually signed for, with the operational controls she needs to manage her own publications. She does not have to call the photographer. She does not have to write to BentBox support. She does not have to hope.

Illustrative view. Actual interface elements may differ.

From that dashboard the model can, in a small number of clicks, see precisely which scope she signed for on each listing, flag a publication for review if her circumstances have changed, and trigger the structured revocation path described earlier in this article. She can also see, at a glance, how much of what is on the platform under her likeness is from when — useful in its own right when a model has shot with multiple photographers over years.

The model is no longer dependent on the goodwill of a photographer she may not have spoken to in years, or on the platform reading her email charitably. She manages her own publications, directly, from her ProntoID account.

This is the parity that makes the two-sided position the platform takes actually work in practice. The photographer holds the same record from his side, with the same scope, the same signatures, the same audit trail. Both parties are operating from a shared source of truth — which is the only configuration in which BentBox can stand neutrally between them, because there is nothing to take sides about.

Stills Are Not Video. Video Is Not Stills.

One assumption causes more disputes on platforms like ours than any other, and it is worth naming directly. A model release signed for a photographic shoot covers stills. It does not, by default, cover video. A release signed for a video shoot covers moving image. It does not, by default, cover the publication of stills extracted from the same session.

These are different rights, with different commercial implications, and in many jurisdictions they sit under different legal regimes. A model who agreed to be photographed for an editorial portrait series did not, by signing that release, agree to have a behind-the-scenes clip uploaded to a video marketplace. A model who agreed to a short video sequence did not, by signing that release, agree to have frame-grabs sold as still imagery.

If a Box contains video, the ProntoTag release attached to it must explicitly cover video. If the same shoot also yields stills the photographer wants to publish, that is a second scope — either added to the original release at signing, or issued as a separate ProntoTag request. The model sees both. The platform sees both. There is no quiet expansion of consent from one medium into another.

What Happens When the Model’s Life Changes

A model who signed a release at twenty-two is not necessarily the same person at twenty-nine. She may have entered a public-facing profession. She may have left the industry entirely. She may be navigating a personal circumstance that makes the continued circulation of certain images materially different from what she anticipated when she signed.

A platform that pretends none of this is its problem is a platform that is one complaint away from a regulator inviting itself in. A platform that lets any model unpublish anything at any time is a platform that no photographer would publish on. Neither extreme is workable. The middle position — structured, on-record revocation, scoped to what the release actually permits to be revoked — is the only one that survives both pressures.

What changes	Paper release	ProntoTag on BentBox
Model wants to see what is being sold under her likeness	No mechanism; she has to ask	Live dashboard in her ProntoID account
Model’s circumstances change materially	She calls the photographer, or doesn’t	Structured revocation flagged to the platform
Publisher or aggregator asks for proof of consent	Scanned PDF, possibly unsigned, possibly stale	Cryptographic record produced from either side
Dispute reaches the platform	BentBox has no evidence of its own	Audit trail attached to the listing
Past sales already completed	Contested case-by-case	Preserved; revocation is forward-looking