Your wedding is yours.Here is what we hold, and why.

We collect:

• Account and wedding details — your email, partner names, wedding date and city, guest count, budget, and the style, traditions, and notes you share while planning.
• Guest and collaborator information you provide — names, emails, phone numbers, postal addresses, dietary, accessibility, and age-group notes (adult / child / infant), and RSVP responses. This is personal information about other people that you give us so we can help you plan (see “Information about your guests” below).
• Images and documents you upload or import — inspiration photos, engagement and gallery photos, and files such as contracts or floor plans. You may also import images from a URL, a public Instagram post, or a single Pinterest pin, or upload a screenshot of a Pinterest board; when you do, we fetch (or read) and store those images.
• Vendor outreach content — the inquiry messages you approve and the replies vendors send back, which pass through your workflows. While a workflow is in test mode, an approved draft is emailed to you — the person who approved it — instead of to the vendor, so you can see exactly what would go out; if we cannot resolve an address for you, that preview goes to a VowBloom-operated mailbox instead. When the managed reply address is enabled, vendor replies to your outreach are received at a VowBloomaddress and read by your concierge so it can show you what they said.
• Connected-account credentials — if you choose to connect Gmail, we store encrypted access tokens to send and sync your vendor threads. You can disconnect at any time.
• Technical information — a sign-in session cookie, a one-way keyed hash of your IP address (never the address itself) and your browser string when you accept our Terms, internal usage and cost logs that keep the service running within limits, and — only if you accept analytics cookies — which pages you visit and which features you use (never the contents of your plan).

We use this information to:

• operate the service — build your profile, match venues and vendors, organize your planning, and draft and send the outreach you approve;
• analyze your inspiration and preferences with AI so matches reflect your taste;
• secure the service, prevent abuse, and enforce our Terms; and
• comply with law and respond to legal requests.

Matching, style analysis, vendor descriptions, and email understanding are powered by AI providers (Anthropic’s Claude and Voyage AI for embeddings). To provide these features we send relevant content — for example, an inspiration photo, your wedding preferences, or the text of a vendor’s reply — to those providers to process and return a result.

The content we send to Anthropic through its commercial API is not used to train its models, and is retained only briefly to guard against misuse. For embeddings, we use Voyage AI with its training opt-out enabled, so the content we send is not used to train models and is deleted after it is processed for you.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We share information only with service providers that help us run VowBloom, and only as needed to provide the service:

• Supabase — authentication, database, and file storage.
• Anthropic — AI for style analysis, matching, vendor descriptions, and reading vendor replies.
• Voyage AI (a MongoDB company) — turns text and images into the embeddings used for matching.
• Google Places — vendor discovery, ratings, and reviews.
• Yelp — additional vendor discovery and reviews.
• Resend — delivering email (your outreach and our notifications).
• Google / Gmail — only if you connect your Gmail account, to send and sync vendor threads.
• Replicate — generating storyboard images and proposal video, where enabled.
• Unsplash — stock imagery (no personal information is sent).
• Vercel — hosting the site and keeping the request logs that run it.
• PostHog — product analytics. The browser script loads only after you accept analytics cookies; a small set of server-side product events is recorded either way (see “Cookies” below).
• Sentry — error reports when something breaks, where configured, so we can fix it; diagnostic details, not your plan.

When you import an image from a URL, Instagram, or Pinterest, we fetch it from that source at your direction. We may also disclose information if required by law, to enforce our Terms, or as part of a business transfer.

The guest and collaborator details in your account are personal information about other people that you choose to provide. You decide what to enter and what to share, and you are responsible for having the authority to give it to us. We process it on your behalf to help you plan your wedding — we do not use it to market to your guests. If one of your guests asks us to remove their information, we will work with you to honor that request.

VowBloom sets first-party cookies to run the service: a session cookie to keep you signed in, a short-lived cookie recording that you have agreed to the current version of these documents, and a small cookie that remembers the choice you make in our cookie banner.

Two more first-party cookies are set only if you arrive by a link that carries a referral or credit code — the “Planned with VowBloom” link on another couple’s guest pages, or a referral link a friend sent you. They store only that opaque code, for up to 90 days, so we can credit the person who sent you if you sign up. They are not readable by scripts, they are not shared, and they are not used for advertising.

We also offer one optional analytics cookie, set by PostHog, that helps us learn which parts of VowBloom help couples most. The PostHog script in your browser loads only after you choose “Accept analytics” in the banner — nothing is sent from your browser to PostHog before that, and choosing “Essential only” keeps it off. Separately from your browser, our servers record a small set of product events (for example, that an onboarding step finished, or that a proposal was viewed) so we can tell whether the product works; those carry no cookie, no browsing history, and no contents of your plan. We do not use advertising or cross-site tracking cookies.

To change your choice later, delete the cookie_consent cookie for this site in your browser’s settings; the banner will ask you again on your next visit.

We keep your information for as long as your account is active. When you delete your account, we remove your wedding, inspiration boards, uploaded photos and documents, guest list, and workflows, and we purge the associated files from storage. We may retain limited records for a reasonable period where we need to — for example, to honor a vendor’s unsubscribe request, to keep a record that you accepted these policies, to comply with law, or to resolve disputes. Your underlying sign-in record is deleted when you ask us to remove it, which keeps a clear trail for the request.

Depending on your state, you may have the right to access the personal information we hold about you, to correct or delete it, to obtain a portable copy, and to opt out of any “sale,” “sharing,” or targeted advertising. We do not sell or share your information or use it for targeted advertising, and we will not discriminate against you for exercising a right.

To make a request, email info@vowbloom.ai, or export your data or delete your account from your settings. You may use an authorized agent where the law allows. We will verify your request through your account email. The specific rights and any appeal process vary by state (for example, California, Colorado, Connecticut, Virginia, Texas, and Utah); tell us your state and we will apply the rights available to you.

VowBloom is intended for adults and is not directed to children under 18, and we do not knowingly collect personal information from children. The age-group field in an RSVP (adult / child / infant) is provided by an adult guest or by you for seating and meal planning — it is not collected from a child directly. If you believe a child has provided us information, contact us and we will delete it.

We encrypt data in transit and at rest, store any connected-account tokens encrypted, and limit access to what is needed to run the service. No method of transmission or storage is perfectly secure, so we cannot guarantee absolute security. We process and store information in the United States.

We will update this policy as the service evolves and revise the “Last updated” date above. Questions or requests? Email info@vowbloom.ai or write to [LEGAL ENTITY — form an LLC/corporation: prerequisite A-1], [COMPANY POSTAL ADDRESS].