Privacy Policy
Last updated 28 October 2026
The short version
Floryn has no passwords to choose, no payments and no advertising. You type the details of a wedding into a form, get a link, and share it. That link is the invitation. Anyone who has the link can read it, so the link is the invitation — treat it as the thing you would hand out at a door.
To manage your invitation after creating it — edit details, add guests, or delete it — you sign in with the email address you provided when creating. We send a one-time link to that address; clicking it signs you in with no password. Your email is used for this and nothing else: no newsletters, no marketing, no sharing. See how sign-in works.
Invitations are not tied to a verifiable identity. If you find a record containing your name, it did not necessarily come from you — anyone can put a name on an invitation. See who can create one.
Every invitation is deleted automatically 90 days after it was created. The couple can also delete it at any moment from the dashboard: it asks once, then removes the record immediately and permanently, with no backup we can restore from and no soft-delete state, so deletion really is deletion.
We do not run analytics of any kind. Nothing on this site tracks you between pages, follows you around the web, or profiles you.
Who is responsible for your data
Floryn is operated under Sri Lankan law.
This service is run by one person, not a company. If you need to reach us about anything in this policy, use the address at the bottom. There is no formally appointed Data Protection Officer; the same address is the contact point for data subject requests.
What an invitation actually contains
These are the only fields stored for an invitation. There is no user table, no login table, and no analytics table, because there is no concept of a user.
| Invitation link | The short address in your invitation link. It is not a secret. |
|---|---|
| Bride's name | Name shown on the card. |
| Groom's name | Name shown on the card. |
| Date and time | Wedding date, times and time zone, used for the countdown, the calendar file and RSVP timing. |
| Venue name | Venue name shown on the card. |
| Venue address | Street address shown on the card. |
| Message | Your note, up to 500 characters, shown on the card. |
| Card design and colors | Which card design and color scheme you picked. |
| Guest list | The guest list you generate on the dashboard, up to 200 names, stored encoded (readable, not encrypted) so the list survives across your devices. Each entry carries that guest's RSVP answer and when they gave it, if any. |
| RSVP on or off | Whether the card shows RSVP buttons. |
| Guest message | The message you type on the dashboard to send with guest links, up to 1000 characters. Copied with the links, never shown on the card. |
| Created on | When you created it. Written by us, not by you, and used to expire the invitation after 90 days. |
| Active | Whether the record is still served. |
| The email address you provide when creating the invitation. Used only to send sign-in links you request yourself. Never shown to guests, never shown on the card, and never used for anything else. See how sign-in works. | |
| Sign-in link | Set only while a sign-in link you requested is still unused, and cleared the moment it is used or expires. A one-way hash — nobody, including us, can derive a working link from it. |
How sign-in works
To sign in to the dashboard, you enter your email address. If that address matches one on file, a one-time link is sent to it. The link works once, expires after ten minutes, and signs you into the dashboard for that invitation. No password is ever set or stored.
We respond the same way regardless of whether the address you enter matches anything on file, so this request on its own cannot confirm whether a given email or invitation exists.
Sending that email is handled by Resend, a transactional email provider — see data outside Sri Lanka. Resend sees the address the link is sent to and the link itself; it does not see anything else in your invitation.
Who can create an invitation
Invitations are not tied to a verified identity. The email on a record is not checked against who you are — it proves only that whoever made the invitation can receive a sign-in link at that address. Practically that means a name can appear on a Floryn invitation that somebody wrote about you without asking, and there is no way for us to tell from the record alone whether it was you who made it.
We do not moderate content and we cannot review every record as it is created. If a Floryn invitation names you and you did not expect it, click the Report link at the bottom of the invitation. It opens an email to [email protected] with the invitation link filled in; say that you don't want to be on this invitation. Your email address comes with the message. We will review and delete the record on request. You can also find a Delete button on any invitation you created yourself.
What is not collected
-
No email addresses from guests. The only email address Floryn stores
is the one the couple provides when creating their invitation — covered
above under
email— and it is never used for anything except sign-in links they request themselves. - No phone numbers and no physical addresses of guests.
- No IP addresses stored by us, no device identifiers, and no advertising, analytics or profiling cookies. Cookies this site sets are strictly functional and described under what is stored on your device.
- No third-party analytics, advertising pixels, session recording or heat maps.
Guest names, and why the link is the secret
Guest names are not encrypted. When you personalize a link for a guest, their name is included in the URL. The link itself is the secret — anyone who has it can see the guest's name.
The guest list you generate on the dashboard is stored with the invitation, encoded but readable, so it is still there when you sign in from another device. A personalized link itself reveals only the one name it was made for, to anyone who receives that link.
In practice this means: a personalized guest link reveals who it was made for to anyone who receives it. If that matters for your guest list, send the unpersonalized link instead. We cannot make the name private without turning every guest into an account, which would be a worse trade.
ChatGPT, if you use it
The homepage offers a link that opens ChatGPT with a prompt to help you prepare your details. Nothing is sent to ChatGPT until you open that link yourself. The chat happens on OpenAI's site, under OpenAI's own terms and privacy policy. Floryn does not receive or see that chat.
What you type into ChatGPT, such as names, dates, venue details or a message, is handled by OpenAI. Floryn receives the details you submit in our form. If you open a link that ChatGPT made for you, those details are also part of the web address when the page loads, and that address can be written to our server logs. Please do not type your sign-in email into the chat. It goes in our form, and nowhere else.
Who can see an invitation
- Anyone with the link. There is no password, no login and no per-guest access control on an invitation. This is the intended behavior, not an oversight.
- Search engines and link previews. Invitation pages ask search engines to leave them out, but not every service listens. If you want an invitation kept private, only share its link with people you trust.
- Anyone you paste the link into. Messaging apps, email and social platforms all handle the link themselves, and several of them will generate a preview of the page.
Other services that handle data on a guest's visit
These services are contacted directly by your browser while loading the page. None of them are used to track anyone across the web.
- Hosting and content delivery — Cloudflare serves the site to you and keeps its own security logs.
- Database — invitation records are stored on a private database.
- Bot protection — creating an invitation or signing in checks a Cloudflare Turnstile challenge, so your browser contacts Cloudflare's challenge servers and they see your IP address. No account or tracking is involved.
- Google Maps — only if a guest taps the venue link on the card. Nothing is sent to Google before that tap.
One more, contacted by our server rather than your browser: Resend delivers sign-in links to the email address on file. Resend sees that address and the link itself; it does not see anything else in your invitation.
What is stored on your device
Two things, both strictly functional. Neither is used to track you.
| Dashboard sign-in | A sign-in cookie set when you sign in to the dashboard. Other websites cannot read it. It expires when you sign out or after a set time. Guests never receive it — only someone signed into the dashboard does. |
|---|---|
| Guest name on this device | Local storage on a guest's own device, holding that guest's name so a personalized card still greets them if they reload. It never leaves the device and is never sent to us. Clearing site data removes it. |
How long we keep things
- 90 days. Every invitation is permanently deleted by an automatic sweep once it is 90 days old. There is no archive.
- Any time before that. The dashboard delete button asks once and then removes the record immediately, with no recovery copy.
- After deletion. The record is gone from the live database. Hosting and database providers may keep their own backups for a short period, and copies may persist in log files; we do not control that and cannot give it a fixed end date.
- Your own device. The guest list is stored on your device until you clear your browser data.
Because deletion is real and immediate, an invitation is worth recreating if you need to change it after deleting. There is no undo.
Your rights
You have the right to access your data, to have inaccurate data corrected, to withdraw consent, to object to further processing, and to have data erased. You also have the right to ask for a review of any decision made about you by automated processing.
How to make a request
Write to us with the slug from the invitation link — that is the part
after /invite/ — and say what you want. We aim to respond
within 21 working days. In practice a deletion request is actioned in
minutes.
One honest limitation: an invitation does not record who created it. The email on file proves someone can sign in to that dashboard, not that they are you, so if you never kept the link we cannot confirm whether a given slug is yours or show you who made it.
Security
This service handles a small, low-sensitivity amount of data, and the measures below are real but modest. It is not a bank and should not be treated like one.
- Deletion removes the record itself, not a hidden copy.
- Guest data is not public. Only the invitation link shows it.
- No analytics, so no cross-site tracking.
No system is perfect. If a breach affects personal data, we will notify the affected people as soon as reasonably practicable. We will not be able to guarantee a specific timeline, as that depends on decisions made under pressure.
Children
Floryn is made for weddings, and weddings involve guests of many ages. We do not knowingly collect information from children, and we collect no information directly from anyone at all — the only person who types anything in is the couple creating the invitation. If a guest is a child, their name is personal data and the same rights above apply on their behalf by a parent or guardian. Nothing on this site is directed at children or built to draw them in.
Data outside Sri Lanka
Parts of the service rely on providers outside Sri Lanka. Your data is processed outside Sri Lanka as a normal part of serving the page, under the PDPA's cross-border provisions. If you use ChatGPT, OpenAI processes what you type there outside Sri Lanka, under its own terms.
Changes to this policy
If this policy changes, the date at the top changes with it. Material changes — what we store, who sees it, or how long we keep it — will be reflected here. We do not email couples about policy changes, recovery email on file or not, so that page is the only notice you will get.
Contact
Questions, requests and complaints about this policy: write to [email protected] with the invitation slug in the subject line. For anything involving the data of a guest rather than your own invitation, we will need the slug — the email on file is tied to the couple's own access, not to anyone the invitation names, and is not an identifier we look anyone up by.