Legal
Privacy policy
How Aemeli handles the personal data of the couples, guests and vendors who use it — what we collect, why, who sees it, and what you can ask of us. Last updated 9 October 2026.
Who we are
Aemeli is a wedding planner for couples marrying in Athens, at aemeli.com. It is a personal, non-commercial project run by Dimitris Kotsakos, a private individual in Greece — not a company. He is the controller of the personal data described here; "we" in this policy means him and the people who help him run Aemeli.
This policy covers the website, the planning app, the vendor side and the emails we send. A couple's own wedding website on a *.aemeli.com address is covered too.
Questions about your data: hello@aemeli.com.
What we collect
We collect what you give us to plan the wedding, what vendors send you through Aemeli, and a little technical data to keep accounts secure.
| What | Examples | Where it comes from |
|---|---|---|
| Account | Name, email address; your Google, Apple or Facebook account ID if you sign in with one | You, or the sign-in provider you choose |
| Wedding plan | Your names, date or date window, guest count, budget band and figures, how you plan, your to-dos | You and your partner |
| Guest list | Each party's name, size, reply, email, phone and notes | You and your partner |
| Wedding website | Names, date, place, welcome note, cover photo, the address you choose | You and your partner |
| Messages and offers | Your enquiries, the vendor's replies (including replies sent by email), offers, their line items and payment plans | You and the vendors you contact |
| Signatures | The name you type, the time, your IP address and browser, and a fingerprint of the document you signed | Recorded when you sign an offer |
| Vendor listings | Business name, contact details, address and location, photos, description, prices | Vendors |
| Technical | Sign-in times and IP addresses, a session cookie, error reports | Your browser and our servers |
| How you use Aemeli | Only if you accept analytics: the pages you visit and what you click, and recordings of your visits, with everything you type and your guests' and vendors' details hidden | Your browser |
We do not take card or bank details. No payment passes through Aemeli today.
Guest details are about people other than you. Add them only if you are allowed to, and only what the planning needs.
How we use it, and why we may
We use your data to run the planner you signed up for, and for little else. Each use rests on a legal basis under the GDPR.
| Use | Legal basis | ||
|---|---|---|---|
| Your account, sign-in by code or provider, your plan, guest list, budget, to-dos and website | Contract: it is the service (Art. 6(1)(b)) | ||
| Sending your enquiries to vendors and their replies and offers back to you | Contract (Art. 6(1)(b)) | ||
| Recording a signature as evidence of what was agreed | Contract, and our legitimate interest in proving it (Art. 6(1)(b), (f)) | ||
| Emails about your account and your conversations | Contract (Art. 6(1)(b)) | ||
| Keeping accounts secure, preventing abuse, fixing errors | Legitimate interest (Art. 6(1)(f)) | ||
| Showing published vendor listings to couples | Contract with the vendor (Art. 6(1)(b)) | ||
| Keeping records the law requires | Legal obligation (Art. 6(1)(c)) | ||
| Understanding how Aemeli is used | and recordings of visits | to improve it | Your consent, asked in the cookie banner (Art. 6(1)(a)); you can withdraw it at any time |
We do not sell your data, show advertising, or send marketing email. If that ever changes, we will ask first.
How AI helps, and what it never decides
We use an AI model from OpenAI to read your conversations with vendors. It decides nothing about you.
When a vendor replies, the model reads that thread to pull out the dates they say are free, the price range they quote, and anything they ask you to do by a date. These show up as suggestions and to-dos, marked as found by AI. We check every result before showing it, and you can ignore or dismiss any of them.
Only the thread in question is sent to the model, in the United States. Under OpenAI's API terms, data sent through the API is not used to train their models, and OpenAI keeps it for at most 30 days to detect abuse before deleting it.
Who we share it with
We share data only with the people you plan with, the vendors you contact, and the companies that run parts of the service for us.
- Your partner. Everyone you invite to your wedding sees and can change everything in it.
- Vendors you contact. When you check availability or send an enquiry, the vendor receives your names, wedding date, guest count, the brief you share, and your messages. When you sign their offer, they receive your signature record. Vendors are independent businesses and handle what they receive under their own policies.
- The people who run Aemeli. We can read your wedding's details, your conversations and your offers when running the service needs it, and to help you when you ask. Only those whose work on Aemeli needs it have that access.
- Guests. If you publish your wedding website, anyone with its address can see what you put on it.
Companies that process data for us, under data processing agreements:
| Provider | What they do | Data involved |
|---|---|---|
| Fly.io | Hosting, database, servers (EU region, Amsterdam) | All service data |
| Cloudflare (R2) | Storing uploaded photos and files; serving listing photos | Uploads |
| Resend | Sending email, and receiving vendors' email replies | Email addresses, message content |
| OpenAI | AI reading of your conversations with vendors | The thread read |
| Sign-in with Google; address search for vendor locations | Account ID and email; addresses typed | |
| Apple, Meta (Facebook) | Sign-in with Apple or Facebook | Account ID and email |
| Sentry | Error reports | Technical details; we strip personal data before sending |
| PostHog (EU) | Analytics and recordings of visits, only if you accept them | What you click and see, with what you type hidden; your account ID, email and name if you are signed in |
We may also disclose data when the law requires it, or to protect someone's rights or safety.
Where it is stored
Our servers and database run in the EU, in Amsterdam. Some providers above are based in the United States (OpenAI, Resend, Google, Apple, Meta, Sentry, Cloudflare). Where data leaves the EU, it is covered by the EU–US Data Privacy Framework where the provider is certified under it, and otherwise by the European Commission's Standard Contractual Clauses in that provider's data processing terms.
How long we keep it
- Your account and wedding: for as long as you keep the account. You can delete it at any time from your account settings.
- Signed offers and their signature records: for five years after the wedding date, as evidence of what was agreed, then deleted.
- Conversations with vendors: for as long as the wedding exists; the vendor keeps its own copy.
- Sign-in codes: a few minutes, until used or expired.
- Analytics and recordings of visits: one year for analytics, 30 days for recordings.
- Error reports and server logs: up to 90 days.
- Backups: daily copies for 60 days and monthly copies for a year, after which deleted data is gone from them too.
Your rights
You can ask us to show you, correct, delete, or hand over your data, to restrict or object to how we use it, and to withdraw any consent you gave. Write to hello@aemeli.com; we answer within one month.
Much of this you can do yourself: change your details, remove guests, and delete your account in the app, under Settings › Account. Deleting it removes your account and, if no partner remains, your wedding — whether you signed in with a code, Google, Apple or Facebook. If you cannot sign in, write to us and we will delete it for you.
If you think we got something wrong, you can complain to the Hellenic Data Protection Authority (dpa.gr), or the authority where you live. We would like to hear from you first.
Cookies
Some cookies the service needs to work: one that keeps you signed in, one that remembers you on your device if you ask it to, and one that remembers your answer to the cookie banner. We do not ask for consent to these.
Analytics cookies are set only if you accept them in the banner. They let PostHog, our analytics provider in the EU, tell your visits apart and record them, so we can see where Aemeli is hard to use. Refuse them and nothing is sent to PostHog. You can change your answer at any time from Cookie settings, in the site's footer or your account settings.
A couple's wedding website sets no cookies at all. We use no advertising cookies.
Children, changes and contact
Aemeli is for adults planning their own wedding, and not for anyone under 18.
If we change this policy, we will update the date at the top. We will tell you by email before a change that affects how we use your data.
Contact: Dimitris Kotsakos, hello@aemeli.com.