Privacy Policy

• Your account — your email address, and a display name and avatar image URL if you set them (or if your sign-in provider supplied them). Sign-in is handled by Supabase Auth; we keep a copy of your profile (email, name, avatar URL) in our own database, together with your plan (free or premium).
• Events — the event name, description, date, budget and settings; who is a member and in what role; the draw (who gives to whom) and any exclusion rules; group and direct messages posted in the event, including whether a message was marked anonymous.
• Invitations — the email addresses organizers enter when inviting people, plus the invite link token and whether it was accepted. Invitees do not need an account for us to hold their address.
• Households — household names, which members belong to them (used so couples and families don’t draw each other), and the email addresses of people invited to a household until they accept or decline. Nobody is added to a household without accepting.
• Wishlists — wishlist names, visibility settings, and items (title, link, image URL, price, priority, notes), plus who has claimed or bought an item.
• Gift tracker (premium) — gifts you record (recipient, description, cost, status) and shipments (carrier, tracking number, status). A gift recipient may be a person who does not use the Service; you type their name.
• Admin audit log — if a site administrator acts on an event, we record who did what and when.
• Rate-limit counters — short-lived counters keyed by your account (or an event) so invitations, messages and draws can’t be fired off too quickly.
• Server logs — standard request logs kept automatically by our hosting providers (Vercel, Supabase), which include IP address and browser type.

We do not run analytics, tracking pixels or advertising scripts. We do not store files you upload — the app only stores links (URLs) you paste.

Mellowish is a group tool, so some of your information is visible to the people you share events with. Here is exactly what:

• Event members see each other’s names in the member list and messages. If you have not set a name, your email address is shown instead.
• Your match is private: after the draw, only you see who you’re buying for. Organizers do not see the assignments.
• Organizers and event admins see the email addresses of people they have invited who have not yet joined.
• Invite links show the event name, description, type, date, budget, how many people have joined, the inviter’s name (or the part of their email before the @ if they have no name), and a partly hidden version of the invitee’s email (for example mi•••@example.com) to anyone who opens the link. Treat invite links like a key to the event.
• Wishlists have three visibility settings. Private: only you. Event: members of the chosen event. Public: any signed-in Mellowish user who has the link. “Public” does not mean the open internet — the page requires signing in and is not listed anywhere.
• Claims on your wishlist are hidden from you so gifts stay a surprise. Other viewers of the wishlist see the claimer’s name (never their email) next to a claimed item. Your name appears on the wishlist as its owner.
• Messages posted to the whole event are visible to all members. A direct message is visible only to the sender and the recipient. If you tick “Anonymous”, other members see “Anonymous” instead of your name.
• Household members see the names (or emails) of the other people in the household and the addresses of pending invitations. Joining or leaving a household resets any already-drawn exchange you share with its members.
• Site administrators can open any event to help with support or abuse reports. Every such action is written to the audit log.

To run the Service: create events, perform draws, share wishlists, deliver messages, send invitations, and (on premium) track gifts. To sign you in and keep your account secure. To email you the messages the Service needs to send: sign-in links and event invitations.

We do not sell your personal information, and we do not use it for advertising.

• Sign-in links (“magic links”) are sent by Supabase Auth when you ask to sign in.
• Invitation emails are sent through Resend, on behalf of the organizer, to the addresses they enter. If you receive one and don’t want to join, you can simply ignore it.

We use only the cookies Supabase Auth needs to keep you signed in. There are no analytics or advertising cookies.

• Supabase — authentication and our Postgres database.
• Vercel — hosting and request logs.
• Resend — delivery of invitation emails.
• Google — only if you choose “Continue with Google”; Google then acts as your identity provider and shares your email, name and profile picture with us.

Each of these processes data only to provide its service, under its own privacy policy. If we add paid plans, we will update this list with the payment processor before taking any payment.

Your content stays until you delete it. You can delete events, wishlists, items and gifts inside the app.

Delete my account on your profile page removes your account, your profile, and your personal data. Be aware of what remains:

• Events you own are handed to another member, or deleted if you were the only one left.
• Messages you sent are deleted with your account.
• Audit-log entries and invitations you sent lose their link to you.
• Invitations addressed to your email address are deleted, including ones you accepted.

Deleting your account also deletes your Supabase Auth login. Backups kept by our providers age out on their own schedule.

Download my data on your profile page gives you a JSON file of your account and content. Depending on where you live (for example under GDPR or CCPA) you may also have rights to access, correct, export, or delete your personal data, or to complain to a supervisory authority. Email us and we’ll help.

The Service is not directed at children. You must be at least 16 to create an account. There is no feature for parents to manage a child’s account; if you learn that a child under 16 has an account, tell us and we will delete it.

We may update this policy from time to time. Material changes will be posted here with a new “last updated” date.