ShootHarbor - Privacy Policy
Effective Date: May 13, 2026
Last Updated: May 13, 2026
BlueSparrow operates ShootHarbor, including the mobile application, public booking pages, public delivery pages, backend APIs, notifications, emails, subscriptions, analytics, support, and related services.
BlueSparrow is operated by a solo developer based in India. This Privacy Policy applies globally, including to users and client visitors in the European Union, United Kingdom, United States, India, Brazil, Canada, Australia, and other regions, subject to applicable local law.
Quick Summary
| Topic | Summary |
|---|---|
| Main purpose | Booking, shoot operations, delivery galleries, invoices, and payment follow-up for solo photographers. |
| Operator app | Firebase sign-in, local Drift storage, queued sync, and Rust backend APIs. |
| Public web | Booking pages, confirmation pages, and tokenized delivery pages for clients and leads. |
| Core storage | PostgreSQL through the Rust backend, plus local device storage and limited Firestore subscription mirror data. |
| Providers | Firebase, Google Play, RevenueCat, BSMailAllRust / BSAR-NC, hosting, analytics, diagnostics, and storage providers. |
| Sale of data | We do not sell personal information. |
| Privacy contact | privacy@bluesparrow.dev |
Contact Information
- Website: https://bluesparrow.dev
- General inquiries: info@bluesparrow.dev
- Privacy inquiries: privacy@bluesparrow.dev
1. Scope
This Privacy Policy applies to the ShootHarbor mobile app, public booking pages, public delivery pages, backend APIs, worker processes, notifications, emails, subscription checks, analytics, diagnostics, and support workflows connected to ShootHarbor.
This Policy does not apply to websites, apps, payment tools, storage locations, or communication tools operated by other companies and linked from ShootHarbor.
2. Roles
Operator account data: information about the photographer or studio user who signs in and manages the workspace. For this data, BlueSparrow generally acts as the operator of the service.
Client and shoot data: information entered by the operator or submitted through public pages, such as client contact details, locations, booking details, intake answers, media delivery, invoices, and communications. For this data, the photographer or studio is usually responsible for deciding what to collect and how to use it. BlueSparrow provides the infrastructure that stores, syncs, sends, and displays that data as part of ShootHarbor.
If you are a client of a photographer using ShootHarbor, contact that photographer first for questions about a specific booking, shoot, gallery, invoice, or delivery page. You may also contact privacy@bluesparrow.dev for questions about ShootHarbor's role.
3. Information We Collect
3.1 Account and sign-in information
When an operator signs in or uses ShootHarbor, we may collect Firebase user identifier, Google account email address, display name, profile image if provided, authentication state, sign-in timestamps, workspace identifier, membership information, and device identifiers used for local sync, security, and push notifications.
3.2 Workspace and business profile information
Operators may provide studio or business name, public studio slug, booking page identifier, logo, brand colors, public presentation settings, service region, timezone, contact preferences, public email, phone number, website, social links, tax settings, invoice settings, pricing settings, and templates for offerings, questionnaires, contracts, delivery copy, and invoice copy.
3.3 Client, lead, and booking information
Operators or public booking visitors may provide client names, requester contacts, on-site contacts, billing contacts, email addresses, phone numbers, company or family names, property or venue details, selected services, packages, add-ons, campaign slots, preferred scheduling windows, intake answers, notes, instructions, special requests, policy acknowledgements, lead source, referral channel, URL parameters, and referrer information.
3.4 Shoot workflow information
ShootHarbor may store shoot title, type, status, stage, source, schedule, timezone, calendar details, client snapshots, contact snapshots, property snapshots, pricing snapshots, intake snapshots, notes, checklist state, tasks, operational history, delivery state, invoice state, and payment follow-up state.
3.5 Media and delivery information
Operators may register, upload, process, publish, or share media asset metadata, file names or local upload metadata when needed for processing, private storage keys used by the backend, generated previews and thumbnails, delivery draft settings, cover choice, gallery title, client message, expiry notes, download settings, and tokenized public delivery links.
ShootHarbor is designed so public delivery pages use token-scoped preview URLs instead of exposing private storage keys directly.
3.6 Invoice and billing workflow information
ShootHarbor may store invoice records, invoice item details, prices, taxes, discounts, totals, currency, payment state, invoice email status, manual paid-state changes entered by the operator, and usage counters for confirmed shoots, booking pages, deliveries, media storage, and other plan limits.
ShootHarbor does not process public client checkout for the property-shoot MVP. Clients may pay the photographer outside ShootHarbor, such as by bank transfer, cash, or another operator-managed method.
3.7 Subscription information
For operator Premium subscriptions, we may receive or store app store product identifiers, RevenueCat customer identifiers, entitlement state, trial, purchase, renewal, cancellation, expiration, billing status, subscription sync timestamps, and limited Firestore mirror data needed by the app. Payment card numbers and app store payment credentials are handled by the app store, RevenueCat, or other payment-related providers. ShootHarbor does not store full payment card numbers.
3.8 Notifications, email, analytics, diagnostics, and support
ShootHarbor may process FCM device tokens, push preferences, delivery state, email addresses, email template data, message content, notification outbox status, retry counts, provider response metadata, device model, operating system, app version, locale, crash reports, diagnostic events, GA4 events, backend request logs, IP address or approximate network information, support messages, screenshots, logs, and attachments you choose to send.
4. Sources of Information
We collect information from operators, clients and leads who submit public forms or open delivery pages, sign-in providers such as Firebase Authentication and Google sign-in, subscription providers such as Google Play and RevenueCat, devices and browsers, backend systems, analytics, diagnostics, notification, and email providers.
5. How We Use Information
We use information to create and manage accounts, maintain workspaces, publish booking pages, receive booking requests, validate availability, offerings, pricing, quotas, workflow state, manage clients, contacts, locations, shoots, tasks, notes, deliveries, invoices, and payment follow-up, sync local app changes, process media, generate previews, publish delivery pages, send operational emails and push notifications, manage subscription state, enforce usage limits, provide support, monitor reliability, diagnose crashes, improve performance, secure the service, prevent abuse, and meet responsibilities that apply to the service.
6. Legal Bases Where Required
Where a legal basis is required, such as in the European Economic Area, United Kingdom, or similar regions, we rely on contract performance, consent, legitimate interests, and legal obligation as appropriate. Operators are responsible for choosing an appropriate basis for the client data they collect and process through ShootHarbor for their own photography business.
7. Email, Push, and Operational Communications
ShootHarbor supports public booking confirmation emails, operator alert emails, delivery published emails, invoice issued emails, reminder emails when enabled, support and feedback emails, and operator-facing push notifications through FCM. Operational emails are sent when the workflow requires them or when the operator triggers the relevant action.
8. Local Storage, Backend Storage, and Sync
- On-device local storage: Drift / SQLite stores a working set for fast use, offline access, queued changes, local upload state, and cached billing or quota snapshots.
- PostgreSQL backend: the Rust backend stores canonical workspace, client, offering, booking, shoot, delivery, invoice, usage, outbox, reminder, and audit records.
- Firestore mirror: Firestore is intentionally limited to lightweight authenticated user and subscription mirror data.
- Media storage: media originals, previews, and thumbnails may be stored in private backend-managed file storage or equivalent storage infrastructure.
The app may remain usable while offline or while the backend is temporarily unreachable. Some actions, such as delivery publish, invoice email, push notification delivery, media processing, and subscription enforcement, require a reachable backend.
9. Sharing and Service Providers
We do not sell personal information.
We may share information with service providers that help operate ShootHarbor, including Firebase Authentication, Firebase Cloud Messaging, Firebase Analytics / GA4, Crashlytics, Firestore, Firebase Functions, RevenueCat, Google Play, BSMailAllRust / BSAR-NC, hosting, database, storage, security, and anti-abuse providers.
We may also share information when an operator publishes a public booking page or delivery page, when an operator sends an email or shares a link, with the operator who controls the relevant workspace, when required to protect the service or respond to valid official requests, or as part of a business transition for the ShootHarbor service.
10. Public Pages and Shared Links
Public booking pages and public delivery pages may be visible to anyone who has the link, depending on the operator's settings and the type of page. Delivery links use non-guessable tokens, but anyone with a valid link may be able to open the page unless additional access controls are added. Operators should share delivery links carefully.
11. Cookies and Similar Technologies
The mobile app and public web pages may use local storage, device identifiers, cookies, SDK identifiers, or similar technologies to keep the app or page functioning, remember session or runtime settings, support Firebase, subscription, analytics, diagnostics, security, anti-abuse features, measure public booking and delivery funnel events, and preserve attribution such as ref, source, channel, UTM values, or referrer details. Where required, consent or additional notices may be provided for optional analytics or tracking technologies.
12. International Processing
BlueSparrow is based in India. Service providers and infrastructure used by ShootHarbor may process information in India, the European Union, the United States, and other countries. Where required, we use appropriate safeguards such as provider agreements, access controls, security measures, and transfer mechanisms recognized by applicable law.
13. Data Retention
We keep information for as long as reasonably needed to provide the service, maintain accounts, support sync, handle support requests, maintain security, meet applicable obligations, and preserve operational records.
- Account and workspace data: while the account or workspace is active and for a reasonable period afterward.
- Client, booking, shoot, delivery, and invoice data: until the operator deletes it, requests deletion, closes the account, or it is no longer needed for service operation.
- Media files and generated previews: while needed for delivery, sync, storage, or operator workflow, subject to plan limits and deletion tools.
- Local device data: until the app cache is cleared, the user signs out, the app deletes local records, or the app is uninstalled.
- Notification and email outbox records: while needed for delivery, retries, audit, abuse prevention, and operational support.
- Subscription records: while needed for entitlement history, billing support, and app store or provider reconciliation.
- Backups: retained for a limited backup cycle and then overwritten or deleted according to infrastructure practices.
14. Your Choices and Privacy Rights
Depending on the feature and your location, you may be able to update account, workspace, branding, template, and contact settings, delete or edit clients, shoots, deliveries, invoices, and media where app controls exist, stop using public booking or delivery links, cancel or manage subscriptions through Google Play, disable push notifications through device settings, opt out of optional communications where an opt-out method is provided, or request access, correction, deletion, export, restriction, or objection by contacting privacy@bluesparrow.dev.
Depending on your location and how local law applies, you may have privacy rights under GDPR, UK GDPR, Swiss data protection law, United States state privacy laws, India's Digital Personal Data Protection framework, Brazil's LGPD, and privacy laws in Canada, Australia, and other regions. We may need to verify your identity, account, workspace, or authority before responding.
15. Advertising, Sensitive Data, and Automated Processing
We do not use client shoot content, private media, invoice details, or intake answers for cross-context behavioral advertising. ShootHarbor is not designed to collect sensitive personal information beyond what an operator or client chooses to enter for a photography workflow. Operators should avoid collecting unnecessary sensitive information and should obtain appropriate consent when their workflow requires special categories of information, images of minors, property access details, or other sensitive context.
ShootHarbor may use automated rules for quota checks, sync conflict detection, duplicate or idempotency checks, availability validation, notification retry timing, and media processing status. ShootHarbor is not designed to make decisions with legal or similarly significant effects about individuals.
16. Security
We use reasonable safeguards designed to protect information, including HTTPS / TLS, authenticated operator routes, Firebase token verification, workspace-scoped backend permission checks, PostgreSQL-backed canonical storage, private media storage keys, tokenized public delivery access, structured logging, backend-owned queues, provider secrets stored outside public client code, and limited Firestore mirror data.
No system can be guaranteed completely secure. Operators should use secure devices, keep their Google account safe, protect shared delivery links, and avoid collecting more client data than needed.
17. Children and Family Photography
ShootHarbor is intended for photographers and business operators. It is not directed to children. Some photography workflows, such as family portraits or mini-sessions, may involve children or family information entered by an adult client or by the photographer. Operators are responsible for obtaining any required permission from parents, guardians, or clients before collecting, uploading, publishing, or sharing images or information involving children.
18. Operator Responsibilities
If you use ShootHarbor as a photographer or studio operator, you are responsible for making sure you have a lawful reason to collect and use client data, giving clients any notices required for your business, obtaining permissions for photos, family/session details, property access, signatures, contracts, emails, and delivery links, keeping your account and devices secure, checking public booking, invoice, delivery, and email content before publishing or sending, and using ShootHarbor in a way that respects privacy, consumer, tax, marketing, intellectual property, and professional obligations that apply to your business.
19. Data Deletion and Account Closure
You may request deletion of account data by contacting privacy@bluesparrow.dev from the email associated with your account, by using the ShootHarbor deletion page, or through any in-app deletion flow that becomes available.
Before deleting an account or workspace, we may need to verify your identity and authority, preserve records needed for subscription, support, security, accounting, or compliance reasons, complete a reasonable backup expiration cycle, and avoid deleting data controlled by another workspace operator where you are not authorized to request deletion.
20. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date and may provide notice in the app, on the website, or by other reasonable means when the change is important.
For terms that apply to use of ShootHarbor, see the Terms of Use.