Intimate Portrait Galleries: Discreet Proofing and Secure Delivery

Intimate portrait work can include boudoir, bridal boudoir, and other private sessions. Configure delivery from the client's recorded access and sharing choices.

Framekeep omits private routes from sitemaps and sends noindex and robots directives for compliant crawlers. Authorization remains the privacy boundary, and indexing directives are not a guarantee.

A permanent URL is hard to take back once it is forwarded. Use invites that can expire, and make it easy to disable access if a client changes their mind.

This approach supports consent updates after the shoot.

• Prefer expiring invites over permanent share links.
• Configure PIN or invite access for client-only delivery; add partner access only when requested.
• Expire or revoke proof invites, then delete galleries under the studio's retention policy.
• Keep finals accessible per your retention policy, not forever by accident.

An authorized viewer can capture the screen, and any downloaded file can leave the gallery. Keep final-only downloads off during proofing and explain the screenshot limit.

Use private favorites for selections and avoid public feedback.

Framekeep studio galleries can show a logo, custom accent color, and White or Dark theme.

Brand settings are separate from the optional PIN or invite used for authorization.

Publish the access rules, invite expiry, final-download state, screenshot limit, and gallery-retention policy.

State who can request an access change and which action the studio will take.

Ask who may view, then choose a studio PIN or invite if access must be restricted. Test the configuration while signed out.

Make the public privacy explanation match the observed gallery behavior.

• Configure PIN or invite access for client-only delivery when that matches the recorded consent choice, with optional partner invites later.
• Proofing-gallery downloads disabled; the gallery's published Finals used for delivered selects.
• Expiring invites and a stated retention timeline.
• Watermark proofs only if needed, and remove for finals.

Check for long-lived invites, unclear sharing rules, final-only downloads enabled during proofing, and galleries retained beyond the stated policy.

If you share a sample gallery publicly for marketing, keep it separate from client work and make sure it contains only images that are explicitly approved for public use.

Some clients want to share with a partner later, but they do not want to decide on day one. Keep sharing optional and reversible so consent can evolve over time.

Offer two clear modes: PIN or invite access configured for the client now, and an optional partner invite later with an expiration window.

• Create a partner invite only after the client requests it.
• Set a short expiration window for partner access.
• Give the client one way to ask the studio to revoke access.
• Keep proofing-gallery downloads disabled; approval does not create asset-level download permission.

Ask whether the client will use a shared phone, tablet, or computer, and mention that browsers, email previews, and saved links may expose session details.

Match configured client or partner invite access to the recorded consent choice, and state invite expiry separately from gallery retention.

• Prefer expiring invites over a single long-lived share URL.
• Make revocation easy so consent changes can be honored quickly.
• Use an expiration policy for proofs and a clear retention window for finals.
• Avoid putting passwords in places that get forwarded or saved automatically.

Tell the client that proofs are for choosing and delivered finals are for saving.

If you use retouching approvals, keep them structured and private so feedback does not spill into texts or social DMs.

• Keep the proofing gallery downloads disabled and use favorites for selects.
• Deliver finals from the gallery's published Finals with clear naming.
• Confirm selects before retouching and record any later change.
• Enable partner viewing later by invite if the client requests it.