Draft for review — not yet in effect.

Privacy

Last updated: October 20, 2026. This draft describes how Captr handles account, booking and media information. It needs business and legal review before launch.

What we collect

• Account and contact information, including your name, email address and phone number, for sign-in, booking notices and support. Captr stores profile phone numbers, including the client’s and the Creative’s numbers, to connect masked calls. Neither side sees the other’s number.
• Booking and purchase history, including the service, schedule, quote, payment status and payout records.
• The shoot address, lockbox code and access notes, stored encrypted; shoot briefs, reviews, revision requests and support notes.
• Photos and videos uploaded by Creatives, and files clients send for Studio Edit. Metadata is stripped only from JPEG and PNG working copies. RAW camera files, HEIC photos and video are passed through as recorded and can contain location metadata. Editors receive these originals with the camera’s metadata, which can include location.
• A Creative’s precise location while on the way to an accepted shoot. Only the latest position is kept for that job, and it is removed when the job leaves the on-the-way state. The client sees a rounded position only while it is less than five minutes old.
• Your Lookbook, if you make one: which versions of the example photos and clips you picked, your answers (such as vertical or horizontal), the situations you chose, any notes, and the style profile worked out from them. It is saved to your account so it follows you to a new phone. You can delete it in the app at any time, and it is deleted with your account.
• Quote requests, including contact details, ZIP, preferred dates and your description; Creative and Editor applications; and waitlist email addresses and interests.
• Sign-in session information, push notification device tokens, and request information used for security and rate limiting, including an IP-derived identifier.

Why we use it

We use this information to sign you in, arrange and deliver work, process payments and payouts, show arrival updates, send service notices, answer requests and protect the service from abuse. The current app has no advertising or analytics SDKs and no cross-app advertising tracking. This draft provides for no data trading.

Who sees what

• Clients: your own bookings, access details, work status and delivered files, plus the assigned Creative’s first name and an arrival update while they are on the way.
• The accepted Creative: the shoot brief and work instructions, with the address and access details available from 12 hours before the shoot until 4 hours after its scheduled start. If a dusk visit is booked, access also opens 30 minutes before that visit and closes 30 minutes after it. The gap between those windows stays closed. The Creative’s job view does not show the client’s name, email or phone number. Twilio connects calls using Captr’s number.
• Editors: assigned media, editing instructions, standards and revision feedback. Editor job views never show the shoot address, client name, phone, email or shoot brief. Uploaded media and editing notes can themselves identify a person or place; camera-original files can contain location metadata.
• Your Lookbook: your photographer and Editor see a one-line summary of your style on your bookings, in the brief and editing notes. They don’t see your individual answers.
• Ops: authorized studio staff can access the booking, contact and access information needed to arrange work and resolve problems. Reads of Creative access details record who accessed them and when, rather than the lockbox code.

Avoid putting contact details or lockbox codes in media, editing notes, reviews or other free-text fields. Use the designated encrypted access fields for entry information.

Service providers

The service uses these providers when the corresponding service is configured:

• Supabase: database and sign-in, including account, booking and content records.
• Vercel: website hosting and scheduled processing.
• Media storage: uploads and delivered files use a configured S3-compatible storage provider: [provider confirmed at launch]. The launch provider must be confirmed before this policy takes effect.
• Stripe: payments and Stripe Connect payouts. Stripe hosts collection of Creative and Editor identity, tax and bank details; Captr stores the connected account identifier and payout setup status, rather than those submitted documents and bank details.
• Resend: service email, including booking and payment notices.
• Twilio: masked phone calls. Captr sends the stored phone numbers to Twilio to bridge the call; neither participant’s job view exposes the other participant’s real number.
• Apple Push Notification service: device tokens and service notifications.
• Upstash: request counters and identifiers for rate limiting.
• Slack: internal studio alerts. Quote-request alerts contain service, market and ZIP rather than contact details. Other alerts can include booking references, status, studio links, Creative display names and redacted problem notes. Redaction does not guarantee that all personal information in free text is removed.

Retention and account deletion

Booking and payment records are retained for accounting and reconciliation. Retention periods for those records, media, enquiries, applications, waitlist entries and provider backups must be confirmed before launch; this draft does not promise a fixed deletion deadline.

You can delete your account in the Captr app: tap the account button at the top of Bookings or Work, choose Delete account, and type DELETE to confirm. If you can’t use the app, contact the studio. Your account stops working at once. Personal details are then scrubbed, and your sign-in is removed. Unfinished bookings and accepted assignments must be resolved, and unpaid earnings paid, before an account can be deleted. In that case nothing is removed and your account keeps working; if it stays locked, the studio restores access after checking. An account whose details have been scrubbed stays closed, even if removing the sign-in has to be finished by the studio.

The scrub removes your profile name and phone; worker home ZIP, categories and active status; Editor timezone preferences; push devices and current positions; linked enquiry contact details, request details, preferred dates and ZIP; review comments; shoot addresses, lockbox codes and access notes; briefs and edit notes; revision notes and outcomes; and ticket subjects and bodies. Roles are disabled. Linked enquiries are detached from the account and use anonymous placeholders where required, as do revision and ticket text fields.

We are retaining booking and financial records and their identifiers for accounting: projects, payments, payouts, assignments, project events, review scores and connected payout-account records. System cancellation reasons remain. Deletion does not erase all media, unlinked applications or waitlist entries, separate requests or provider backups automatically. Closing a Stripe Express account is a separate studio step after all earnings are paid. If a deletion is interrupted, Captr finishes it automatically or the studio does. We don’t yet promise a fixed retention period for the records we keep; it is being confirmed with legal counsel.

Your choices

You can manage notification and location permissions in your device settings. Location permission is used for Creative arrival updates; disabling it prevents those updates. Contact the studio to ask about access, correction or deletion of your information, including requests sent without an account. The studio must confirm the applicable rights and request process before launch.

Children

Captr is intended for adults aged 18 and over and is not intended for anyone under 18. The current app has no age gate. If you believe a child has provided personal information, contact the studio so it can review the request.

Contact

For privacy questions, contact bookings@captr.life. The studio must confirm this contact is monitored before launch.

Changes

We will update the date on this page when the policy changes. Any required notice of material changes and the policy’s effective date will be confirmed during legal review.