Private Client Gallery for Boudoir Photographers

Use demo images for this evaluation: two unfinished proofs and a separately prepared finished file. Use filenames you can distinguish, add your studio branding, and open the client view on a phone as well as a desktop. These are checks for you to perform in your own studio gallery, rather than reported results from a client session.

Choose the access method and selection allowance you intend to offer. Keep Downloads off initially. A read-only public example can help you inspect presentation, but the private gallery test is where you verify access, saved choices, and delivery permissions.

• Use demo files with no client identity or private session details.
• Write down the expected access, selection, and download result before testing.
• Inspect your logo, gallery title, and White or Dark theme on a phone.
• Resolve a failed check before moving active client work.

Copy the exact link you would send to a client and open it in a fresh private browser window. For PIN access, check that an incorrect PIN leaves the gallery locked and the correct one opens it. Check what a locked page reveals about the gallery title and session before access is granted.

For invite access, create a demo invite, open it, revoke it, and try that invite again in a new private window. Revocation should end that invite path; it does not delete the gallery or promise to disable every other valid access path. If you also share a reusable PIN or another invite, account for those separately.

• Pass: the configured access rule works through the actual client link.
• Pass: a locked gallery withholds identifying gallery details.
• Pass: a revoked invite fails when opened in a fresh private window.
• Search directives such as noindex guide crawlers; they do not authenticate a viewer.

In the client view, favorite one proof, reload, and check that it remains selected. Remove that favorite and select the other proof. Compare the result with the favorite counts in the studio asset list so you can identify the chosen file without asking for a screenshot.

Agree on the final selection with the client before retouching, especially if several viewers have access. Framekeep records choices; it does not enforce the included image count, approve extra-image charges, or turn favorites into edited files. Your editor and existing studio agreement still determine that work.

• Pass: a saved choice survives a reload in the same viewer session.
• Pass: changing the choice updates the studio's recorded counts.
• Pass: the studio and client can confirm the same intended retouch list.
• If proof watermarks obscure expressions or details, adjust them before asking for selections.

Upload the separately prepared finished file, publish it, and use Mark as final. Check the following states from the client view. The Downloads setting applies to every published Final, so review the complete Finals set before enabling it.

Download the finished file individually and in the final-only ZIP. Open both and compare their contents with the intended delivery file. An unfinished proof should remain view-only even when finals are downloadable.

Framekeep studio galleries close and move to a reversible archive after 14 days. Put the selection date, editing time, and final-download deadline on one schedule before choosing the gallery. If the work needs more time, plan how the studio will restore access and communicate the revised dates. An invite can expire sooner; permanent deletion follows your separate studio policy.

Decide who may receive the link or PIN and record portfolio permission separately from delivery. Framekeep's access controls are not end-to-end encryption and cannot prevent screenshots, screen recording, or photographs of the display. Keep original files in your own archive and use your existing tools for editing, contracts, payments, and print sales.

• Pass: the client-facing dates match the actual gallery and invite access windows.
• Pass: you have a plan for archived galleries and keep a separate original-file archive.
• Pass: the client understands permitted sharing and the limits of visual protection.
• Pass: public image use requires its own permission decision.