Privacy policy

Two different groups appear in MyEventOS, and they reach us differently. Hosts create an account and design an event. Guests never create an account; they answer an invitation their host sent them. A guest's details belong to the host who invited them, and we hold them on that host's behalf.

• Your email address, and if you sign in with Google, the name and profile picture Google shares with us.
• The events you build: wording, design, dates, guest lists, survey questions and any images you upload.
• Payment records for what you buy: which plan, for which event, when, and the Stripe reference. We never see or store your card details.
• Any message you send through the in-app feedback form, along with the page you were on.
• Requests for an offer you send to suppliers from the planner, and their answers, which come back through us: the supplier, what you wrote, the details sent with it (your names, date, venue, place and number of guests) and what they answered, with any files. We keep them so we can pass each answer on to you, and so we can show a supplier how many couples found them through MyEventOS.
• Which link or ad brought you here when you made your account (its source, campaign and ad name) and whether you were on a phone or a computer, so we can tell which of our ads are useful.

Only what the host asks for in their survey, and only what the guest chooses to type. That typically means a name and whether they are coming, and depending on the event it can include a meal choice, allergies, the number of people or children in their party, travel and accommodation details, and a gift they have claimed.

Guests are not profiled by us and never contacted by us for our own purposes. We do not use their answers to market anything. The ad measurement described below runs only for people who accept cookies, guests included, and never touches what a guest has answered.

The GDPR asks us to name a lawful basis for each thing we do with data, so here they are, in plain words.

• Running your account and your events, and taking payment for what you buy: performance of the contract between us.
• Keeping the service standing up, stopping abuse, and answering you when you write in: our legitimate interests in a service that works and is not misused.
• The Meta Pixel and PostHog, described below: your consent, given in the cookie banner and withdrawable at any time.
• Sending invitations and reminders to the guests a host names: the host's own lawful basis for contacting their guests. We send them on the host's instructions.
• Keeping payment records for as long as tax law says: a legal obligation.

A guest's answer can include things the GDPR treats as health data, such as an allergy, a dietary need or a request for step-free access. A guest types those into their host's own form, for their host to read, and only because they choose to: no field of that kind is ever required. That explicit choice is the basis for holding it, and a guest who would rather tell their host another way should leave the field empty.

• No selling or sharing of data with brokers, and no ad networks beyond the one measurement described below.
• No tracking cookies unless you accept them: decline the cookie banner and nothing follows you anywhere.
• No reading of your guest lists to build marketing lists of our own.

We use Vercel Web Analytics to see which pages people read, so we know what to improve. It counts page views, and how many visitors accept or decline the cookie banner, without cookies and without building a profile of you: no identifier is stored on your device for it, and it runs whether or not you accept cookies.

We also advertise on Facebook and Instagram, and to see whether those ads bring anyone here we use the Meta Pixel. It loads only after you accept cookies in the banner this site shows. Once it runs, Meta sets a cookie in your browser and receives the pages you visit here and a few moments along the way, such as opening a design, signing up, sending an invitation or paying, together with the amount paid. Meta may connect that to your Meta account if you have one, under its own privacy policy. Decline the banner, or choose "Only to improve" where the banner offers it, and nothing from Meta is loaded.

Behind the same banner we use PostHog, hosted in the European Union, to understand how the product is used and where it goes wrong: the pages you visit, moments such as creating an event, choosing a design, sharing an invitation, adding a guest or paying, and a replay of your session as a recording of the screen. Anything you type is hidden in that recording, and so is anything on the screens that hold guests' own answers: their names, meal choices and notes are blanked out before the recording is made. If you are signed in, PostHog is told your account id and email address, so a recording can be found for your account when you ask us for help. Decline the banner and PostHog is not loaded. "Only to improve", where the banner offers it, allows PostHog and nothing else.

What is kept in your browser, and by whom:

• Your sign-in session, kept by us in local storage so you stay logged in between visits. The service cannot work without it. It lasts until you sign out.
• The answer you gave the cookie banner, kept by us for a year so it does not ask again.
• _fbp and _fbc, set by Meta only if you accept, to tell whether an advert brought you here. Meta keeps them for three months.
• PostHog's own cookie, set only if you accept, to tie the pages of one visit together. It lasts a year.

Counting page views needs no cookie at all and stores nothing on your device. Nothing else is kept, and nothing is read for advertising unless you said yes.

Changing your mind takes one click. Cookie settings, at the foot of any page, opens the banner again, and a new answer takes effect at once: say no and what was set is not read again. Clearing your browser data removes all of it too.

We use a small number of established providers, each doing one job. They act on our instructions and are bound by their own data protection commitments.

• Supabase: the database and sign-in system that holds accounts, events and guest replies.
• Vercel: hosting for the website and its server functions, and the cookieless page-view counts described above.
• Meta: only if you accept cookies, to measure whether our ads on Facebook and Instagram bring people here. Meta receives the pages you visit and the moments listed above, and handles them under its own privacy policy.
• PostHog: only if you accept cookies, to see how the product is used, with session recordings in which everything typed is hidden. Hosted in the European Union.
• Stripe: payment processing. Stripe receives your payment details directly and we never handle card numbers.
• Resend: sending invitation and reminder emails, to the addresses a host supplies and to one a guest leaves to be reminded at, and a few emails to hosts about their own events (a welcome, and a reminder to share or finish one), each with a one-click unsubscribe.
• Google: three separate things. Signing in with Google, only if you choose it, tells us your email address, name and picture. Google Fonts serves the typefaces the pages are set in, which means Google sees the address your browser asks from. And a host who puts a map on their invitation embeds it from Google Maps, so a guest who opens that page loads it from Google.
• Cloudflare: the challenge on the sign-in page that tells a person from a machine.
• Anthropic: only when a host asks the designer to draft an invitation for them. What the host typed is sent to be written up, and is not used to train anything.

Data is stored on our providers' infrastructure and may be processed outside the European Economic Area, in particular in the United States. Those providers rely on the European Commission's standard contractual clauses, or equivalent safeguards, to make such transfers lawful.

• Your account, your events and their guest replies: while your account exists, so you can come back to an event after it happens. Delete the account yourself from the account menu (tap your email, then Delete my account), or ask us to, and they go at once, with the photos and music you uploaded.
• A deleted event: thirty days in a bin, then erased for good, automatically, every night. The thirty days are there so an event deleted by mistake can be put back; nothing in the app can read the bin in the meantime. A deleted account is not kept in the bin.
• Payment records: seven years, which is what Cyprus tax and accounting rules ask for, kept with Stripe even after an account is deleted. These are the amount, the date and the Stripe reference, never card details.
• Messages you send us through the feedback form or by email: two years, or longer if we are still talking about the thing you wrote in about.
• Requests for an offer and the suppliers' answers: while your account exists, like your events, and our copy in the MyEventOS mailbox for two years.
• What the cookie banner is told: one year, in your own browser, after which it asks again.

Under the GDPR you can ask for a copy of your data, ask us to correct it, ask us to delete it, object to how we use it, or ask for it in a portable form. You can delete your account yourself at any time from the account menu. For anything else, write to support@myeventos.com and we will answer within one month.

If you are a guest who replied to an invitation, the host who invited you decides what happens to your answer. Contact them first, or write to us and we will pass your request on.

You also have the right to complain to a data protection authority, in Cyprus the Office of the Commissioner for Personal Data Protection.

MyEventOS is for adults planning events. We do not knowingly create accounts for children under 16. A guest list may of course mention children attending a party; that information belongs to the host who entered it.

If this policy changes in a way that affects you, we will update the date at the top and, for significant changes, tell account holders by email.