Legal and policy center · Updated 15 October 2026
This policy explains what ShootGuide collects, why it is used, how long it is retained and the choices available to users.
We collect account and profile details, login identities, uploads and metadata, location/privacy choices, ratings, comments, inquiries, course and payment references, verification applications, manufacturer information, device/security logs and support communications. Payment providers process payment credentials separately.
Data is used to provide requested services, secure accounts, process enrollment, publish chosen content, operate rankings and verification, prevent fraud, moderate abuse, comply with law and improve performance. Marketing communications require the applicable consent or lawful basis and can be disabled.
Identity/business evidence and exact coordinates are restricted. Public location precision follows the uploader’s choice. Do not submit unnecessary sensitive information. Verification evidence is available only to authorized reviewers and retained according to the configured retention schedule.
Essential cookies maintain sessions and security. Aggregated profile analytics deduplicate views using a salted one-way hash and do not reveal individual viewers to photographers. Optional analytics or third-party embeds should load only under the configured consent rules.
Data may be shared with processors providing hosting, email, payment, monitoring or identity services under appropriate terms; with users according to your settings; during a lawful business transfer; or when required to protect rights, safety or comply with law. We do not sell personal information as a data-broker product.
Hosting and providers may process data in other countries. Production deployment must document provider locations and use legally required transfer safeguards.
We retain active account data while needed for service delivery; security/audit/payment records for legal and fraud periods; verification evidence only as long as necessary; deleted media through backup expiry; and permissions/licenses as needed to prove granted rights.
We use access controls, password hashing, private storage, audit records and transport security in production. No online system is completely secure. Users should use unique passwords and report suspected compromise.
Depending on applicable law, you may access, correct, export, object, restrict, withdraw consent or request deletion. Some records may be retained for legal, payment, fraud, dispute and rights-proof obligations.
The commercial launch must specify its minimum account age and any parental-consent process. Privacy-controller identity, postal address and privacy contact must be completed in the production operator notice before launch.
Use the platform’s report, permission-request or contact channel appropriate to your issue. Formal operator identity, postal address, privacy contact, copyright contact and dispute details must be added before production launch.