What we keep, and what we don’t.

The short version

Epica Invites is run by Epica Brands LLC. We do not sell your information, we do not show advertising, and we do not track you across the internet. There is no analytics tool and no tracking pixel in this product — not a small one, not a private one. We keep what the service needs to work, and not much else.

The one thing we do collect that isn’t strictly the service working is crash reports, so that when something breaks we find out without waiting for someone to tell us. That is error detail — what failed and where in our code — not a record of what you did. We don’t record your screen, and we don’t attach your IP address or your cookies to it.

1. If you are a guest

You can open an invitation and read all of it without an account and without giving us anything. If you reply, we keep the name you type, your answer, how many people you are bringing, and anything you choose to add — a dietary note, a comment, a photo. That is stored so the host can see it.

Your contact details are never shown to other guests. That is a fixed behaviour of the product, not a setting somebody could switch.

2. If you are a host

We keep your email address (that is how you sign in), your name and any profile photo you add, and the events you create — their details, the guests you add, replies, tasks, announcements, and photographs.

Some of that is other people’s information that you entered. You are responsible for having it fairly; we hold it in order to run your event and for no other purpose. We do not email your guests on your behalf — there is no sender in this product, and you share invitations yourself.

3. The companies that help us run it

We use a small number of service providers, and each one only receives what it needs:

• Supabase — the database, sign-in, and file storage. Most of what is described above lives here.
• Vercel — hosting. It processes the requests your browser makes.
• Resend — sends our email, which today is sign-in codes.
• Sentry — crash reports. When something goes wrong it receives the error and where it happened in our code. It is set up not to attach your IP address or your cookies, and it never records your screen.
• Open-Meteo — the weather shown on an event. It receives the event’s location, never anything about you.
• A map provider — for the little map on an invitation. We fetch that image from our own servers, so the map provider never sees your device or your address, only ours.

4. Cookies

We use cookies only to keep you signed in. There are no advertising cookies and no third-party trackers, which is why this site does not greet you with a consent banner — there is nothing to consent to.

5. An invite link is unlisted, not secret

An invitation can be opened by anyone holding its link. We ask search engines not to index invite pages, but that is a request rather than a lock. Treat every invitation as unlisted rather than private, and think before putting a home address on one.

6. How long we keep things

We keep an event and its contents while your account exists, so that you can look back at a celebration afterwards. Ask us to delete your account and we will remove it and its events. A guest can ask us to remove their reply or a comment at any time.

This is an early-access product and it does not yet have a self-service delete button. Until it does, ask us and a person will do it.

7. Your choices

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Depending on where you live you may have further rights; tell us what you need and we will do our best to honour it regardless.

8. Children

The service is not intended for children under 13, and we do not knowingly collect their information. If a child has been added as a guest by a host and you would rather they were not, tell us and we will remove them.

9. Changes, and reaching us

If we change this policy in a way that matters, we will say so rather than quietly move the date at the top. Write to hello@epicainvites.com or use the contact page. See also our terms.