Privacy policy
What Flogift collects, why it is needed and who receives it.
Last changed: September 20, 2026
What this document is
Flogift is a flower ordering and delivery service. To get a bouquet to someone we need data: who to deliver to, where and when. This page says exactly what we collect, what for, and who it reaches.
It describes what the system actually does. If anything here disagrees with how the service behaves, the service is the truth and this page is a mistake to be fixed.
Your data
A phone number or an email — whichever you sign in with. Without it the service cannot tell you apart from anyone else or show you your orders.
Your name, city and profile photo, if you provided them. The shop assembling your bouquet sees your name: it is the shop that calls you when something goes wrong.
If you sign in with Google, Apple or Telegram, we receive an identifier from them plus a verified email or phone. Your password for those accounts never reaches us.
Recipient data belongs to a third person
Flowers are almost always bought for someone else. So along with the order you give us the recipient's name, phone number and address, and sometimes the text of a card.
That is data about a person who told us nothing and may never have heard of us. We pass it only to the shop and the courier, and only to deliver — never for mailings, never to anyone else.
By giving us someone else's phone and address you confirm you are entitled to. If the recipient asks us to delete their data, we will.
Order data
What was ordered, the amounts, the delivery window, the card text, the photo of the assembled bouquet and your answer to it, and the review after delivery.
Order lines are a snapshot taken at purchase. The shop may change its prices tomorrow; your order from yesterday stays as it was, so it can still be checked a year later.
Payment: we never see your card
Payment goes through the bank by QR code. Card or account details are entered inside your bank's own app and never reach us — we learn only the amount, the time, and whether it was paid.
We run no payment processing of our own and are technically unable to store payment credentials.
Who we share with
The shop assembling your bouquet — your name and phone, the recipient's details and the contents of the order. Without these it can neither assemble nor deliver.
The bank — the amount. It does not learn from us who bought what.
Google, Apple or Telegram — only if you chose that way of signing in, and only to confirm the account is yours.
There are no ad networks, analytics counters or data brokers on this site. We sell nothing to anyone.
Cookies and browser storage
One cookie — your session. It is bound to a single site name and does not travel to neighbouring ones; sign out and it dies.
Your browser keeps your chosen theme and language, and — before you sign in — your basket and the key to an order you placed as a guest. That is your browser, not our server: clear it and they are gone.
We set no advertising or tracking cookies.
How we protect it
Passwords are stored as an irreversible hash: it cannot be read back, only checked against what you type. Session keys are hashed too — a leaked copy of the database lets nobody sign in as anybody.
Every change to data is written to a log: who, what and when. The log cannot be edited, only appended to.
Sign-in codes live five minutes and die the moment a correct one is entered.
How long we keep it
Account data — for as long as the account exists. Order history — longer: it is an accounting record, both for us and for the shop.
Deleting your account removes your profile and address book. Orders remain but stop being linked to you.
Your rights
You can see your data in the cabinet, correct it there, delete your account, and ask us to explain where something came from.
Sign-in methods can be unlinked one by one — except the last one: unlinking that would lock you out of your own cabinet.
To use any of these rights, write to us — see below.
Children
The service is meant for adults. We do not knowingly collect children's data; if we learn that we have, we delete it.
Changes
We may change this document. The date of the last edit is at the top of the page; significant changes we will show in the cabinet rather than quietly swap the text.