Photographs stay elsewhere
CaptureBeacon does not store original photographs, edited photographs, thumbnails, or gallery files. External galleries and storage remain with the customer’s selected provider.
Privacy & trust
Keep the operational trail. Leave the photograph files alone.
The platform is designed around a narrow job: coordinating photography-service work without becoming a photograph repository.
Only useful operational records
The platform may store the records required to run the workflow: statuses, counts, dates, permissions, links, completion history, and audit events.
A workspace is not a shared bucket
Each customer workspace has its own identity, administrators, team members, events, destinations, settings, permissions, and reporting history. Isolation is a release requirement.
Public means intentionally public
Public pages must never expose private participant or administrative information. Guided-preview data is invented and periodically reset.
No professional-status assumptions
CaptureBeacon displays information supplied by users. It does not certify a person’s legal status, license, insurance, business registration, trademark, or professional standing.
Responsibilities remain clear
Users remain responsible for permissions, branding, services, applicable law, and the providers they select. CaptureBeacon’s explanations are not legal advice.
Program relationship
CaptureBeacon is currently a program of Frames of Service Foundation. It is not presently described as a separate company or subsidiary.