Photography studio proofing privacy
Does your gallery password protect your client's photos?
Client proofing galleries can store private photos and client details on your WordPress site. This sample compares documented gallery access, password handling, and direct image links. Check who can open galleries and image files, and what your exports and backups contain.
Based on plugin documentation, not tests of your site. Which fields you collect, who can open proofing screens, connector settings, and backup inclusion decide who can see private galleries. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks third-party requests made by a visitor's browser on the page you submit. It does not test gallery passwords, staff access, direct access to private image files, or what your exports, backups, and connected services store.
Site-hosted proofing vs outside client-delivery hosts
Proofing galleries on your WordPress site
Check how gallery passwords and share links are created, whether passwords are emailed in cleartext, which roles can open client galleries, and whether image files under uploads remain reachable by direct URL without the gallery login. Review retention after events close and whether download links expire.
Outside proofing SaaS and optional cloud add-ons
Many studios deliver galleries on Pixieset-class hosts with no citable WordPress.org plugin in this sample. Some site-hosted tools also offer optional cloud storage or payment processors. Those paths may hold originals or checkout data off-site. A browser scan cannot inspect vendor gallery databases or emailed password archives stored only on the server.
Photography studio proofing setups
No paid placement. Site-hosted proofing tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still use paid Pro or cloud add-ons when enabled. Names are alphabetical within each group.
This is a small documentation sample of WordPress photography studio proofing plugins, not a survey of Pixieset, ShootProof, or every client-delivery SaaS.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| PhotoProof Documented self-hosted proofing galleries and photos under /uploads/photoproof/ (and watermarked copies). Clients can browse without an account; a WordPress login (subscriber+) is required only to validate the final selection. Optional private UUID links replace guessable slugs. No shared gallery-password feature is documented. The listing states no third-party APIs, tracking, or analytics, and uninstall deletes galleries, photos, settings, and a custom table. Optional auto-archive 30 days after publication is described; an auth gate that blocks direct URL fetch of uploads/photoproof files without gallery access is not documented. Download-link lifetime is not documented (selection/CSV/email workflow, not a digital-download storefront). | Proofing galleries under uploads/photoproof on your WordPress site; UUID share links | Browser hosts not verified | Not assessed | Not tested |
| |
| picu – Online Photo Proofing Gallery Documented self-hosted proofing collections with randomized collection URLs and optional collection passwords. Default settings include the password in the client email; that can be disabled. Password hashing in the database is not documented. The FAQ states image links can be taken from page source and opened directly; Pro documents a “Prevent direct image access” setting so files are only usable from within a picu collection. Optional expire-collections default (docs cite 30 days) and deleting a collection deletes its images. Pro download / ZIP link lifetime is not documented in the sources reviewed. Browser hosts have not been verified for the free proofing path. | Proofing collections stored on your WordPress site; password may be emailed in cleartext | Browser hosts not verified | Not assessed | Not tested |
| |
| Sunshine Photo Cart Documented self-hosted client galleries with password-protected, private (allowlisted WP users), email-gate, and direct-URL listing-hide access types. After a correct password or email, the value is stored in the browser session (docs default up to 7 days). Password hashing in the database is not documented. Image protection docs describe random filenames and Apache hotlink rules under uploads/sunshine for full-size files; right-click protection is called a browser deterrent, and auth-gated file serving that blocks same-site direct URLs without gallery login is not documented. Privacy settings document configurable retention for inactive accounts, order personal data, and deletion of expired galleries after N days. Background-queue emailed zip download links expire after 48 hours. Optional Cloud Storage and payment add-ons are described but were not assessed as browser hosts here. | Client galleries and proofing on your WordPress site; optional print and download cart | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table compares documented photography studio proofing workflows. It does not test your site, consent timing, access controls, password hashing, or data retention. Check which client and event details you collect, who can access galleries, where connected services store originals, and what exports and backups contain.
Documentation snapshot: Oct 9, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-photography-plugin-privacy