Privacy Policy

Last updated: October 18, 2026. Effective: October 18, 2026.

Please read this; if anything is unclear, email benkoe@gmail.com.

Who we are

My Wedding Planner Online (myweddingplanneronline.com) is a website for planning a wedding together. It is run by Benjamin Koevary, an individual, who is responsible for your information. In this policy "we" and "us" mean him. For any privacy or account question, email benkoe@gmail.com.

The service is in a closed test: people join by invitation only.

What we collect

Your account: your email address, your first and last name, and the invite code you signed up with.
Your password: if you choose one, it goes straight from your browser to our sign-in provider, Supabase. Our own server never receives it.
Sign in with Google: if you use it, Google shares your name, email address and profile picture (the basic profile permissions the app asks for). See "Data from Google" below.
Invitations: the email addresses owners enter to invite people to a wedding, kept before those people have an account.
Your wedding's plan: what you and the other members of a wedding enter, such as venues, caterers, vendors, guests and their details, seating, tasks, the timeline, music, votes and comments, and the wedding's settings.
Files you upload, such as quotes, contracts and pictures.
Email sent to a wedding's address: each wedding can have its own email address. Email sent or forwarded there is kept with the wedding: who it is from, to and copied to, the subject, the text and its attachments.
Spotify, only if a wedding links an account: the Spotify account's name and ID and the keys (tokens) that let the app use it, stored encrypted, and the songs and playlists you choose to bring in.
AI usage: each time an AI feature runs, a usage record for the wedding's account: which feature, how much text it used (counted in tokens) and when.
Technical details: like any website, our servers receive your IP address and basic browser information when you visit. Our app uses your IP address briefly, in memory, to limit repeated sign-up attempts.

How we use it

Only to run the service for you: to sign you in, to show and save your wedding's plan for its members, to send the emails the service needs (invitations, sign-up and password emails), and to run the features you choose to use. We do not sell your information, we do not show ads, and we do not use your information for advertising.

Who in a wedding can see what

Each wedding has members, and each member has a role: owner, editor or viewer. Every member can see that wedding's plan, files and emails, and the names and email addresses of its other members. Owners and editors can change the plan; viewers can only look. Owners invite and remove members and change the wedding's settings. Members of one wedding cannot see another wedding's information.

Services that handle your information

We use these companies to run the service. Each one gets only what its job needs.

Supabase: our database (accounts and every wedding's plan), sign-in (passwords and Sign in with Google) and file storage (uploaded files and email attachments).
Vercel: hosts the website and runs our server code.
Resend: sends the service's emails (invitations, sign-up emails and password emails) and receives the email sent to a wedding's address.
Anthropic: powers the AI features. Every AI request includes the wedding's style, catering setting and couple type. Beyond that, each feature sends only what it needs:
- Reading a quote: the document, the guest count and the wedding date, and, for a venue or caterer already saved, its saved details.
- Reading a venue's pricing: the venue's saved pricing and notes, its stored files and the guest count.
- Describing a bar: the description you type in.
- Ask the planner: the wedding's plan (venues, caterers, vendors, guests, seating, groups and votes) and your question. It leaves out the contact names, phone numbers and email addresses of venues, caterers and vendors, and guests' home addresses, phone numbers and email addresses.
- Smart seating: the guest parties (names, party size, whose guests they are, side, class and group, priority, children, dietary needs and notes, but not their addresses, phone numbers or email addresses), the room, the tables, the sides' names and your seating rules.
- Email sent to a wedding's address: the email (who it is from, to and copied to, the date, the subject and the text) and its attachments. To work out who the email is from, the AI also gets the wedding's list of venues, caterers and vendors with their contact names, contact email addresses and websites, the wedding's vendor categories, and the email addresses of the wedding's members, so their own messages can be told apart. To read it, the AI also gets the saved details of the venue, caterer or vendor it is about, the guest count, the wedding date and the members' email addresses again.
Google: Sign in with Google, if you use it. The Venues page also loads Google Maps and Google Places in your browser to show the map and suggest places and addresses as you type. Setting up a wedding, and choosing or changing the town in Wedding settings, load Google Places the same way: the town you type goes from your browser to Google to suggest towns. The town you pick, with its map coordinates, is saved with the wedding, and our server looks up its time zone from those coordinates itself, without sending them to anyone. The pages also load their fonts from Google Fonts, so Google sees those requests from your browser. Google handles them under its own privacy policy.
jsDelivr: the Venues map loads a small map helper from the jsDelivr network.
Spotify: if a wedding links a Spotify account, the app reads that account's playlists and songs when you ask it to, sends Spotify the words you type to search for songs, and creates or updates the playlist you send. Songs with a Spotify link play in a player loaded from Spotify.

If you subscribe to a wedding's calendar, your calendar app gets a private link to the wedding's dates. The Google and Outlook subscribe buttons hand that link to Google Calendar or to Microsoft's Outlook.com (Outlook also gets the wedding's name). Anyone who has that link can see those dates, so share it only with people you trust.

Data from Google

If you sign in with Google, Google shares your name, email address and profile picture. Google sign-in works only for an email address that already has an account here; our sign-in provider, Supabase, links your Google login to that account and keeps the data Google shares with it.

Your email address is your account's email address, and we use it as we use any account's email address: to sign you in, to send you the service's emails, to show it to the other members of your weddings, and, when the AI reads an email that arrived at a wedding's address, together with the other members' addresses, to tell the members' own messages apart from the sender's (see Anthropic above). The app does not use the name or the picture Google shares: we ask for your name ourselves, and we do not show your Google picture.

We do not sell information from Google, we do not use it for advertising, and we do not use it to train AI models.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your browser

The app keeps your sign-in session and a few preferences (such as filters and view choices) in your browser's own storage. It sets no cookies of its own, and it uses no advertising, tracking or analytics tools. Signing out removes the session from your browser.

Keeping and deleting your information

We keep your information while your account is open. When someone deletes something in the app, it is hidden from everyone but kept, so a mistake can be undone.

To delete your account, or, if you own a wedding, the wedding and everything in it, email benkoe@gmail.com from the address you sign in with. We will delete it within a reasonable time.

Security

Everything travels over encrypted connections (HTTPS). Every request is checked against your sign-in, and the database itself only lets each member reach the weddings they belong to. Files are kept in private storage and opened only through short-lived links. Spotify keys are stored encrypted. No system is perfectly secure, but we work to keep yours safe.

Children

The service is not for children under 13, and we do not knowingly collect information from them. If you think a child under 13 has given us information, email us and we will delete it.

Changes to this policy

If we change this policy, we will post the new version on this page and update the date at the top.

Contact

Benjamin Koevary, benkoe@gmail.com.