Share Boudoir Proofs Privately

To share boudoir proofs in Framekeep, create a studio gallery for the session, add the unfinished images as watermarked proofs, keep downloads off, and test the client view. Send either the studio gallery link with a PIN or an invite link that can expire. Tell the client to favorite the images they want you to retouch.

When the choices are in, review the favorite counts in the studio asset list. Retouch the selected originals in your normal editing software. Then upload the delivery files and deliberately mark the intended assets as final in Framekeep. The download toggle is configured at gallery level and applies only to published Finals, so proofs can remain viewable without becoming downloadable.

Framekeep studio galleries support an optional PIN and expiring invite links. A PIN is a shared secret for the gallery. An invite is a separate access URL whose expiry can be set or whose access can be revoked. Choose the control that matches the agreement you made with the client, and test it in a signed-out browser before sending.

Use a discreet gallery title because metadata can appear after an authorized viewer opens the gallery. Avoid names or session details that would be uncomfortable on a shared screen. Client gallery routes use noindex, nofollow, and noimageindex response controls, but search directives are not an access-control substitute.

• Use a PIN if the client wants a separate credential.
• Use an expiring invite when the access URL should stop working on a schedule.
• Do not put a client name or intimate description in the gallery title.
• Open the exact link on mobile and desktop before delivery.

Framekeep lets the studio keep proof assets in the Gallery state, apply watermarked preview delivery while leaving the original unchanged, and disable the client download action. Those controls make the proof status visible, but the delivery note still needs to say what the client is viewing.

Give one action: favorite the images you want retouched by a stated date. Do not call the images finished, and do not tell the client that favorite selections will appear as finals automatically. The favorite is a recorded choice for the photographer to review; the photographer remains responsible for retouching and final publishing.

• State that the files are proofs, not delivered finals.
• State that downloads are unavailable during selection.
• Ask for favorites by a specific date.
• Explain that the studio will publish retouched finals later.

The client-facing gallery records favorites, and the admin asset list shows favorite counts. Use those counts as the selection list, but compare them with the contract and any message from the client before editing. Framekeep does not approve a selection, enforce an image allowance, or perform retouching.

After retouching, mark only the correct assets as final. The client view separates Gallery and Finals, and final assets are labeled accordingly. Download availability is a gallery-level studio setting, with Final status providing the per-asset eligibility boundary. Unfinished proofs can remain visible without receiving a download action.

• Confirm favorite counts against the promised selection.
• Retouch outside Framekeep.
• Use the explicit final control; favorites are not promoted automatically.
• Test every visible asset after changing the gallery-level final-download setting.

A PIN, invite link, watermark, and disabled download button reduce accidental access and casual reuse. They cannot stop an authorized viewer from taking screenshots, screen recordings, or photographs of the display. Anyone who receives a reusable PIN or valid invite may be able to open the gallery, so discuss link sharing with the client instead of implying that software can enforce consent.

A Framekeep studio gallery does not automatically expire. Expiring or revoking an invite stops that invite path; it does not delete the gallery or create a retention schedule. The studio must decide when to revoke access, delete the gallery, or retain files under its own contract and privacy policy.

• Do not promise screenshot prevention.
• Do not describe noindex as access control.
• Revoke an invite when its access window should end.
• Handle gallery deletion and retention as separate studio decisions.