Privacy Policy

1. Who We Are and How to Contact Us

WedCall (wedcall.com) is operated by Orbinate LLC, 30 N Gould St # 56317, Sheridan, WY 82801, USA. Orbinate LLC is the controller of account, service, support, security, and product-analytics data. For privacy requests, email may@orbinate.com.

When a couple uploads a guest list and decides how to use it for their wedding, the couple determines that purpose and WedCall processes the guest data to provide the requested wedding service.

2. Data We Collect

Account and profile data: name, email address, authentication details, language, and optional profile information. If you sign in with Google, Google provides your name, email address, and sign-in identifier; WedCall does not receive your Google password.

Wedding and guest data: wedding details, events, guest names and contact details, invitations, RSVPs, seating, budgets, checklists, stories, photos, messages, and other content you choose to add.

Payment and communication data: purchase amount, currency, plan, payment status and provider references; support messages; and email, SMS, WhatsApp, push, and delivery-status records when those channels are used. Stripe receives card details directly; WedCall does not store full card numbers.

WhatsApp guest replies: when a guest sends a message to a WedCall WhatsApp number, we record the message content and the sender's phone number.

Technical and usage data: IP address, device and browser information, timestamps, requested pages, security and rate-limit logs, consent choices, and product-interaction events.

AI feature data: text or planning context needed to answer a request when you choose an AI-assisted feature. Do not submit information you do not want processed for that request.

3. Why We Use Data and Our Legal Bases

Contract: to create and secure your account; host wedding pages; manage guests, invitations, RSVPs, plans, media and paid features; provide support; and deliver requested communications.

Legitimate interests: to prevent abuse, keep the Service reliable, diagnose errors, understand aggregate product use, and improve WedCall. We balance these interests against the rights of affected people.

Consent: for optional analytics or ad measurement where consent is required, and for optional device permissions or communications that require consent. You may withdraw consent at any time without affecting earlier lawful processing.

Legal obligations and claims: to keep records required by tax, accounting, consumer, fraud-prevention, or other applicable law, and to establish, exercise, or defend legal claims.

4. Guest Data

Couples may add guests' names, phone numbers, email addresses, meal choices, household information, and RSVP details. We use guest data to provide that wedding's invitation, RSVP, seating, communication, and related planning features—not to market WedCall to guests.

If a guest replies through WhatsApp, WedCall records the message content and sender's phone number, sends the message content to Anthropic to interpret the guest's intent, and may automatically create an RSVP response that the couple can view and correct in their wedding dashboard. These message and RSVP records follow the same retention and deletion rules as the related wedding data described in Section 8.

If you are a guest, the couple is normally the source of your information. You can contact the couple or may@orbinate.com to ask about access, correction, objection, or deletion. We may need enough information to identify the relevant wedding and verify the request.

5. Service Providers and Sharing

We disclose data only as needed to operate a requested or enabled feature: DigitalOcean for hosting and infrastructure; Resend for transactional email and delivery events; Google for sign-in, Analytics and—only when allowed—Ads measurement; Microsoft Clarity for product interaction analytics; Stripe for payments; Anthropic for invoked AI-assisted features; Twilio for enabled SMS delivery; and Meta for enabled WhatsApp delivery.

For the WhatsApp RSVP assistant, Anthropic receives the guest's message content to interpret the intended response.

A provider receives only the data needed for its role. Some providers or channels may be disabled and receive no data. We may also disclose data when required by law, to protect users or the Service, or as part of a corporate transaction subject to appropriate confidentiality protections.

Public wedding pages and content are visible according to the couple's publication, password, link, and visibility choices. A public or link-accessible page should not contain information the couple wants to keep private.

6. International Data Transfers

Orbinate LLC is established in the United States, while core hosting is configured in a DigitalOcean EU region. Providers may process data in the United States, the European Economic Area, or other locations where they operate.

Where applicable law requires transfer safeguards, we use the provider's applicable contractual and legal transfer mechanism. You may contact may@orbinate.com for information about the mechanism relevant to your data and how to obtain available safeguards.

7. Cookies, Analytics and Ad Measurement

Essential storage is used for authentication, security, language, and session management. A self-hosted, cookieless Umami counter records limited page and product events.

Google Analytics and Microsoft Clarity help us understand product use and diagnose usability problems. Clarity can record interactions such as clicks, scrolling, and navigation; sensitive form areas are designed to be masked, and we do not intentionally send message or form contents as analytics events. You can change analytics preferences from the footer. In the EEA, UK, and Switzerland, analytics storage follows the applicable consent signal.

Google Ads measurement is a separate optional category and is not enabled unless you allow it. We use it to measure whether a paid ad led to a conversion, not to sell personal data. Ad personalization remains disabled by WedCall.

8. Retention and Deletion

We keep account and wedding data while the account or wedding is active. A deletion request removes the relevant content from active product systems as the deletion operation is completed. Residual encrypted backups expire on their normal protection cycle and are not restored except for disaster recovery.

Security, payment, tax, delivery, consent, and support records may be kept longer when reasonably needed for fraud prevention, accounting, legal obligations, dispute handling, or proof of user choices. We delete or de-identify data when its purpose and required retention period end.

9. Your Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to processing, withdraw consent, receive a portable copy, and complain to a data-protection authority. You may also have a right to appeal a denied privacy request.

Use account settings where available or email may@orbinate.com. We may verify your identity and may retain the minimum record needed to document the request. We do not discriminate against anyone for exercising a privacy right.

10. Security and Automated Processing

Data is encrypted in transit and stored on access-controlled infrastructure. We use technical and organizational safeguards appropriate to the Service, but no online system can be guaranteed completely secure.

AI features generate suggestions and drafts. WedCall does not use AI output to make decisions that produce legal or similarly significant effects about users or guests. Review AI-generated text before relying on or publishing it.

The WhatsApp RSVP assistant may automatically create an RSVP response from its interpretation of a guest message. The couple can see and correct that response in the wedding dashboard.

11. Children

WedCall account services are not directed to people under 18 or under the legal age required to enter a contract where they live. If you believe a minor created an account without appropriate authority, contact us so we can investigate and remove it when required.

12. Changes to This Policy

We may update this policy as the Service or applicable requirements change. We will provide an in-product or email notice before a material change takes effect when required. The effective date above identifies the current version.