Last updated · November 17, 2026
Privacy Policy
This policy explains what information Find for Event collects, why we collect it, who else sees it, and the choices you have. The short version: we collect what the platform needs to work, we do not sell it, and we use no advertising networks or tracking.
Who we are, and how to reach us
Find for Event is operated under the domain findforevent.com. We are the controller of the personal data described in this policy. No company is registered behind the platform at present; you can reach us at hello@findforevent.com or +374 98 688548.
For any privacy question or request, write to hello@findforevent.com.
What we collect
Usage analytics. When you browse Find for Event we record the pages you visit and your interactions with vendor profiles — views, contact clicks, favourites — together with a randomly generated visitor identifier, the country your request came from, and the page that referred you. If you reach us through a link we have tagged for one of our own campaigns, we also record that campaign tag, so we can tell which announcement brought you here. The country is worked out on our own server from your IP address, using the GeoLite2 database created by MaxMind (https://www.maxmind.com); the address goes to no one else for this. We do not store your IP address with these events, and the identifier is not linked to your name or to any account.
Vendor account details. If you register as a vendor we store what you provide: your name, contact details, the content of your listing, and the hash of your password (never the password itself). If you sign in with Google we receive your name, email address, Google account identifier and profile picture from Google.
Planner account details. If you create an account to plan an event we store your name, email address and the hash of your password, or, if you sign in with Google, what Google tells us (see above).
What you enter in the planner. Your events and what they hold: guest lists (names, and where you add them, phone numbers, email addresses, dietary needs and notes), seating, tasks, budget, payments to vendors and gifts. A guest list holds other people's data: you decide what goes in it, and we process it only to run the planner for you. As you use the planner we also note against your account that certain steps happened, and when — an event created, a vendor added, an order paid — to understand how the planner is used; these notes hold no names, contact details, guests or gifts.
Invitations and guests' answers. What you put on an invitation: names, texts, photos and a song, if you upload one. When a guest answers, we store the names they give for themselves and for anyone coming with them, their answer, the side that invited them and any message they write. We count how many people open an invitation each day, using the anonymous visitor identifier.
Orders. When you order Event Pro we store the order: the event, the price, the contact details and message you give us, and when it was paid.
Records of agreement. When you accept our Terms of Service, Vendor Agreement or Privacy Policy, we store which documents and versions you accepted, when, in which language, and the IP address and browser the acceptance came from. This record exists so that both sides can prove what was agreed.
Messages you send us. If you write to us — by email, on WhatsApp or through the feedback form — we keep the correspondence so we can deal with it and refer back to it. With a message from the feedback form we also store the page it was sent from, your browser and screen size, and your account if you were signed in. A screenshot you attach is passed on to our team and is not kept on our servers. With a request for planning help we store your name, the contact you leave, what you tell us about your event, the page it was sent from, and your account and event if you were signed in.
Technical records. Like any website, our servers receive your IP address and browser details with every request. We use the address to work out your country, as described above, and to limit repeated attempts at signing in or sending a form. It also appears in the web server's log, which is kept for a short time for security and troubleshooting and is then overwritten.
Why we use it, and on what legal basis
To run your vendor account and publish your listing — because it is necessary to perform the Vendor Agreement between us.
To run your planner account, the planner and your invitation, and to handle your Event Pro order — because it is necessary to perform our agreement with you (the Terms of Service).
To pass a guest's answer to the people who sent the invitation — which is what the guest is answering for — because they and we have a legitimate interest in organising the event.
To keep a record of the agreements you accepted — because we have a legitimate interest in being able to prove what was agreed, and in some cases a legal obligation to keep records.
To operate and improve the marketplace, to measure how it is used, and to show vendors anonymous statistics about their own profiles — because we have a legitimate interest in understanding and improving a service we provide. You can object to this at any time on the Cookie Settings page, which switches analytics off for your browser.
To keep the platform secure and to prevent abuse — because we have a legitimate interest in doing so.
To answer your messages — because we have a legitimate interest in responding to people who write to us.
We do not sell personal data, we use no advertising networks, and we do not use your data to build profiles of you or to make decisions about you by automated means. A sponsored banner on the site is a picture and a link, shown the same to everyone and marked as such.
What stays on your device
Your theme and other display preferences — how a list is laid out, which sections are folded — stay in your browser's local storage. So does your favourites list while you are signed out; when you sign in to a planner account it moves to the account, so you see it on every device. When you favourite a vendor an anonymous event is recorded so the vendor can see how their profile performs.
Content embedded from other companies
Some pages include content served directly by other companies. We keep this to a minimum, and every instance of it is listed here.
Google Maps. Vendor profiles that have a map, the churches page, and invitations whose hosts chose to show the place on a map, embed a map from Google. When such a page loads, Google receives your IP address and browser information and may set its own cookies in that frame. If you use “Near me” on the churches page, your location is passed to that map; it is not sent to us.
YouTube. Vendor portfolio videos are embedded from YouTube. A video's preview picture is loaded from YouTube together with the page, and the player — in YouTube's privacy-enhanced mode — when you open the video; in both cases Google receives your IP address and browser information.
Sign in with Google. If you choose to sign in with Google, Google processes that sign-in and tells us your name, email address, account identifier and profile picture.
These companies act as controllers of the data they collect through their own content, under their own terms and privacy policies, and we cannot control what they do with it. We use no advertising networks, no analytics products belonging to other companies, and no cross-site tracking of our own.
Who else sees your data
The hosting and infrastructure providers that run our servers and deliver our pages, which process data on our instructions and only to provide that service.
The companies whose content is embedded in our pages, as described above.
Anyone, in the case of the information you publish in a vendor listing — that is public by design.
The people you plan an event with, who see that event in the planner.
Anyone with the link to a published invitation, who sees what you put on it.
Anyone with the link to an event's table finder, if the planners switch it on: entering a guest's name shows where that guest sits.
Email: the messages we send, such as password resets, go out through Google's Gmail, and mail to our addresses is forwarded by Cloudflare.
Messages you send us through the feedback form, with a screenshot if you add one, reach our team through Telegram. Requests for planning help reach our team the same way.
Public authorities, where the law requires us to disclose something.
We do not share personal data with anyone else.
Where your data is stored
Our database and uploaded files are held on servers rented from commercial hosting providers. At present they are in a data centre in Frankfurt, Germany. Where data is transferred to a country outside the one you are in, we rely on the safeguards available under applicable law — including, where the GDPR applies, the European Commission's standard contractual clauses. The embedded content described above is served by companies that operate globally.
How long we keep it
The visitor cookie lasts one year.
Analytics events are kept for as long as they are needed for vendor statistics and product decisions, and in any case no longer than 24 months.
Vendor account data and listing content are kept while the account is active, and removed within 90 days of the account being deleted, except where we must keep something for longer by law.
Planner accounts and what they hold are kept while the account is active, and removed within 90 days of the account being deleted.
A published invitation's photos, song and texts are deleted twelve months after the event's date; the guests' answers stay with the event.
Event Pro orders are kept for as long as we are required to keep records of payments.
Records of agreement are kept for three years after the account is closed, because their purpose is to remain available if what was agreed is ever questioned.
Backups of the database and files are kept for up to 28 days, so something we have deleted can remain in a backup for that long before it is gone for good.
Your rights
You may ask us for a copy of the personal data we hold about you, to correct it if it is wrong, to delete it, to restrict or object to how we use it, or to receive it in a portable form. Where we rely on your consent you may withdraw it at any time, and where we rely on legitimate interests you may object.
Write to hello@findforevent.com and we will respond within one month. There is no charge.
If you are not satisfied with our answer, you may complain to a data protection authority: in Armenia, the Personal Data Protection Agency of the Ministry of Justice; in the European Economic Area, the supervisory authority of the country where you live or work.
Children
Find for Event is not intended for children. Accounts require you to be at least 18, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, write to hello@findforevent.com and we will delete it.
Guest lists and invitations may name children who are invited. The people planning the event decide that, and the same rules apply to it.
Changes to this policy
We may update this policy as the platform develops. Each version carries the date it took effect. Where a change is material we announce it on the site, and account holders are asked to accept the new version.