Trust, security & privacy

This page is maintained by Wedding Solutions LLC to answer common security and privacy questions about The Wed Thread. It is editable project content, not an independent certification. Where this page describes platform features we rely on, those are factual descriptions of enabled controls — not third-party verification.

The Wed Thread is operated by Wedding Solutions LLC, a New Jersey company. The service is intended for users 18 and older. We aim to honor user rights consistent with GDPR and CCPA for users in those jurisdictions, and the service is governed by the laws of the State of New Jersey, USA.

Sign-in is handled by our authentication provider using email and password or Google sign-in. Sessions are tied to your account and stored locally in your browser; signing out clears that local session.

Every couple's wedding data — profile, planner messages, memory, saved vendors, moodboards, guests, budget, checklist, seating — is protected by row-level access rules so that only the signed-in account can read or write its own rows.

We collect only what powers your planner and AI features:

• Account basics (email, display name, optional avatar).
• Wedding profile you choose to share — date, location, guest count, budget, aesthetic, venue type.
• Planner content you create — saved vendors, moodboards, guests, budget, checklist, seating.
• Chat messages you send to the AI assistant.
• Minimal operational logs (rate-limit counters, error reports) to keep the service reliable.

We do not sell your data, and we do not use your wedding content to train third-party foundation models.

On the free plan, the AI can see your current planner state (the profile and items you have saved) but does not carry conversation history forward between sessions.

On WedThread+, persistent per-couple memory is enabled so the AI can recall earlier conversations and preferences. This memory lives in your account and is removed when you delete your data (see below).

We route AI requests through our model provider on standard commercial terms — no training on customer API data, with the provider's standard short-term retention for abuse monitoring. We do not currently advertise zero-data-retention; if and when we qualify for that tier, we will say so explicitly here.

We rely on these vendors to operate the service. None receives your data for their own marketing:

• Supabase — managed Postgres, authentication, and file storage for moodboard images.
• Cloudflare — application hosting and edge runtime.
• AI model providers (currently Anthropic and Google via a managed gateway) — process your prompts to return planner responses.
• Google Maps Platform — venue and location lookups.
• Transactional email provider — account and notification emails only.

We use a small number of first-party cookies and local-storage keys required to keep you signed in. We do not run third-party advertising trackers. Any product analytics we add will be limited to aggregate usage signals and disclosed here.

You can wipe your data at any time from Your thread in the planner using "Delete everything." That action removes your wedding profile, AI memory, saved vendors, moodboards, guests, budget, checklist, and seating from our database.

We retain minimal operational logs (for security and abuse prevention) for a short period and then purge them on a rolling schedule.

To request access, export, correction, or deletion of your personal data, email support@thewedthread.com. We respond within the timeframes required by applicable law. You can also exercise most rights directly in the app (export your profile, delete everything).

If you believe you've found a security issue, please email support@thewedthread.com. Please give us reasonable time to investigate and remediate before any public disclosure. We will not pursue researchers who act in good faith.

The Wed Thread is GDPR- and CCPA-aware in how we handle personal data and user rights. We are not currently certified under SOC 2, ISO 27001, HIPAA, or PCI DSS, and we don't claim to be. If that changes, this page will say so with the issuing body and date.