On this page

1. The short version

We collect what we need to run the platform: account info, what you do on the site, and payment-processing details that flow through Stripe.
We share information with vendors when you book them, with payment processors so you can pay, with AI providers when you use AI features, and with no one else without your consent or a legal obligation.
We don't sell your personal information. We don't share it for cross-context behavioral advertising, except that if our team has configured Google Ads conversion tracking and you accept marketing cookies, a click identifier is shared with Google to measure ad performance — see Section 6.
You have rights, to access, correct, delete, or export your data. See section 8.

2. What we collect

Information you provide

Account info: name, email, password (hashed), phone (optional; see section 4 for AI-feature-specific consent), role (couple, vendor, guest, admin).
Profile content: for couples: partner names, wedding date, venue, guest count, budget, style preferences, color palette, photos. For vendors: business name, bio, portfolio photos, services offered, pricing, service area, team members.
Communications: messages between couples and vendors, comments on vendor profiles, day-of group chat messages, support tickets.
Finish-later link: if you ask us to email you a link to finish setting up later, we store your email address and your in-progress setup answers for up to 14 days, only to send you that link, and delete them when the link is used, when you create an account, or when the 14 days end.
Vendor invite links: if you create a vendor account after following another vendor's invite link, we store the referral code from that link with your new vendor account so we can credit the vendor who invited you.
Feedback: what you send us through the feedback form, including any screenshots you choose to attach when signed in; screenshots are stored privately, seen only by our team, and deleted after 180 days.
Booking + payment info: contracts, payment milestones, refund history, dispute filings, and vendor metered-usage records (electronic-signature sends, AI Receptionist minutes, AI feature usage). Payment card details are processed by Stripe; we do not store full card numbers on our servers.
Electronic-signature audit-trail information: for each contract or document you sign on the Platform, we capture the authenticated identity of the signer (account identifier, name, and email of record), the timestamp of acceptance in coordinated universal time (UTC), the IP address and user-agent of the accepting session, the exact text and version of the consent shown, the SHA-256 hash of the signed document, and the authentication method used. This audit trail is retained for the longer of seven (7) years or the duration of any applicable statute of limitations.
AI conversation content: what you type into the Vows Assistant or other AI features.
Voice content (AI Receptionist only): when a vendor enables the AI Receptionist feature and you call the vendor, the call is transcribed, and it is also recorded unless recording is switched off for that call. Recording is switched off for the whole call whenever all-party consent applies at either end of it (your state or the vendor's), whenever the vendor has turned recording off, and whenever you ask us not to keep a recording. The agent tells you at the start of the call which of the two you are on. See our separate disclosure at unitedvows.com/ai-receptionist-disclosure.
Voice answers (when you choose to speak instead of type): where the Platform offers a microphone button, for example when answering the setup questions as you join, your recording is sent to one of our AI providers (currently OpenAI) to be transcribed into text, and we use that text exactly as if you had typed it. For the setup questions, United Vows does not store the recording: we hold it only for the moment it takes to transcribe. The provider receives the recording to transcribe it and may keep it for a limited time under its own terms, for example for abuse monitoring. Typing instead is always available.

Information collected automatically

Device and browser information (user agent, screen size, locale).
IP address and approximate location derived from it.
Cookies and similar technologies (see our Cookies Policy at unitedvows.com/cookies).
Usage events: pages viewed, features used, search queries, click paths.

Information from third parties

For vendors: when we import publicly available business info (Google Business Profile, etc.) to seed unclaimed listings, we attribute the source and offer a clear claim flow.
For OAuth signins: we receive the basic profile (name, email, profile photo) from the provider you used.

Google Calendar (vendors who connect it)

If you are a vendor and connect Google Calendar, United Vows asks Google for two permissions and nothing more: to see your busy/free times, and to create one separate calendar named "United Vows" and manage the events in it. We cannot see, change or delete anything else in your Google Calendar.

What we read. Busy/free time blocks from your main Google calendar, and nothing else: when you are busy, never the title, description, location, guests or any other detail of an event. We read them at the moment we work out which times to offer, for example when a couple opens your consultation booking page, or when we check that a requested consultation time is still free. We use them only so that nobody is offered a time you are already busy, and we do not store them.
What we write, and where. Only to the "United Vows" calendar we create in your Google account, never to your main calendar, and only bookings that exist on United Vows: a wedding once its contract is fully signed (a title with the couple's names, the date and the ceremony time they gave, and a link to the contract), dates you block on your United Vows calendar (marked unavailable, with your note if you added one), and consultations couples book with you (a title with the name they gave, the time, and the email address, phone number and wedding date they gave). For a consultation, the couple's email address is also added as a guest on the event, and Google may email them about it under its own settings. When a booking changes or is cancelled, or you unblock a date, we update or remove the event.
What we store. Your Google access and refresh tokens (which let us do the above), the ID of the "United Vows" calendar, and, for each event we create, its Google event ID together with the booking it belongs to, its title and its start and end time. We keep these only while Google Calendar is connected. We delete them when you disconnect, when you ask us to delete your account (at the moment you confirm, not at the end of the grace period in Section 7), and when Google tells us you have removed our access.
What we never do. We never send Google Calendar data, including your busy/free times, to any AI model, the AI Receptionist included, and we never use it to train or improve any AI or machine-learning model. We never use it for advertising, never sell it, and never transfer it to anyone except as needed to provide this calendar feature, for security, or to comply with the law. People at United Vows do not read it unless you ask us to, it is needed for security, or the law requires it.
Disconnecting. Use Disconnect in your calendar settings. We then delete the "United Vows" calendar, and the events we put in it, from your Google account, revoke our access with Google, and delete the tokens and records described above. Your bookings stay on United Vows. You can also remove our access at any time at myaccount.google.com/permissions. If you do it there, we can no longer reach the "United Vows" calendar to remove it, so delete it yourself in Google Calendar if you no longer want it; we delete the stored tokens and records the next time we find our access has ended.
Earlier connections. Before we narrowed these permissions in October 2026, connecting Google Calendar gave United Vows wider access (to see your calendars and edit their events) and we added bookings to your main calendar. If you connected then, we ask you to reconnect, and until you do we add nothing new to your Google Calendar and read only busy/free times. When you reconnect or disconnect, we first delete the events we added to your main calendar (only the ones we created, which we recorded), then revoke the old access.
Google's Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Guest information provided by couples. Couples may add information about their wedding guests — names, contact details, RSVP status, and any dietary or accessibility notes a guest shares — to run their guest list, seating, RSVP, and check-in tools. If you are a wedding guest, this information was provided by the couple who invited you (or by you, through their RSVP or guestbook forms); we process it only to operate the couple’s wedding tools, we do not use it for marketing to you, and we delete it with the couple’s account. Photos or notes you choose to share on a couple’s wedding site are shown only after the couple approves them, and you can ask the couple (or us at privacy@unitedvows.com) to remove them.

3. How we use it

To run the platform, show you relevant vendors, process payments, route messages.
To make AI features work, process your inputs through AI providers and return results.
To improve the platform, measure feature usage, debug issues. We do not train internal models on identifiable user content. Aggregate, non-identifying analytics may be derived from usage events.
To communicate with you, transactional emails (booking confirmations, payment receipts), service announcements, and (with your consent) marketing.
To prevent fraud and enforce our Terms.
To comply with legal obligations (including tax records retention).

4. AI features and your data

United Vows uses AI models from OpenAI, Anthropic, and Google to power the Vows Assistant, the Instant Profile Builder, AI-assisted vendor matching, AI-generated proposals, the AI Receptionist (vendor feature), the vendor Coach, Insights, and other features. When you use one of these features:

To provide these personalized features, we send only the information a given request needs (messages, profile fields you ask AI to rewrite, voice answers you choose to speak so they can be transcribed, transcripts of AI Receptionist calls) to the AI service provider, who processes it to return a response.
We use this processing only to provide and personalize the service — for example recommendations, planning help, and tips. We do not sell your information or share it with anyone else, except as needed to operate the service as described in this policy, or when the law requires it (for example, a valid court order).
We retain a copy of AI conversations for up to 90 days for service quality, debugging, and abuse-detection. A daily job then deletes the conversation content itself — what you sent and what came back. What survives is the operational record of the run: which model answered, how many tokens it used, what it cost, how long it took, and whether you accepted the suggestion. That record is what we need to run and pay for the feature, and it no longer contains anything you wrote.
AI outputs are suggestions, not advice. Don't rely on them for legal, medical, financial, tax, insurance, employment, immigration, or any other professional decision without independent verification.

What we learn about you, and how. As you use United Vows — during onboarding, in conversations with the Vows Assistant, and as you save vendors or set a budget — we build a profile of what you have told us, so the product can be specific to your wedding rather than generic. Every entry in that profile records the input it came from: the answer you gave, or a quote from the message you wrote. We do not add anything to it that you did not tell us, and where a signal is weak we treat it as a question to ask rather than a fact about you. You can read this profile yourself at any time in your privacy settings: every entry, what we drew it from, how much weight we currently give it, and whether we are still using it at all. You can remove any entry there, and put it back if you change your mind. It is included in your data export too. If you would rather we did it for you, email privacy@unitedvows.com.

Accessibility, dietary, faith and health details — your explicit choice. Some of what matters most about a wedding is personal: a step-free venue, a kosher or halal caterer, an allergy a kitchen has to know about. Laws in the UK, EU and several US states treat these as special-category or sensitive information, and we treat them that way too.

We use them only if you explicitly turn this on. It is a separate, opt-in choice, never bundled into accepting our Terms, never pre-ticked, and never a condition of using United Vows. Everything else works the same whether you turn it on or not.
What we do with them. We make them available to the Vows Assistant, so that when you ask it something the answer is about your wedding rather than a generic one. That is the whole of it. We do not disclose these details to vendors, and we do not use them to search for, rank, match, or recommend vendors to you.
You choose what for. There is one purpose, and it is the one printed on the checkbox: letting the Vows Assistant take these details into account when it answers you. Nothing else in United Vows reads them. If we ever build a second use for them, it gets its own separate checkbox and its own wording — we will not quietly widen this one.
We never guess them. These details are only ever recorded where you typed them into a field that said what it was for. We do not infer your faith, health, or disability from anything else you say or do.
We never use them to set prices, and we never sell them or share them for advertising.
You can withdraw at any time, in your privacy settings, by clearing that one checkbox. We stop using them immediately. You can still see what we hold after withdrawing, because being unable to look at something is not the same as us not using it. If we change the wording of what you agreed to, we ask you again rather than carrying your old answer across to new words — so the box may come back unticked after an update, and we say why when it does.
You can also permanently erase an individual entry. Withdrawing consent stops us using everything in this category; the "Delete permanently" control next to any single accessibility, dietary, faith, or health entry in your privacy settings goes further and erases that entry's content outright, keeping only a dated record that something was once entered there. This is irreversible.

Your guests' details are not part of this. When a wedding guest tells you about an allergy or an access need through an RSVP form, that information is used to run your wedding — telling your caterer, your venue, your seating plan — and nothing else. It never becomes part of any profile, yours or theirs, and it is never used for recommendations or marketing. Your guests did not sign up for United Vows, and we do not treat them as if they had.

Phone number, listing-claim texts and AI Receptionist consent. If you provide your phone number to United Vows (couple settings or vendor profile), you consent to its use for: inbound caller-matching by the AI Receptionist when you call a vendor that has enabled the feature, and outbound callbacks only when you affirmatively request one. We send exactly one kind of text message: a one-time code that proves you manage a business listing you are claiming. It goes only to the phone number already on that listing, never to a number typed in, and only when you choose the text option on the claim page; email is the default way to claim a listing. We do not text couples, guests or account holders, and account confirmation and sign-in codes are sent by email only. We never send marketing, reminders or other notifications by text. Message and data rates may apply. To prevent abuse and cap our spending, we keep a record of each claim text that holds a one-way hash of the number (never the number itself), its area code and exchange, and a one-way hash of the requesting IP address; those records are deleted after 30 days. Our text-message provider receives the listing's number and the code in order to deliver and check it. The AI Receptionist is voice-only and does not text callers, and we do not place outbound marketing calls. If we ever enable any other outbound text messaging, we will obtain the prior express written consent required by the federal TCPA and applicable state laws first. See section 6 (sub-processors).

5. Cross-vendor features and shared data

Some features intentionally share information between vendors and couples on the same wedding. Specifically:

Vendor recommendations: when a vendor recommends another vendor, that endorsement is publicly visible on both vendor profiles.
Vendor-to-vendor rental records and damage claims (only if and when the vendor marketplace is available to you): if and when this feature is available to you, when a vendor records an issue about a rental with another vendor, or files a damage claim against a rental deposit, what they submit (the description, any amount and any photos) and the other vendor's answer are shown to both vendors and kept as a record of that rental, which United Vows provides to either of them on request. United Vows does not use these records to decide who is right.
Shared wedding-day timelines: all confirmed vendors on a wedding can view the couple's timeline. Each vendor's notes on the timeline are visible to the couple and the other confirmed vendors.
Day-of group chat: when 2+ vendors are confirmed on a wedding, an automatic shared chat thread is created with the couple and every confirmed vendor. Messages in this thread are visible to all participants.
Vendor Exchange, Sell lane (only if and when this feature is available to you): if and when this feature is available to you, when a vendor lists inventory for sale to other vendors, its listing (item, condition, photos, price) will be visible to other vendors browsing the marketplace. When another vendor buys it, the buyer's business name and, if the buyer chooses shipping, the shipping recipient name and mailing address would be shared with the seller so the item can be delivered; the seller's tracking information would be shared with the buyer. Each vendor could use this information only to complete that sale.
Vendor Exchange Services lane (a couple's files shared with a second vendor; only if and when this feature is available to you): if and when this feature is available to you, when a vendor orders a remote task from another vendor through the Vendor Exchange (for example photo or video editing, colour grading, audio mixing, design, or calligraphy), the ordering vendor may upload a couple's files (such as photos, video, audio, or documents from their wedding) so the provider can complete the task. The provider may use those files only to complete the task, must keep them confidential and reasonably secure, must not use them to train or improve any machine-learning or AI model, and must not share them with anyone else. Those files would be deleted within 30 days after the task is complete. The ordering vendor is responsible for having the right to share a couple's files with a provider this way, as described in the terms that will apply to that feature.
Crew worker profiles and contact reveal (Vendor Exchange; only if and when this feature is available to you): if and when this feature is available to you, a vendor searching for crew will be able to see a worker's name, photo, roles, experience, portfolio, languages, general work area, reviews, and whether a licence for a regulated role is on file and when we last reviewed it, but not the worker's contact details (email, phone). A worker will be able to see the same kind of information about a hiring vendor. Contact details on either side would be shared only after both the vendor and the worker agree to connect for a shift; that reveal is recorded. After a shift, the vendor and the worker can each leave the other a review, visible on both profiles. United Vows does not process payment for Crew and does not receive or store any payment information between a vendor and a worker.
Subcontractors (Vendor Exchange; only if and when this feature is available to you): if and when this feature is available, and a vendor you booked brings in another vendor through the Vendor Exchange to deliver part of your booking (a subcontractor), we would share with that subcontractor only what it needs for that part of the work: your event date, where the work happens, and the booked vendor's description and notes for the task. We would not give the subcontractor your contact details; the vendor you booked would stay your contact and remain responsible to you for your whole contract. Before the event we would tell you, in the app and by email, the subcontractor's business name and the part of the job it will provide, and we would keep a record of that notice (its wording, version and date). The subcontractor could use your details only for that work, under the terms that will apply to that feature.

Don't share sensitive information (passwords, financial account numbers, government IDs, health data) in these shared surfaces.

Vendor handoffs (Vendor Exchange; only if and when this feature is available to you). If and when this feature is available to you, a vendor who cannot take your enquiry may recommend another vendor through United Vows. Before you agree, the other vendor would see only a summary that does not identify you (for example the service, the date, the general area and a budget range). We would ask you first, in the app and by email, and share your name, contact details, wedding date, venue and your message to the first vendor with the recommended vendor only if you say yes. Saying no would cost you nothing and share nothing, and an unanswered request would lapse after 14 days with nothing shared. We would keep a record of your answer, the wording you agreed to and when, for as long as we keep the handoff record. If you book the recommended vendor, the first vendor may receive a referral fee from them; you would never pay more because of it. The first vendor could not use the handoff to market to you for 12 months.

Wedding Requests. When you post a wedding request (a description of a service you need, so that matching businesses can reply):

What businesses see. We check each request before it is shared. Businesses on United Vows that match it see the request as it appears on your review screen: the service, the area, the date or season, a budget range, and what you wrote, with phone numbers, email addresses and links removed. They do not see your name, email, phone number or address unless you choose to share them with a business. Anything else you type into the request is shown as you wrote it, so leave out your name and address.
Businesses not yet on United Vows. If the box on the review screen is ticked, we may also email matching businesses that have not joined United Vows a short summary, at the address on their public business listing. The summary contains only the service, the market area, the month or season, a budget range and a few preset style tags. It never includes your own words, your name, your exact date, a venue or contact details. Those businesses are not bound by our terms. The box starts unticked for visitors in the European Economic Area, the United Kingdom and Switzerland, and when we cannot tell which country you are in. You can switch this off later on your request page; summaries already sent cannot be taken back.
Public summary, only if you choose it. Where the option is offered and you choose it, a short summary with the same kind of details (never your name, your words or your contact details) is listed publicly. We ask search engines not to index it, but copies other people make cannot be taken back.
Your account. Confirming your email with a code creates a simple United Vows account for that email address, with no password, so you can come back to your requests. We do not send it our welcome or tips emails; those start only if you later finish setting up a full account, and you can unsubscribe from them at any time.

6. Sub-processors and recipients

We use the following sub-processors to operate the platform. Each is bound by data-protection terms in their service agreements with us:

Stripe: payments and Stripe Connect payouts.
Electronic-signature service provider: the Platform uses one or more electronic-signature services to administer signing of contracts and the Platform Addendum. We are provider-agnostic and may change the underlying service at any time. The current service is identified in our sub-processor list maintained at unitedvows.com/sub-processors. The provider receives the document, the signer's name and email, and the audit-trail data necessary to produce the signed record.
Vapi: voice / AI Receptionist runtime (voice only; it does not send text messages).
OpenAI, Anthropic, Google: AI inference for assistant, matching, and analysis features, and (OpenAI) transcription of voice answers. No Google Calendar data is sent for AI inference.
Google (Google Calendar): for vendors who connect Google Calendar, Google receives the booking details we add to the separate "United Vows" calendar in the vendor's own Google account (event details and attendee email addresses), and returns the vendor's busy/free times. See "Google Calendar" in Section 2.
Twilio (Twilio Verify): only for claiming a business listing, when text verification is switched on: delivery and checking of a one-time code texted to the phone number on that listing. Receives that phone number and the code.
Microsoft: Outlook Calendar synchronisation for vendors who connect it, receiving event details and attendee email addresses.
Resend: transactional email delivery.
Neon: database hosting.
Vercel: application hosting, and a cookieless page-view and referrer count (Vercel Web Analytics; see our Cookies Policy, section 2.3).
Upstash: cache / rate-limit storage.
Sentry: error monitoring (stack traces and request metadata; configured to redact PII).
PostHog: product analytics (aggregated, anonymous-where-possible). Before you accept analytics cookies, only an anonymous count of the visit, the pages and steps it reached, and the country and US state derived from the request is kept (nothing you type into a form is included, and the IP address is not stored), with no cookie and nothing stored on your device (see our Cookies Policy, section 2.3). If you are in the EEA, the United Kingdom or Switzerland, or we cannot tell where you are, we do not count your visit at all until you accept analytics cookies. If you accept analytics cookies, PostHog also records your session on our sign-up pages only (what the page shows and how you move through it), with everything you type masked, text in form fields masked, and no network contents captured; it never runs without that consent (see the Cookies Policy, section 2.3). A Do Not Track or Global Privacy Control signal, or the account-wide opt-out, stops even that.
Google Analytics (Google LLC): when configured, aggregated site-usage measurement, receiving page views, approximate location, and device/browser information. Loaded only after you accept analytics cookies (see our Cookies Policy at unitedvows.com/cookies).
Google Ads (Google LLC): when our team has configured a Google Ads account, conversion-tracking to measure whether an ad you clicked led to a signup. Loaded only after you accept marketing cookies. We do not use this to build an advertising profile of you or to show you ads elsewhere. Accepting marketing cookies while this is configured may constitute "sharing" of personal information for cross-context behavioral advertising under California law — see Section 8 for how to opt out, which fully blocks it.

We share information with the following non-sub-processor recipients:

Vendors you contact or book. Your contact info, wedding details, and messages reach the vendor when you inquire. If the business has not joined United Vows yet, we may instead email it a short version of your inquiry at the address on its public business listing: your first name and last initial, wedding date and area, budget range, guest count, and up to 200 characters of your message with any contact details removed. That business is not bound by our terms, and it cannot reply to you or see your contact details unless it claims its listing on United Vows.
Other confirmed vendors on your wedding. See section 5 (cross-vendor features).
Legal & safety: we'll disclose information when required by law, to enforce our Terms, to investigate fraud, or to protect rights, property, or safety.
In a sale of the company: if United Vows is acquired or merged, personal information may transfer to the new entity. We'll notify you in advance.

We don't sell or rent personal information to third parties for their own marketing. We don't otherwise share personal information for cross-context behavioral advertising as those terms are defined under California law, other than the Google Ads conversion-tracking sharing described above, which happens only if our team has configured it and only if you accept marketing cookies.

7. Data retention

Active accounts: as long as you have an account.
Closed accounts: we retain core records (account, contracts, payment history) for up to 7 years for tax (IRS retention requirements), dispute-resolution, and legal-obligation purposes; the rest is deleted within 90 days of account closure. The 7-year retention is necessary for compliance with federal tax law and the platform's defense in any subsequent claim under state contract or consumer-protection statutes. Concretely: when you confirm deletion your account is closed immediately — you are signed out and a vendor listing comes off the marketplace — and a daily job erases the account 30 days later. If any of those 7-year records exist, that automatic erase would take them (and, for a vendor, couples' reviews and a couple's own copy of a shared contract) with it, so we stop it and tell you at the time to email privacy@unitedvows.com; a person then removes everything we are allowed to remove and keeps only what this section requires.
AI conversation logs: 90 days. A daily job then deletes the conversation content and keeps only the operational record of the run (model, tokens, cost, latency, whether you accepted the suggestion).
Wedding-site content: kept until you delete the wedding site or close your account.
Google Calendar connection (vendors): tokens, the "United Vows" calendar ID and our records of the events we created are kept only while Google Calendar is connected, and deleted as described under "Google Calendar" in Section 2. Busy/free times are not stored.
AI Receptionist call recordings: 13 months, deleted by the same daily job — both our link to the recording and the recording itself at our voice provider. A recording you asked us not to keep, or one from a call where all-party consent applied, is discarded when the call ends rather than waiting for the 13 months. Call transcripts: 7 years. Opt-out records: indefinite (retained to honor your opt-out).

8. Your rights

Depending on your location you may have the following rights. Several are self-serve in your privacy settings: reading and removing entries in the profile we have inferred about you, downloading your data, your communication and sharing choices, and deleting your account. To have an entry corrected rather than removed, email privacy@unitedvows.com, and for anything else:

Access: request a copy of the personal information we hold.
Correction: have inaccurate data corrected.
Deletion: request deletion of your personal information (with legal-retention exceptions described in Section 7).
Portability: receive your data in a machine-readable format.
Opt-out of marketing: unsubscribe from any marketing email; transactional emails will continue while your account is active.
Object to processing: object to certain processing, including automated decision-making.
Opt-out of sharing for cross-context behavioral advertising: rejecting marketing cookies in the cookie banner or the cookie preference center fully blocks the one form of this sharing we support (Google Ads conversion tracking, Section 6), if and when our team has configured it. To confirm current status in writing, see Section 8 (California).

We honor browser-level Do Not Track (DNT) and Global Privacy Control (GPC) signals as requests to opt out of any non-necessary tracking. Our cookie banner reflects these signals when set.

If you're in the EU/EEA/UK (GDPR): you also have the right to lodge a complaint with your local supervisory authority. We process data on lawful bases including contract performance, legitimate interests (platform operations, fraud prevention), consent (marketing, optional features), and legal obligation.

If you're in California (CCPA/CPRA): see your rights to know, delete, correct, and opt-out. To opt out of sharing (see Section 6 — this only applies if our team has configured Google Ads conversion tracking), reject marketing cookies in the cookie preference center, email privacy@unitedvows.com, or use the privacy preferences page at unitedvows.com/privacy-preferences.

9. Children

United Vows is intended for users 18 and older. We do not knowingly collect personal information from anyone under 18. In particular, we do not knowingly collect personal information from children under 13 in compliance with the Children's Online Privacy Protection Act (COPPA). If you believe a minor has created an account, email privacy@unitedvows.com and we'll delete the account and associated personal information promptly.

10. International transfers

Our servers are in the United States. If you're using United Vows from outside the US, your information will be transferred to and processed in the US. For users in the EU/EEA/UK, we are in the process of implementing Standard Contractual Clauses and supplementary measures to safeguard cross-border transfers. If you have specific questions about international transfer mechanisms, email privacy@unitedvows.com.

11. Security

We use TLS 1.3 in transit, encrypted storage at rest, role-based access controls, rate limiting on public endpoints, audit logs on sensitive actions, and structured incident-response procedures. No system is perfectly secure, if you suspect a security issue, email security@unitedvows.com.

12. Changes to this policy

We may update this Privacy Policy from time to time. We will give you reasonable advance notice of any material change, by email or in the app, and publish every change on this page. For a change that reduces your rights, we will give at least 7 days' notice before it applies to you. Changes that are required by law, that address security or fraud, or that only benefit you may take effect immediately. Where the law requires your consent for a change, such as using personal information we already hold for a new purpose, we will ask for your consent and will not apply that change to you without it.

13. Contact

Privacy questions: privacy@unitedvows.com. Security disclosures: security@unitedvows.com. General inquiries: support@unitedvows.com.