Last updated: September 20, 2026
Wedding Recon is a community tool for engaged couples. We collect as little as we can get away with: an email address so you can sign in, a username, and whatever recon you choose to post. We do not sell your personal information, we do not run ads, and we do not record your screen or your browsing outside this site.
Your account. Your email address (used to send sign-in codes and to contact you about your account) and the username you pick. We never ask for a password — sign-in is a one-time code sent to your email.
What you post. Recon entries — vendor, price quotes, notes, dates, and any photos you upload — along with the vendors you save to your Planning Hub.
How you found us. On your first visit, if you arrived from a link that carries campaign tags or from another site, we store that source in a first-party cookie and attach it to your profile if you later sign up. It records where you came from and nothing else, it is never overwritten by a later visit, and a direct visit records nothing at all. A separate Muse-arrival event lets us count a connector return without replacing that original first-touch source.
Usage. Page views and a small set of named product events (for example: a recon saved, a vendor page opened) through PostHog, our analytics provider. Blanket click tracking and session recording are both switched off, and anonymous visitors stay anonymous to PostHog until they sign in.
Technical data. Our hosting and database providers log ordinary request data — IP address, browser type, timestamps — for security and reliability.
Vendors who claim a listing. A contact email, your role at the business, and the listing content you write. Payments run through Stripe: we store only Stripe identifiers and your subscription status. Card numbers never touch our servers.
The Explore map has a “find me” button. If you allow it, your browser gives us your position so the map can centre on you. It stays in your browser for that visit — we do not send it to our servers, store it, or attach it to your account. The map otherwise works from whatever area you have panned to.
Recon you post is public. It appears on the vendor page attributed to your username, is visible to anyone with the link whether or not they have an account, and may be indexed by search engines. Your email address is never shown publicly. Please do not put anything in a recon entry — including in photos — that you would not want a vendor, a guest, or a search engine to see.
The read-only connector exposes selected public vendor and active recon information. It never returns emails, author IDs, private saves, reports, moderation data, unpublished vendor listings, billing identifiers, or raw internal metadata. Operational telemetry is limited to operation, category, coarse location, result counts, duration, status, request ID, and partner identity. We do not log API keys, agent prompts, full search conversation text, recon text, or personal wedding details.
To sign you in and keep your account secure; to show your recon and saved vendors back to you and to the community; to moderate reported content; to understand which parts of the product people actually use and where new couples are finding us; and to bill vendors who subscribe to a verified listing.
We do not sell your personal information or share it for advertising. We use a small number of service providers who process data on our behalf: Supabase (database, authentication, photo storage), Vercel (hosting), PostHog (product analytics), Stripe (vendor payments), and Google (business search and vendor photos in the directory). Map tiles come from OpenFreeMap. We may also disclose information if the law requires it, or to investigate abuse of the service.
We use a session cookie to keep you signed in, the first-touch source cookie described above, PostHog’s analytics cookie, and a first-party preference cookie that records for up to one year only that this browser has used the product. There are no advertising or cross-site tracking cookies. You can clear or block cookies in your browser; sign-in will stop working without the session cookie. Connector API routes neither require nor set browser cookies.
We keep your account data for as long as your account exists. You can edit any recon entry you posted from your Planning Hub at any time. There is no self-serve delete button yet — email us to have an entry taken down, or to delete your account and everything attached to it. Content you posted may remain in backups for a short period after deletion, and moderation records may be retained where we need them to prevent abuse.
Connector operational analytics are reviewed after the 30-day pilot and retained for no more than 12 months unless a longer period is needed to investigate abuse or a security incident. Quota counters contain only credential bucket identifiers and counts, reset in place, and may be removed during routine maintenance. Access is limited to operators who need it.
Depending on where you live — including Colorado, where we are based — you may have the right to access, correct, delete, or receive a copy of your personal data, and to opt out of its sale or of profiling (we do neither). Email us and we will action the request; we will not treat you differently for making one. If you are unhappy with our response, Colorado residents can raise it with the Colorado Attorney General.
Wedding Recon is not intended for anyone under 16, and we do not knowingly collect information from children. If you believe a child has created an account, let us know and we will remove it.
If we change this policy we will update the date at the top of this page. Material changes will be flagged in the app.
Questions, requests, or concerns about privacy? Email kiara@weddingrecon.com.
See also our Terms & disclaimer.