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 add-ons you buy: what was purchased, 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.

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.

• 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 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 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. 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.

MyEventOS keeps your sign-in session in your browser's local storage so you stay logged in between visits, and remembers the answer you gave the cookie banner so it does not ask again. If you accepted, the Meta Pixel and PostHog set their own cookies as well. Clearing your browser data removes all of it, and the banner asks afresh.

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.
• Google: only if you choose to sign in with Google, which tells us your email address, name and profile picture.

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.

Events, guest replies and account data are kept while your account exists, so that you can come back to an event after it happens. Ask us to delete your account and we remove your events and their guest replies. Records of payments are kept longer where tax and accounting rules require it.

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. 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.