Privacy Policy

Shootbin is the controller for data processed for its own purposes. For customer content uploaded to manage a photographer's or studio's clients, the Shootbin customer is normally the controller and Shootbin is the processor.

Depending on how the service is used, this can include names, first and last names, display names, email addresses, optional telephone numbers, language, time zone, account type, roles, login and activity data, communication preferences and account status; company, VAT, billing address, country, billing email, customer type, subscription, payment status and Mollie identifiers; projects, albums, memberships, invitations, approvals, ratings, comments, annotations, messages, revisions, history, audit events, statuses and deadlines; photos, originals, web variants, revisions, thumbnails, delivery files, ZIP files, watermarks, filenames, EXIF, keywords and other technical metadata; and contract signer data, timestamps, IP address, user agent, hash, locale, status and audit events. A photo is personal data when a person is directly or indirectly identifiable. It is not automatically special-category data, but it can reveal such information in some cases.

Shootbin is the controller for account administration, profiles, subscriptions, billing, our own customer administration, security, login information, service communication, support, technical logs and business administration. When a customer uses Shootbin for photos and data about their own clients, models, employees or other people, that customer decides why and how the data is used. In that situation, Shootbin processes the data only to provide the service and on the customer's documented instructions.

We process data to perform the agreement, including account management, project functionality, storage, delivery, collaboration, subscriptions and technical operation; to comply with legal obligations, including tax records, invoices, accounting and lawful requests; and for legitimate interests such as fraud and abuse prevention, security, logging, technical monitoring, reliability and error detection. Consent is used only where it is actually required. The customer remains responsible for the legal basis for customer content, including photos.

Production is hosted on Railway, where the application, database, queues, cache and background processing can process account data, project metadata, messages, annotations, approvals, ratings, contracts, billing metadata, login and security data and technical logs. Photos and other persistent customer objects are stored in Cloudflare R2 with the EU jurisdiction configuration, so persistent object data is stored within the European Union in accordance with that configuration. Cloudflare Workers, CDN, network and security services can process data temporarily or at the edge; this does not mean every network operation is guaranteed to take place only in the EU.

Active account data is kept while the account or service relationship exists, subject to legal obligations. Hobby accounts are assessed after about 90 days of inactivity, warned after about 120 days, and may be deleted 14 days after that warning if there is no new activity. Deleting an account or project starts the implemented deletion flow; soft-deleted photos, albums, projects and revisions are permanently purged by background jobs after the applicable retention state. Delivery ZIPs are retained for 7 days for Hobby and 30 days for Beta, Studio, Agency and Nonprofit, with a warning 3 or 7 days before expiry depending on plan. Personal data exports are available for 14 days. Temporary uploads and traces are cleaned after 30 days. Billing, security, dispute and legally required records may be retained longer, and backup copies may persist until their normal rotation.

The application uses HTTPS/TLS, authorization and project-based access controls, role permissions, private object storage and short-lived signed URLs where applicable. Passwords are hashed with Laravel's password hashing and are not reversibly or plainly stored. Certain tokens and secrets, including payment connection tokens, are encrypted using Laravel encrypted casts. Security logging, queue isolation, backups, monitoring and deletion flows are used as appropriate. No method of transmission or storage is completely risk-free.

You may have rights to access, rectify, erase, restrict, port and object to processing, and to withdraw consent where consent is the legal basis. Contact support@shootbin.com. Authenticated users can request a personal-data export; the export is protected by account access and its download is available for 14 days. If your request concerns photos or project data uploaded by a Shootbin customer, that customer is normally the controller. We can forward the request and support the customer with export, correction or deletion. You may complain to the Belgian Data Protection Authority or another competent supervisory authority.

Shootbin's accounts and service are not directed specifically at children. Photographs uploaded by photographers can nevertheless contain minors. The photographer or other controller must have a valid legal basis and obtain consent where the law requires it. Contact us if you believe data has been processed unlawfully.

Shootbin uses essential session, authentication, CSRF and security cookies, plus cookies or local preferences needed to remember language, currency or interface settings. We do not use marketing cookies or advertising trackers in the service. Non-essential analytics cookies are not used by this policy. Disabling essential cookies can prevent login or normal operation.

Cloudflare R2 persistent object storage uses the EU jurisdiction configuration. Railway and Cloudflare infrastructure may involve processing outside Belgium, and network or security processing is not represented as exclusively European. Where personal data is transferred outside the European Economic Area, Shootbin applies the safeguards required by applicable data-protection law, such as an adequacy decision or appropriate contractual safeguards where needed. Mollie processes payment data under its own privacy terms and role for the relevant service.

For privacy questions or requests, contact Shootbin at support@shootbin.com. We may update this policy when the service or legal requirements change and will publish the new version here.