Privacy Policy
Effective October 25, 2026
Who this covers
This policy explains how Big I Do (“Big I Do,” “we,” “us”) handles information in the Big I Do website at bigidoapp.com and the Big I Do apps: the studio app used by wedding businesses (“studios”), the couple app used by their clients, the crew app used by their team, and the galleries, proposals, forms and booking pages a studio shares. A studio decides what it collects about its own clients and is responsible to them for it; we process that information on the studio's behalf.
What we collect
- Account details: the name, email address and phone number of the people who use a studio's account, and their role in the studio.
- Studio records: what a studio enters or imports, such as couples and their contact details, wedding dates and places, proposals, contracts and signatures, invoices and payments, questionnaires, timelines, floor plans, messages, notes, tasks, expenses and mileage.
- Photographs and files a studio uploads to galleries or to a couple's files.
- Payment information: payments are processed by Stripe. We receive the result of a payment (amount, date, status and the last four digits of a card), never the full card number.
- Usage and device information: sign-in times, pages used, and basic technical information such as browser type and IP address, used to keep the service working and secure.
- Information from connected accounts, only when a studio chooses to connect them, as described below.
How we use it
We use information only to provide, secure and support the service a studio asks for: showing its records, sending the emails, texts and reminders it sets up, taking its clients' payments, building its timelines and galleries, keeping its calendar in step, and answering its support requests. We do not sell personal information, we do not share it for others' advertising, and we do not use it to build advertising profiles.
Google account data
A studio can connect its own Google account in Settings so that its emails to couples go out from its own Gmail address and its weddings, sessions and consults appear on its own Google Calendar. When it does, Google asks the studio to allow the following, and we use each only for the purpose shown:
| Permission | What we use it for |
|---|---|
openid, email | To know which Google account was connected and show its address in Settings. |
gmail.send | To send the emails the studio writes or sets up (such as replies, reminders and payment notices) from its own Gmail address. We do not read the studio's mailbox with this permission. |
calendar.events | To add the studio's weddings, sessions and consults to the calendar it picks, keep them up to date and remove them when they are canceled, and to read busy times so its booking page does not offer times it is already taken. |
calendar.calendarlist.readonly | To list the studio's calendars so it can pick which one to use. |
If Google later approves it and the studio turns it on, the gmail.readonly permission is used only to bring a couple's replies to the studio's emails into that couple's message thread in Big I Do, matched to the email the studio sent. Other mail is not stored.
Big I Do's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, we do not let people read it except with the studio's permission, for security, or to comply with the law, and we do not use it to train artificial-intelligence models.
Microsoft account data
A studio can connect its own Microsoft account (Outlook or Office 365) for the same reasons. Microsoft asks the studio to allow User.Read (to know which account was connected), Mail.Send (to send the studio's emails from its own address), Mail.Read (only to bring couples' replies to those emails into their message thread), Calendars.ReadWrite (to keep its weddings, sessions and consults on its calendar and read its busy times) and offline_access (to keep the connection working without signing in again). We use this data under the same limits as Google data above.
Connected accounts: storage and disconnecting
The sign-in tokens for a connected Google or Microsoft account are encrypted (AES-256) before they are stored and are used only by the service itself. A studio can disconnect either account at any time in Settings; we then delete its tokens, and for Google we also ask Google to revoke them. A studio can also remove our access from its Google or Microsoft account settings at any time.
Artificial intelligence
Some features use artificial intelligence: the voice and text assistant, “Write it for me,” smart import and gallery sorting. To run them, the text, files or photos involved are sent to our AI provider, Anthropic, under terms that do not allow it to train its models on that data. Google and Microsoft user data is never used to train AI models.
Who else handles data
We use service providers to run Big I Do, each only for its part of the service: Cloudflare (hosting, databases and file storage), Stripe (payments and subscriptions), Twilio (text messages and calls), our email delivery provider, Anthropic (AI features), and, when a studio connects them, Google, Microsoft, QuickBooks, and Claude or ChatGPT. We may also disclose information when the law requires it, to protect people's safety, or as part of a sale or merger of the business, in which case this policy continues to apply.
Keeping and deleting data
We keep a studio's records while its account is open. A studio can export its couples and payments at any time and can delete records in the app. When a studio closes its account, it can ask us to delete its records and we will, except what we must keep for tax, accounting or legal reasons. Couples and crew members can ask the studio, or us at hello@bigidoapp.com, to see, correct or delete their information.
Security
All traffic is encrypted in transit. Each studio's records are kept in its own database, staff accounts sign in with personal codes, and roles limit what each person can see. No system is perfectly secure; if we learn of a breach affecting your information, we will tell you as the law requires.
Children
Big I Do is a business tool and is not directed to children under 13. We do not knowingly collect their information.
Changes and contact
We may update this policy; the effective date above will change, and we will tell studios about material changes. Questions or requests: hello@bigidoapp.com.