Intimate Portrait Delivery and Private Proofing

What makes intimate portrait delivery high-stakes

Intimate portrait delivery can expose sensitive images when access, forwarding, downloads, or retention are left undefined.

For a studio gallery, select an optional PIN or invite when access must be restricted. Branding does not provide authorization.

Start with the recorded access choice

Ask the client who may view, then configure the narrowest access that satisfies that choice. Access can be expanded later at the client's request.

Document and test the settings so the public privacy explanation matches the actual gallery configuration.

• Configure PIN or invite access for client-only delivery; add partner access only when requested.
• Proofing-gallery downloads disabled; the gallery's published Finals used for delivered selects.
• Expiring invites rather than permanent share links.
• A visible retention policy so galleries do not live forever by accident.

Proofing and favorites: keep it simple and private

Give the proofing client one primary action: favorite the images selected for studio review.

Avoid public comments and document whether viewer identity is required before favorites can be recorded.

• One client action: favorite selections.
• One deadline: favorites due date.
• One promise: how long finals will take after favorites are in.

Secure sharing: make it optional and revocable

If a client wants to share with another person later, create a separate invite that can expire or be revoked.

Do not rely on a permanent URL that can be forwarded indefinitely. Separate invites and expiration policies keep consent flexible over time.

• Enable partner invites only after the client requests it.
• Use an expiring link so access naturally ends.
• If a client changes their mind, disable access immediately without drama.

How to explain retention without sounding scary

State how long proofs and finals remain available, when invites expire, when the studio deletes the gallery, and how to request an extension.

Studio galleries close and move to a reversible archive after 14 days; invite expiry and permanent gallery deletion remain separate controls.

• Proof gallery available for a short window (for example, 14 to 30 days).
• Final downloads available longer (for example, 90 days or your studio standard).
• Extensions available on request, with the client controlling who has access.

What the delivery page should answer

Explain the access method, forwarding limits, download scope, screenshot limits, invite expiry, and gallery retention.

The intimate portrait gallery guide covers those decisions.

Device safety and screenshots: what you can (and cannot) control

No platform can stop someone from taking a screenshot. Privacy is about reducing exposure and controlling access, not guaranteeing that an image can never be copied.

The studio can control the PIN, invite status, and gallery-level final-download setting. A viewer with valid access can still forward the link or capture the screen.

If you need extra caution for a client, consider a shorter proof window, stricter access rules, and clear reminders about discretion.

• Use the correct access model: an anonymous shared password, or a studio PIN or expiring invite.
• Keep proofing-gallery downloads off; use the gallery's published Finals for delivered selects.
• Limit sharing by using separate partner invites instead of a single link.
• Communicate the selected PIN or invite path, invite expiry, and separate gallery-retention date.

Use public examples without exposing client galleries

Keep public examples separate from client delivery and treat them as marketing assets.

Only use images with explicit permission for public marketing. If a client prefers anonymity, honor that with careful crops or approved details that do not identify them.

Label exactly what the example demonstrates. A read-only example does not prove a working PIN, invite, favorite write, or permitted download.

• Use only images approved for public use, in writing.
• Never reuse a real client gallery link as a “sample.”
• Keep sample copy neutral: privacy features, steps, and what is downloadable.
• Link the sample experience from your niche pages and blog posts.

A small technical checklist that prevents mistakes

A pre-send checklist can catch access, preview, invite, and download-setting mistakes.

Keep the checklist in your studio notes so you can run it before sending a gallery link.

• Confirm private routes are omitted from the sitemap and send noindex directives; separately test access control as the privacy boundary.
• Verify the anonymous shared password or the studio PIN/invite path before sending the link.
• Check that the proofing gallery's downloads are disabled (if that is your policy).
• Confirm invite expiry and retention expectations are correct; studio galleries archive automatically after 14 days.
• Double-check who has invites before enabling partner access.