Skip to main content

WedBegin Legal

Privacy Policy

This Policy explains what WedBegin collects, why it is used, when it is disclosed, and the choices available to couples, vendors, guests, contributors, planners, and visitors.

Effective: August 16, 2026Version: 2026-08-16

1. Scope and our role

This Privacy Policy applies to WedBegin websites, applications, public pages, communications, and services that link to it (collectively, the “Platform”). “WedBegin,” “we,” “us,” and “our” refer to WedBegin, LLC, a Connecticut limited liability company and the operator of the Platform. For privacy-law purposes, WedBegin, LLC is the controller of personal information it decides how and why to process.

The Platform is a wedding marketplace and planning service. It allows couples and wedding professionals to create accounts and profiles, discover and bundle services, communicate, sign contracts, schedule calls, process purchases and payouts, use planning and RSVP tools, participate in community features, publish content, and use closed-loop WedBegin Bucks. Some public pages can be used by people without accounts, including wedding guests, gift contributors, event attendees, and visitors.

This Policy does not govern a vendor’s independent collection or use of information. Vendors are separate businesses and are responsible for their own privacy practices. A vendor’s contract or privacy notice may apply in addition to this Policy.

2. Information we collect

Depending on how you use the Platform, we collect the following categories:

  • Account and identity information: name, email address, account identifier, account type, authentication status, and records of acceptance of legal documents. A consent receipt may include server time, IP address, and browser user agent.
  • Couple and wedding information: partner names, wedding date, city, state, venue details, budget, itinerary, planning tasks, saved vendors and bundles, preferences, profile biography, photos, wedding website content, registries, and RSVP settings.
  • Vendor and professional information: business name, service categories, biography, city and state, contact information, website, pricing, packages, service area, availability, portfolio media, team information, compliance documents, insurance or licensing information when submitted, subscription tier, referral information, and public profile settings.
  • Guest, event, and third-party information: names, contact details, household or party information, attendance, meal selections, accessibility or dietary responses, plus-one details, custom-question responses, seating assignments, event registrations, and invitations. Couples and organizers are responsible for having authority to provide this information.
  • Transaction and commercial information: products or services viewed, carts, orders, bookings, contracts, invoices, deposits, refunds, disputes, subscriptions, fees, vendor payout status, Stripe account identifiers, wallet balances, gift-contribution details, and transaction history. WedBegin does not intend to store full payment-card numbers; Stripe processes card details.
  • Communications, safety requests, and content: direct and group messages, support requests, nonconsensual-intimate-image removal requests (including requester contact details, content locations, authority, affirmation, signature, request evidence, and status), reviews, comments, posts, polls, attachments, contracts, signatures, uploaded images and videos, contributor messages, and other material you submit.
  • Calendar and integration information: connection status, calendar event or free/busy information requested through an enabled integration, Google Place IDs, imported or embedded review information, and information returned by services you connect.
  • Usage, device, and network information: page paths visited without query strings or fragments, a referrer origin and path without query strings, an anonymous session identifier, mobile or desktop classification, timestamps, interactions, browser and device information, IP address in server logs or consent records, and diagnostic or security events.
  • Approximate location: city and state that you provide and location inferred at a general level from an IP address. The current Platform does not require precise geolocation.
  • Inferences and generated information: recommendations, quiz outcomes, planning suggestions, moderation indicators, and AI-generated drafts or content based on information supplied to a feature.

Please do not submit Social Security numbers, government identification numbers, full financial-account credentials, health records, or other highly sensitive information unless a specific feature clearly requests it and explains why. RSVP custom fields can reveal dietary, accessibility, religious, or other sensitive information; use them only when necessary and with appropriate notice to guests.

3. Sources of information

  • Directly from you when you register, create a profile, make a purchase, upload content, connect an integration, communicate, or use a tool.
  • From other Platform users, such as when a couple enters guest details, a vendor adds a team member, a planner adds participants, or someone sends you a message or invitation.
  • Automatically from your browser, device, and interactions with the Platform.
  • From payment processors, connected services, public sources, referral links, and service providers that help operate the Platform.
  • From public pages or third-party services you direct us to display, such as a public website, Google business listing, YouTube video, or Vimeo video.

4. How we use information

We use personal information to:

  • create, authenticate, secure, personalize, and administer accounts;
  • provide marketplace search, profiles, bundles, bookings, contracts, scheduling, messaging, community, shop, event, planning, RSVP, registry, and wallet functionality;
  • process payments, subscriptions, platform fees, refunds, disputes, contributions, vendor payouts, and accounting records through Stripe and other providers;
  • display information to the audience selected by the user, including public profiles, wedding websites, posts, reviews, listings, and shared links;
  • send service messages, receipts, account notices, invitations, support responses, and, where permitted, marketing communications;
  • provide recommendations, AI-assisted drafts, quizzes, analytics, and feature improvements;
  • detect spam, fraud, security incidents, abuse, prohibited content, payment risk, and violations of our Terms;
  • moderate content, investigate complaints, enforce agreements, resolve disputes, and protect users and the public;
  • comply with law, tax, payment, recordkeeping, litigation, and regulatory obligations; and
  • evaluate or complete a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets.

5. How we disclose information

We disclose information only as reasonably related to operating the Platform, at your direction, or as otherwise described here:

  • Other users and the public. Profiles, listings, portfolios, pricing, availability, reviews, posts, comments, public wedding pages, RSVP content, and other information may be visible according to the feature and your settings. Messages, booking details, guest details, contracts, and transaction information are shared with the participants needed to provide the requested service.
  • Vendors, planners, buyers, sellers, and event organizers. We provide information needed to quote, schedule, contract, fulfill, support, or dispute a transaction or event.
  • Service providers. We use providers for platform hosting and identity, cloud storage and content delivery, payment processing, email and notifications, analytics, customer support, security, media processing, calendar connections, maps and embedded content, and AI processing. They receive information needed to perform services for us.
  • Payment and financial partners. Stripe and connected-account participants receive transaction, identity, tax, fraud-prevention, payout, and account information required to process payments and comply with financial rules.
  • Legal and safety recipients. We may disclose information to comply with law or legal process; respond to government requests; investigate fraud, abuse, safety threats, intellectual-property complaints, or security incidents; enforce agreements; and protect rights, property, or safety.
  • Business transactions. Information may be disclosed to advisers, counterparties, and successors in connection with a corporate transaction, subject to appropriate confidentiality protections where applicable.
  • With your direction or consent. We disclose information when you connect a service, publish content, invite another person, share a link, or otherwise direct us to do so.

We do not knowingly sell personal information for money. Based on the current Platform design, we do not disclose personal information for cross-context behavioral advertising as “sharing” is defined by California law. If those practices change, this Policy and required opt-out methods must be updated before the change is activated.

6. Public and user-directed sharing

Information on a public vendor profile, public couple profile, public wedding or RSVP page, public marketplace listing, community post, review, blog comment, event page, or shared link can be seen, copied, indexed, or reshared by others. Privacy settings limit Platform access but cannot control copies already made by recipients or search engines. Do not publish information that you or another person expects to remain private.

If you provide information about another person, including a partner, guest, customer, team member, or participant, you represent that you are authorized to provide it and to direct the Platform to use it as requested.

7. Payments and WedBegin Bucks

Stripe processes payment-card information and certain vendor onboarding and payout information under Stripe’s own privacy terms. WedBegin receives transaction confirmations, identifiers, amounts, fee information, status, disputes, and limited customer details needed to administer the transaction.

WedBegin Bucks is implemented as a closed-loop platform credit. The Platform records a couple’s balance, reservations, deposits, purchases, refunds, contributors, associated Stripe identifiers, and fees. Contributors provide a name and email for receipts and may provide a message. WedBegin Bucks is not a bank account, does not earn interest, is not eligible for cash withdrawal, and is intended only for eligible Platform purchases, subject to the separate terms shown for the program and applicable law.

8. AI-assisted features

Certain features use third-party artificial-intelligence services, including Google Gemini, to generate drafts, recommendations, polls, posts, quizzes, or other content. Information included in a prompt or feature context may be sent to the applicable AI provider for processing. Do not submit confidential, privileged, regulated, or highly sensitive personal information to an AI feature. AI output can be inaccurate or inappropriate and must be reviewed by a person before reliance or publication.

9. Cookies, analytics, and embeds

The Platform uses necessary browser storage for authentication, security, session continuity, interface preferences, referral attribution, and login presentation. Optional first-party analytics is disabled until you choose to enable it. If enabled, analytics records a sanitized page path, a referrer origin and path without query strings, an anonymous session identifier, device class, and event metadata limited in size and structure. The server derives an authenticated email itself when one is available and does not accept a client-supplied identity.

Optional external media—including Google Maps or reviews, YouTube, Vimeo, and administrator-provided embeds—is blocked until you enable the external-media category or ask to load the content. Those providers may receive device, network, and interaction information when loaded and may use cookies under their own policies. The Platform does not load the previously global Stripe pricing-table script; payment pages may still connect to Stripe when you start or use a payment feature.

You can use the persistent “Privacy Choices” control in the footer to allow, reject, or later withdraw optional categories. A detected Global Privacy Control signal is recorded in the local choice and optional categories remain off unless you affirmatively enable them. The Platform does not currently respond to the separate browser “Do Not Track” signal. Because the current design does not sell personal information or use it for cross-context behavioral advertising, no sale or targeted-advertising opt-out is currently necessary; we will add and honor legally required opt-outs before activating a covered practice.

10. Retention

We retain information for as long as reasonably necessary for the purpose collected, including to provide an active account or feature, complete transactions and payouts, preserve contracts and consent evidence, resolve disputes and chargebacks, maintain security and audit records, meet tax and legal obligations, and enforce agreements. Retention varies by record type and considers the sensitivity of the information, the amount and nature of processing, user expectations, legal limitation periods, and technical backup cycles.

An authenticated couple or vendor can submit an account-deletion request from account settings. The server derives the account identity, records the request, disables public profile features, and places the account in a deletion-requested state for administrator processing. This request does not claim that every record is erased immediately. Transactions, contracts, consent receipts, fraud and security records, support history, legal holds, backups, content involving other users, and records required by law may be retained. Public content already copied by others may remain outside our control. Contact us for access, correction, portability, opt-out, appeal, authorized-agent, guest, or non-account requests.

11. Security

We use administrative, technical, and organizational measures designed to protect personal information, including authenticated access, role-based data rules, restricted service operations, payment processing through Stripe, and controlled cloud-storage upload paths. Analytics identity is derived server-side and event inputs are bounded. Calendar availability requests require authentication, ignore caller-supplied participant emails, validate approved vendor identifiers, limit date ranges, and return only coarse busy intervals rather than call titles, identifiers, notes, or attendee details. No system is completely secure, and we cannot guarantee that unauthorized access, loss, misuse, or alteration will never occur. You are responsible for protecting your login method, devices, and account access and for promptly reporting suspected compromise.

12. Your choices and privacy rights

  • Account information: update available profile, wedding, business, messaging, integration, and visibility settings in the Platform.
  • Marketing email: use the unsubscribe method in a marketing message or contact us. We may still send transactional, security, legal, and account messages.
  • Connected services: disconnect an integration through available settings or the third-party provider. Information already imported may remain until separately deleted.
  • Analytics and external media: use “Privacy Choices” in the footer to allow or withdraw optional first-party analytics and third-party media.
  • Public content: delete or edit content where the feature allows, or contact support. Removal may not affect copies already shared or lawfully retained.
  • Privacy requests: depending on your location and applicable law, you may request access, correction, deletion, or a portable copy of personal information, or opt out of certain sale, targeted-advertising, or profiling practices. You may also appeal a denied request where required.

Submit a request to support@wedbegin.com with “Privacy Request” in the subject. State your request and the email associated with the Platform. We may verify identity and authority before responding. An authorized agent may submit a request where allowed, but we may require proof of authorization and direct verification. We will not discriminate against you for exercising an applicable privacy right.

13. U.S. state privacy disclosures

The categories described in Section 2 correspond to common U.S. state-law categories, including identifiers; customer records; commercial information; internet or electronic activity; approximate geolocation; professional information; user content that may include sensory information; inferences; and, when voluntarily submitted, information that may be considered sensitive. We collect these categories for the purposes in Section 4 and disclose them to the recipient categories in Section 5.

We do not knowingly sell personal information, do not currently share it for cross-context behavioral advertising, and do not offer a financial incentive in exchange for collecting or selling personal information. WedBegin Bucks, vendor discounts, and membership pricing are Platform products and are not offered in exchange for permission to sell personal information.

Some state privacy laws apply only after statutory thresholds are met. Whether or not a particular law applies, we will review a properly verified request and respond as required by applicable law. California residents can use the method in Section 12 to request the information required by the CCPA. Connecticut and other covered-state residents may also use that method to exercise applicable access, correction, deletion, portability, opt-out, and appeal rights.

14. Children

The Platform is intended for adults and is not directed to children under 13. Accounts and commercial transactions require users to be at least 18. We do not knowingly collect personal information directly from children under 13. Wedding guests or event attendees may include minors; an adult organizer must provide and manage that information. If you believe a child under 13 provided information directly without appropriate authorization, contact us so we can investigate and delete it where required.

15. Processing in the United States

WedBegin and its providers operate primarily in the United States. If you access the Platform from another country, your information may be transferred to and processed in the United States, where privacy laws may differ. The Platform is currently offered for U.S.-focused use and is not represented as compliant for active marketing to every foreign jurisdiction.

16. Third-party services

The Platform links to and integrates with services operated by others, including Stripe, Google, YouTube, Vimeo, vendor websites, registries, and social networks. Their privacy policies and terms govern their independent processing. WedBegin is not responsible for a third party’s service, content, or privacy practices.

17. Changes to this Policy

We may update this Policy as the Platform, providers, or law changes. We will post the updated version and effective date. If a change is material, we will provide additional notice or request renewed acknowledgment when required. Earlier consent receipts remain evidence of the version accepted at the time.

18. Contact us

WedBegin, LLC is formed in Connecticut. Questions and privacy requests can be sent to support@wedbegin.com or submitted through the Platform’s Support Ticket page. Include “Privacy Request” in the subject for access, correction, deletion, or appeal requests.

Mailing address: WedBegin, LLC, 41 S Main St, Unit 19, Jewett City, CT.