Privacy Policy - Crew Confirm

Effective October 30, 2026. Last updated November 1, 2026.

1. Who we are, and our two roles

Crew Confirm is software that wedding studios use to staff and coordinate their crew. It is run by Uriel Arnson LLC, a New Jersey limited liability company ("Crew Confirm", "we"). We handle personal information in two roles. For everything a studio keeps in Crew Confirm (its weddings, crew records, bookings, pay records, chat and the rest), the studio decides how it is used and is its controller; we are the studio's service provider (processor) and use it only to run the Service for that studio. For studio accounts and billing, sign-up and demo requests, guide download requests, sign-in records and our own records of text-message consent, we are the controller, and this policy governs that information directly.

2. Whom this covers

Studio owners and staff (Owner, Studio Manager, Studio Editor); crew, whether or not they sign in; couples, family members, guests and venue contacts a studio enters for a wedding (they do not use Crew Confirm and we never contact them); and visitors to our website who send us a request. If you work with a studio, or a studio photographs your wedding, that studio is responsible for its own use of your information.

3. What we collect

Studio sign-up and accounts (we are the controller). When you start a studio: the studio's name, your name, email and (if you give it) phone, what the studio shoots, how many crew it books, the plan you chose, how you heard about us if you say, and the guide you came from if you came from one. If you reached us through a link in one of our ads, we also keep the short labels in that link, which name the source, the campaign and the ad. We keep them with your sign-up request and our payment record for it, so we can see which ads bring studios to us. We do not keep the web address itself or the page you came from. When you pay: which version of our terms you accepted, and when. When you book a demo: your name, email, and if you give them, the studio's name and how many crew it books. For a studio: the Owner's contact details; to register the studio's texting with carriers, its legal name, business type, EIN (its federal tax ID), business address and a representative's name, title, email and phone, with the EIN and the representative's email and phone stored encrypted; and the plan, trial and billing status. Card details are taken and held by Stripe; we receive only Stripe's customer and subscription references.

Guide downloads (we are the controller). When you ask for a free template from one of our guides: your email, your first name if you give it, which guide, and whether you ticked the box to get new guides by email (it starts unticked). We email you the download link once. We email new guides, about once a month, only if you ticked that box; reply to any of them, or write to us, to stop.

Sign-in (we are the controller). Name, mobile number, email, a salted hash of the password (never the password itself), how you sign in, session records and notification settings. If you allow app notifications on a device: that device's notification address and a rough label for it (such as "iPhone - Safari").

Studio data (we are the studio's processor). About crew: roles, rates, the studio's notes, availability, answers to booking requests and holds, bookings, schedules, day-of status taps, arrival times, requests for help on the day, wrap-up and file-delivery reports, invoices, expenses, payment details given to the studio (the destination is stored encrypted), document records, chat messages and poll answers. About weddings: couple names, dates, venues (Wi-Fi passwords are stored encrypted), schedules, family and portrait lists, shot lists and notes.

Message records. For texts: whether a person opted in, when, for which number, and any STOP or START, kept as a history of each opt-in and opt-out with the wording agreed to; the text of each message; delivery results; and the time of any other reply, never its words. Sign-in codes are sent and checked by Twilio; we do not store them.

Technical information. Your IP address is used, in memory, to limit repeated sign-in attempts and form requests; we do not store it with what you send. Our hosting and network providers keep their own request logs, which include IP addresses. Our emails load no web fonts; they use the fonts already on your device. Cookies are covered in section 17.

What we do not collect. No background location tracking (live location is off unless a crew member turns it on; see section 16); no Social Security numbers or other personal government ID numbers (the one tax ID we collect is a studio's EIN, for carrier registration, as described above); no full card numbers; no wedding photos or videos (files go to the studio's own file-delivery provider); no contact lists from your phone.

Do Not Track. We do not track you across other websites, and no one collects information about you through our site to follow you across other sites. So a browser's Do Not Track signal changes nothing here: every visit is treated the same way.

4. How we use it

Studio data, only to run Crew Confirm for that studio: send booking requests and holds, record answers, share schedules, coordinate the day, keep invoices and statements, send the messages the studio's use of the app triggers, keep the Service secure, give support the studio asks for, and comply with law. Information we control, to review sign-up requests and reply to them, run studio accounts and bill subscriptions, see which of our ads lead to sign-ups and payments, register each studio's texting and keep proof of consent and opt-outs, answer requests, send the guide downloads you ask for (and new guides, only if you asked for them), and comply with law. We do not use personal information or studio data to train AI models, and Crew Confirm has no feature that sends it to an AI service.

5. What we never do

We do not sell personal information. We do not share it for cross-context behavioural advertising. We show no ads in the app or on our website. We do advertise Crew Confirm on other companies' services, and nothing about you goes to those services from our website or app for advertising. Mobile phone numbers and text-alert opt-in consent are never sold or shared with third parties or affiliates for marketing or promotional purposes. We never show one studio's information to another studio.

6. Studios are kept apart

No studio can see another studio's data or whether its crew also work with other studios. Today each studio's data is held in a database of its own; if that changes, studios stay kept apart within the shared system and we will update this policy first. Uriel Arnson LLC also runs a wedding studio that uses Crew Confirm like any other customer; it has no access to other studios' data, and studio data is never used for its business. Our people, and the tools they use, reach studio data only to give support a studio asks for, keep the Service secure and working, or comply with law.

7. Who we share it with

The studio you work with, for its own data; the service providers in section 8, only to provide their service to us; phone carriers and messaging networks, which must receive a number and a message to deliver it; authorities when the law requires it or to protect anyone's safety; a buyer or successor if the Crew Confirm business is sold or reorganised, under the same protections; and anyone else only with your consent.

8. Service providers (sub-processors)

These providers run parts of Crew Confirm for us and may use information only to do so:

Railway Corp.: hosting, database and scheduled jobs. Information: all app data.

Twilio Inc.: text messages, delivery results, STOP and HELP replies, sign-in and confirmation codes, and registering each studio's texting with the carriers. Information: mobile numbers, message text, delivery data, and the studio's texting registration details (its legal name, EIN, business address and a representative's name, title, email and phone).

Stripe, Inc.: studio subscriptions and payments. Information: the Owner's billing details and card data (held by Stripe), the record of accepting our terms at checkout and, if you came through one of our ads, that ad's labels; no crew data.

Resend: account, sign-up and guide download emails. Information: names, email addresses, email content.

Ably: live delivery of chat messages. Information: chat messages in transit.

Cloudflare, Inc.: web address, network protection and secure connections. Information: web traffic, IP addresses.

Mapbox, Inc.: the live crew map, driving times and finding a venue on the map. Information: the position of crew who chose to share it, venue addresses, and the connection details and usage data of a device showing the map.

Browser makers' notification services (such as Apple, Google and Mozilla): delivering app notifications to the devices that allowed them. Information: a device address issued by that service and the notification, in encrypted form.

Kapso and Meta Platforms, Inc. (WhatsApp): WhatsApp messages, only where WhatsApp is switched on for a studio. Information: mobile numbers, template messages, delivery data.

Google LLC (Google Workspace): our own email mailbox. Information: what you write to us, and our replies.

Not our provider: a studio's own file-delivery service (for example Filemail) is chosen by and contracted with the studio; Crew Confirm only links to it or shows its page, and that service's own terms and privacy policy apply to the files sent through it. When this list changes we update this section and its date.

9. How long we keep it

Studio data is kept while the studio's subscription runs and while it is read-only; nothing is deleted when a studio becomes read-only. A crew member's past work with a studio stays part of that studio's records. Sign-up and demo requests are kept so we can reply and follow up. Guide download requests are kept so we know whom we emailed and who asked for new guides. Billing records are kept for tax purposes, and proof of text consent and opt-outs for as long as it may be needed to show them. We have no fixed schedule that deletes these records automatically; the one exception is the position behind live location, which is deleted automatically (section 16). A studio's Owner can ask us to close the studio and delete its data by writing to [email protected], and you can ask us to delete information we hold as controller; we do so within a reasonable period, except what the law or a dispute requires us to keep. Copies in our hosting provider's backups last until those backups expire.

10. How we protect it

Secure (HTTPS) connections; passwords stored only as salted hashes; signed sign-in cookies that expire; payment destinations and venue Wi-Fi passwords encrypted on top of the database, with a record of who revealed them; a studio's EIN and its representative's email and phone encrypted too; role checks on what each person can see and do; and no hosting of wedding photos or videos. No system is perfectly secure. If we learn of unauthorized access to personal information, we will tell the affected studios, and others where the law requires, without unreasonable delay.

11. Your choices and rights

In the app you can see and correct your contact details and turn texts, app notifications and live location off; you can also reply STOP to any text. You can ask us for a copy of the information we hold as controller, or ask us to correct or delete it, by writing to [email protected]. Depending on where you live (California, New Jersey and other U.S. states have such laws), you may have the right to know what we collect and how we use it, to get a copy, to correct it and to have it deleted. We do not sell personal information or share it for targeted advertising, so there is nothing to opt out of. We may need to confirm who you are first, we will answer within 45 days, an agent you authorize may ask for you, and if we say no you can write to us again to appeal. Requests about a studio's records (bookings, pay, notes, chat) are decided by that studio: if you send one to us we pass it to the studio and help it answer. We will not treat you differently for using these rights.

12. If you are crew

The studio you work with invited you and decides how it uses Crew Confirm for your work with it. It sees your name, contact details and your work with that studio, never your work with other studios. Texts are your choice, studio by studio: you opt in yourself in the app, reply STOP to stop a studio's texts, and saying no never limits your access or your work. Live location is your choice too (section 16). Crew Confirm records invoices and payments between you and a studio; it never moves money and never charges you. If you leave a studio it keeps the record of your past work with it, but gets nothing new.

13. Couples, families and guests

A studio may enter your name and details (for example a wedding schedule or a family photo list) so its crew can photograph your wedding. We use them only to run Crew Confirm for that studio and never contact you. For questions, contact the studio; you may also write to us and we will pass it on.

14. Children

Crew Confirm is a business tool, not directed to children, and accounts are for people 18 or older. We do not knowingly collect information from children under 13. A family or shot list may mention a child's name so a wedding can be photographed; that is the studio's information, used only for that purpose.

15. Texts

Texts come from the studio, under the studio's own verified texting registration, sent through Crew Confirm. They are operational messages about your work. Consent is optional, given in the app for each studio, and not required to use Crew Confirm or to work with the studio. Message frequency varies. Message and data rates may apply. Reply STOP to opt out, HELP for help. Each studio's full program terms are on its own SMS page, linked from the app.

16. Live location

Crew may choose to share their location on a wedding day. It is off unless the crew member turns it on, after a screen that says who sees what, and we record when it was turned on and off. The studio cannot turn it on. It works only for a wedding they are confirmed on, from 2 hours before their start time until 2 hours after it, or 1 hour after their scheduled end time if that is sooner, and only while the app is open on their phone. The studio's Owner and Studio Manager see it for that wedding; teammates on the same wedding see it only while they share their own. Only the latest position is stored, and it is deleted when the window closes or sharing is turned off. The arrival time and arrival status stay in the wedding's record. The position goes to Mapbox to work out the arrival time. Location is never used to change pay or hours, and is never sold or used for advertising.

17. Cookies and tracking

One strictly necessary cookie keeps you signed in. Our network provider, Cloudflare, may set a short-lived security cookie. The app also keeps small settings in your browser, such as whether you dismissed a card. There are no advertising or analytics cookies, pixels or third-party tools on the website or in the app, and our fonts are served from our own site. If you arrive through a link in one of our ads, we read the ad's labels from that link once and send them with your sign-up form. We do not use cookies or browser storage for this. The live crew map is loaded from Mapbox, and only on the wedding pages that show it; it sends Mapbox its own usage data.

18. Where it is stored

Crew Confirm is for U.S. studios and their crew. Our service providers in section 8 may store and process information in the United States or in other countries.

19. Changes

We will post changes here and change the dates at the top of this page. For a material change we will tell studio Owners by email before it takes effect. See also our Terms of Service.

Contact: Uriel Arnson LLC, [email protected].