Privacy Policy

What we collect, why, and how to get rid of it.

Last updated: 29 October 2026

What we collect

• Your email address: to sign you in, send your receipt, send notices about your own invitation, and a few emails about your preview link (when the preview ends, and one last reminder before your date if you have not activated it) or about a new price or payment method in your country, which you can stop from the link at the bottom of any email or from your account page.
• Your name and phone number if you enter them on your account page (both optional), and your name and account identifier from Google or Facebook if you sign in with either.
• A WhatsApp number, if you leave it in the help card on “My invitations” so we can reach out: it is saved to your account as your phone number, with the time you asked, and we message you on it ourselves about your invitation only, never showing it to anyone. Change or remove it on your account page.
• Your invitation content: names, date, venue, and the photos you upload.
• If you add a gift option (a bank account, a wallet, a link or a QR image), we store it and show it to anyone who opens your invitation, and use it for nothing else. Koroty never receives or transfers any money between you and your guests.
• Your guests’ names, replies and wishes, if you use guest lists.
• Your review of Koroty, if you write one after the celebration of a paid invitation: the number of stars, what you wrote, and the display name and country you chose. It is published only if you agree, after we check it, with your display name and country only (never your email or your invitation title), on the home page, the reviews page and the page of the design you used. We ask for it in at most two emails after the celebration, which you can stop from the link at the bottom of any email, and you can ask us to hide your review at any time.
• An aggregate view counter per invitation, and a view count per guest link.
• An aggregate counter of the steps you take before you have an account: reaching the final review, opening the invitation full screen, opening sign-in, and which sign-in method you chose and whether it finished. It is kept as a daily count on the draft, with no identifier of you, so we can see where people get stuck and make it easier, and we send it to no third party.
• Where you first came to Koroty from: the campaign values in the link you opened (utm), whether you came from an ad, the site that referred you, the first page you opened, and the invitation you came from if you opened Koroty from a link at the bottom of an invitation. We save it with your account when you create it and with your invitation when you first publish it, to learn which of our channels bring people, and we send it to no third party.
• Your country only (not your city or address), as estimated from your internet connection when you sign in. We save it with your account once, to learn which countries our customers come from and which payment methods they lack, and we send it to no third party.
• Your device and browser type only (for example “iPhone, Safari” or “Android, inside Instagram”) and the country of your connection, at three moments: creating your account, publishing an invitation, and pressing the pay button. We store no internet address and no identifier of your device with it, and it is deleted with your invitation or account. We use it to see on which devices payment gets stuck so we can fix it, and we send it to no third party.
• Short-lived technical logs, for running the service and preventing abuse.

What we do not collect

On invitation pages your guest meets no ad pixel and no third-party cookie. Our marketing pages, home, pricing, templates, the engagement invitations page, blog, do carry the Meta pixel, for ad measurement; the next section says exactly what it sends.

Every page of the site, invitation pages included, carries Cloudflare Web Analytics, which uses no cookies and no device fingerprinting: it counts visits and measures how fast the page loads, and gives us aggregate figures (the page, where the visitor came from, browser type and country) that identify no one.

We build no ad profile of you or of your guests. Our own cookies are: language, a device token for drafts, your sign-in session, an entrance supervisor’s device token (until the day after their link ends, only for whoever opens a supervisor link), the ad click id if you came from an ad (next section), and “the invitation you came from” if you opened Koroty from a link at the bottom of an invitation, for thirty days, and “where you first came from” for ninety days; both are saved with your account if you create one (first section). On the marketing pages the Meta pixel adds one of its own.

We never see your card details. Payment happens entirely inside Lemon Squeezy; all that reaches us is a transaction id, an amount and a status.

In Jordan you can instead pay by CliQ transfer from your bank app to our account at Arab Bank. We then see, in our bank app, the amount and the name on the sending account as shown on the transfer; if you type the sender name when you tell us you have transferred, we keep it with the payment request to match the transfer.

You can also pay in USDT on the TRON network (TRC20) to our wallet. We then keep with the payment request what you send us, a screenshot of the transfer or the transaction id, and we see in our wallet the amount received and the address you sent from (transfers on that network are public by nature), solely to check the payment ourselves and match it to your invitation.

From Syria and Türkiye you can pay by Sham Cash or Syriatel Cash, from Lebanon by Whish Money, and from Egypt by Vodafone Cash, through our agent in Syria: you message them on WhatsApp, so they see your number and name as shown in WhatsApp, send the money to their wallet, then upload the transfer receipt to us, with the sending wallet’s name if you like. We keep the image and the name with the payment request to confirm the money arrived, and nobody else sees them.

Ad measurement

We advertise koroty on Facebook and Instagram. To know which ad actually brought someone who signed up, we run the Meta pixel on our marketing pages only, never on a single invitation page, because those pages belong to your guests, not to us.

In the browser the pixel sends one event: page view. If you are signed in, it also carries, hashed: your email, your account identifier, your name, and your phone number if your account has one. It is not on the payment page, not on your dashboard, and not in the editor.

The sign-up, publishing, contact and payment events, creating your account, publishing your first invitation, leaving your number for us to reach out or adding it to your account for the first time, and checkout started and payment completed with its amount, are sent from our server, not from your browser, each with its own event id so it is not counted twice. They carry, hashed and never in clear text: your email, an internal account identifier, your name as you entered it at checkout or as it appears in your account, your phone number if your account has one, and your country, city, region and postal code as entered in your billing details at Lemon Squeezy (for payments), or as roughly inferred from your IP address. Alongside them go the browser id the pixel set, the click id if you came from an ad, your Facebook account identifier if you signed in with Facebook, and your IP address and browser type at the moment of the event, all so it is attributed to the right ad, not to build a profile of you.

If you reach us from an ad that carries a click id (fbclid), we keep it in a cookie on our site for that purpose alone, for ninety days.

We never send Meta your invitation content, your guests’ names, your photos, or anything your guests write.

You can switch the browser side off: a tracker blocker or your privacy settings stop the pixel, and with it the browser id drops out of the server event. The server events themselves cannot be blocked by the browser, and they are limited to sign-up, publishing and payment.

Where it is stored

On Cloudflare’s servers. Data may be processed in data centres outside your country.

Who we share it with

• Lemon Squeezy: our merchant of record: it takes the payment, issues the invoice and handles sales tax on our behalf.
• Arab Bank: receives CliQ transfers into our account from those who pay that way in Jordan.
• Our agent in Syria: receives Sham Cash, Syriatel Cash, Whish Money and Vodafone Cash transfers from those who pay that way in Syria, Türkiye, Lebanon and Egypt, and sees your number on WhatsApp when you message them; we send them nothing about you.
• Cloudflare: for hosting, storage, sending email, and cookieless aggregate visit statistics.
• Resend and Brevo: backup email senders, used only when sending through Cloudflare is unavailable: they receive your email address and the message, solely to deliver it.
• Google: only if you choose to sign in with it.
• Facebook (Meta): only if you choose to sign in with it: we receive your name, email address and an account identifier specific to Koroty, and never post anything on your behalf.
• Meta: ad-measurement events from our marketing pages only, plus the sign-up, publishing, contact and payment events, with the data listed under “Ad measurement”.

Nobody else, and we do not sell your data to anyone.

Your guests

When a guest replies they enter their name, party size and a message. That reaches you and appears in your guest dashboard; we hold it on your behalf.

Your dashboard also shows whether a guest opened their personal link. If you turn on entry tickets, you also see when they first opened their ticket and when they were checked in at the door. Your own opens and link previews in chat apps are not counted.

If you appoint an entrance supervisor with the supervisor link, they type their name or the entrance name the first time; it appears to you next to every guest they check in, and we keep a cookie on their phone that identifies the device until the day after the link ends. The supervisor sees only confirmed guests’ names, party size, table and arrival status, not their numbers or messages, while the link works: from when you create it until the morning after the event, when it stops by itself, and you can pause it, cancel it or stop a single phone at any time.

You are responsible for telling your guests what you collect from them and what you do with it.

How long we keep it

For as long as your invitation exists. When you delete an invitation its images and its rows are removed from storage and the database within thirty days.

One small trace remains after a published invitation is deleted: a fingerprint of its link (not the link itself), so no other account can take it and reach your guests. It holds no name, no email address and none of the invitation’s content.

When a paid invitation or your account is deleted, we keep a bare financial record of each payment (amount, date and transaction number) with no name, no email address and no content, for accounting and payment disputes.

Your rights

Write to support@koroty.com from your registered address to request a copy of your data, correct it, or delete your account entirely. We reply within thirty days.

You can also delete your account and all its data yourself at any time: “My account” → “Delete account”. If you signed in with Facebook, you can remove Koroty from Facebook Settings → “Apps and websites”.

Contact

For any question about this page, write to support@koroty.com.