Back

Privacy

What we keep, why, and for how long. Short, because there is not much to tell.

Last updated 1 November 2026

Who we are

MyBouquet · Bryan Studio's

Address: Gustave Royerslaan 110, 9600 Ronse, Belgium

Email: hello@mybouquet.io

No account

You build a bouquet without signing up. We ask for no email address (unless you ask for a reminder by email yourself or withdraw from a purchase, see below), no password and no phone number. The person receiving it does not sign up either.

A bouquet belongs to a link with a hard-to-guess code. Whoever holds the link can see the bouquet.

What you add yourself

Your message, the names you fill in, the text on the ribbon, a photo, a voice recording and what the bouquet is for (if you pick it). We store that content so we can show the bouquet. We do not read it, do not use it for advertising and do not pass it to anyone.

Photos and audio sit in encrypted storage and are reachable only through the bouquet's own link.

For the preview of your link in apps such as WhatsApp, your browser makes a picture of the bouquet, with the ribbon but without names or message, and we keep it with the bouquet until the bouquet itself is deleted.

What we record

When a bouquet was made, paid for and first opened. That lets us show you whether yours has been seen, and lets us act against abuse. If your browser tries to make a new bouquet more than once (on a slow connection, for example), the page sends the same random code each time, so that only one bouquet is made; the bouquet keeps that code, made unreadable, for at most two days.

We also count, per day and per size, how many bouquets are made, sent, paid for and opened, and how far a new bouquet gets in the builder. That shows us where the site can be better. For this a bouquet only keeps the furthest step it reached, whether it counts, and for thirty days the version of the builder it was made in. Bouquets made by search engines and other automated programs, bouquets we make ourselves to test the site, and many new bouquets within one minute from the same internet address are not counted; if someone does go on with such a bouquet, it counts after all. We tell them apart by the name the browser gives itself, by the signal that a browser is being driven by a program, by the number of new bouquets per minute (we do not keep the internet address for this) and by a cookie on our own devices. The counts themselves hold no name, no IP address and no cookie. Legal basis: our legitimate interest in improving the site.

Per day we also count how often a small offer on the site is shown and tapped, such as “Keep for 10 years” or a premium vase, and how often the banner about the TikTok pixel appears by itself and what people choose there (we do not keep who chose what; your choice itself is stored only in your browser), and on the builder's first screens how often the first question comes into view (on a fresh load of the page or after a reload), which reason for a bouquet people pick and whether they then change a flower or the size, how long it takes after that choice before your bouquet is ready and whether that fails, and how often someone uses ‘Open in browser’ in an app and whether the bouquet then carries on in another browser, and on the overview before paying how often it comes into view, whether people tick the box, open the terms through the link next to it and tap the pay button (also without the tick), whether Stripe's payment page opens (and if not, whether they try again) and whether they come back from it, and whether they go back to an earlier step, each time noting whether the visit came from an ad. These counts hold no name, no IP address and no cookie. Legal basis: our legitimate interest in improving the site.

From the technical description your browser sends with every request (the user agent), our server works out what kind of browser it is: the TikTok app on an iPhone or on Android, another app, a browser on a phone or on a computer, or an automated program. We do not keep that description itself. If a request comes from a data centre's network (such as Amazon's, Google's or Microsoft's: we tell that from the network's number, which our hosting partner Cloudflare derives from the internet address, and we do not keep that number), or from a browser on a computer outside Europe that arrived without a referring site (we tell that from the country Cloudflare derives from the internet address), we count the visit and what happens on the screens as an automated program's; a bouquet you make that way only counts once you go past the flowers. We also count the visits, the bouquets started and the builder's screens per kind of browser, and a new bouquet keeps that kind for at most two days. That shows us whether the site stumbles on a particular device. Legal basis: our legitimate interest in improving the site.

On the home page and on the page where you make a bouquet, the page itself keeps a few simple details, only in its memory, about that one time it was loaded, each a yes or a no: whether it became ready to use and whether that happened in the background, whether you touched the page, whether a tap on a reason did nothing, whether you picked a reason or tapped a button to the builder, whether the flower step came into view and which kind of error occurred, and also roughly how long it was in view (under 5 seconds, up to half a minute, up to two minutes or longer) and whether it opened a bouquet already started. When you leave the page or it goes to the background, your browser sends these details to our server once, and at most once more if you come back after that. The message itself contains no code that recognises you or your visit and not the address of the page. As with every request to our site, your browser may still send its cookies for mybouquet.io and the page address along with it; our server does not read them and does not keep them, except in the short technical logs described further on. Our server keeps them only as totals per day, per page and per kind of browser: the TikTok app on an iPhone, the TikTok app on Android, or anything else. If a finished day has fewer than five loads in one of the two TikTok browsers, we add them to “anything else”; if “anything else” stays under five that day, we erase that count. Besides this, every page reports once per kind of error that an error occurred, the home page and the builder report that they were ready to use, and the builder reports whether making a new bouquet was slow or failed; we count these reports per day and per kind of browser, noting whether the visit came from an ad. That shows us whether the site works in the TikTok app and where it stumbles. Legal basis: our legitimate interest in improving the site.

We also count where visitors come from: which site or app (for example TikTok, Instagram or Google), whether that was through an ad and, for an ad, which one: the label in the ad's link (utm_content, for example the name of a video; nothing about you). Your browser works this out from the address of the link and the page you came from, and for this count sends us only that source and that label, not the address itself (during a test of the first page our server does read the ad code in the address, see below). We do not keep the click code TikTok adds to the link (ttclid). For this we set no cookie and store nothing in your browser. We count it per day, and a new bouquet keeps that source, and that label for thirty days. If you use ‘Open in browser’ in an app to carry on in another browser, or open the address of a bouquet that began in the app in another browser, you start a new bouquet there with the same source and a marker in the address (utm_via). You are not counted as a visitor again there, and next to the source the new bouquet only keeps that it started that way, for thirty days (and, during a test of the first page, the version; see below). We also count which kind of page you arrived on (the home page, the page where you make a bouquet, a page about a flower or an occasion, the guide or the example) and whether a new bouquet began there. If you go from such a page to the page where you make a bouquet, the link takes that kind of page, the source and whether it was through an ad along in the address (utm_entry), because your browser forgets them on that step; that page takes the marker out of the address straight away. If you already pick the reason for your bouquet with a button on the home page or on such a page, we count that choice and where the button was. That shows us which channels and ads work. Legal basis: our legitimate interest in improving the site.

Sometimes we test which first page helps visitors from a TikTok ad most: straight into the page where you make a bouquet, or the home page first. During such a test our server reads the ad code in the address (ttclid) to give you one of the two versions; that way the same click always gets the same version. We do not keep that code. To count a click that comes back within a minute only once, our hosting partner Cloudflare remembers an unreadable form of it for one minute. The version is then in the address of the page (utm_arm, for example b3), and your browser sends it along with a new bouquet and with two reports: that you arrived on the page, and whether you took a first step there (picking a reason, or going on to the page where you make a bouquet). Per day, per version and per kind of browser we count how many visitors got a version and those reports, and per version how far the new bouquets get: made, past the flower step, the overview, Stripe's payment page, sent, paid with money. For this a new bouquet keeps the version until thirty days after the test stopped. Automated programs, our own devices and many visits within a minute from the same internet address are counted separately or not at all (we do not keep the internet address for this). If you tap before the page is ready, our server takes the ad codes for the form of the first question from the address of our own previous page, which your browser sends along; we do not keep that either. These counts hold no name, no IP address, no cookie and no ad code. Legal basis: our legitimate interest in improving the site.

While you are on the site, your browser tells us about every half minute which page or which step of the builder you are on, so we can see how many people are here right now and where they get stuck. For this the page uses a random code that exists only in its memory; we store nothing for it in your browser. Our server adds the city and country that our hosting partner Cloudflare derives from your IP address; we do not keep the IP address itself, and we round the place to about ten kilometres. As soon as you leave the site your visit no longer counts, and we delete this data within a day at the latest. We also count per day and per city how many visitors arrive and how many bouquets are started, and a new bouquet keeps the country it was started in. On the overview before paying, the builder also uses the country of that moment to show which ways to pay work there, such as iDEAL | Wero in the Netherlands; we keep nothing for that. Legal basis: our legitimate interest in improving the site.

Would you rather not be counted? Tick “Don't count my visits” under Cookie settings at the bottom of the page, or turn on Global Privacy Control in your browser. Your browser then sends us none of the counts above, with one exception (a new bouquet, see below): no visit, nothing about the builder's screens, the offers or the banner, nothing about loading or leaving a page and no error reports, and not that you are on the site. “Don't count my visits” is stored only in your browser, so during a test of the first page our server still counts that you got a version: that happens when the page opens, before your browser can tell us anything. Global Privacy Control, however, is sent along by your browser when the page opens; then we do not count that either. If you then make a bouquet anyway, it still counts as made, and so does how far it gets in the builder, with its source (for example TikTok), whether it came through an ad, the city and the country, the version of the builder and whether it started through ‘Open in browser’, as described above, but without the kind of browser, without the ad's label and without the version from a test.

If, before paying, you tick the box to agree to our terms or the box that lets us deliver your bouquet, code or an extra right away (or buy “Keep for 10 years”), we keep the time, the version of the text you saw, the language and the version of our terms. That is our proof of your choice. Legal basis: our legal duty to keep accounts for the payment, and our legitimate interest in being able to show your choice, because the law puts that burden of proof on us (Article VI.62 of the Belgian Code of Economic Law). We keep it with the details of your payment (time, amount and payment method) for as long as we need to be able to show your order and the accounting rules require it. We do not erase those details automatically.

Our servers keep short technical logs, such as IP addresses on errors. Those are gone within thirty days.

Payments

Payments run through Stripe. Your card details never reach our servers; we are told only whether the payment succeeded. Stripe processes those details as its own controller.

Stripe asks for your email address, among other things so it can send you a receipt. We do not store it in our own database, but it is kept with your payment in our Stripe account, where we can see it, for example for a refund or a question. If Stripe makes an invoice, a customer record is added as well.

If you add recipients after paying, their names are also kept with that payment until it has gone through. After that they are only kept with the bouquet and go when the bouquet goes; if the payment fails, we erase them at once.

Sending again, reminders and your home screen

With ‘Send this bouquet again’ your browser starts a new bouquet with the same size, the same vase and the same flowers, and the text on the ribbon. That new bouquet keeps, as its source, that it started this way, just like a bouquet you start from a reminder or from the icon on your home screen (see ‘where visitors come from’ above).

If you put a reminder in your calendar, our server makes the calendar file from the address of the link and keeps nothing of it; the reminder is then only in your own calendar. If you choose Google Calendar, a Google page opens with the day, a title and the link filled in; what Google does with that is covered by Google’s privacy policy. The link in a reminder holds only the size, the vase and the flowers of your bouquet: no names, no text and not the address of your bouquet.

If you ask for a reminder by email, we keep your email address, the day you chose, the language, the size, the vase and the flowers of your bouquet, and the version of this text. We first send one email to confirm the reminder; without a confirmation we erase everything within a week. On the day you chose we send one email and then erase everything; if sending fails, we try again on at most two more days. With the link in the first email you can stop the reminder at any time, and we then erase it at once. To limit abuse, we keep at most three reminders open per address. Our hosting partner Cloudflare sends the emails for us, as a processor. Legal basis: your consent (Article 6(1)(a) GDPR), which you can withdraw at any time by stopping the reminder.

If you put MyBouquet on your phone’s home screen, there is only an icon on your device: we hear nothing of it, except that a visit through that icon counts as a source. On an iPhone that icon has its own cookies and storage, separate from Safari.

Withdrawing

If you withdraw from a purchase with “Withdraw from contract here”, we keep what you filled in (your name, what identifies the purchase and your email address), the language, the time, whether the acknowledgement of receipt went out and when we handled the withdrawal. If what you filled in identifies a payment, we note which one. We send you an acknowledgement of receipt by email straight away, and ourselves a notice with the same details. Our hosting partner Cloudflare sends the emails for us, as a processor. Legal basis: our legal obligation to receive, acknowledge and handle your withdrawal (Article 6(1)(c) GDPR). We erase this two years after your withdrawal.

Cookies and storage in your browser

We use what the site needs to work. Something to measure our ads, such as the TikTok pixel, is only added if you allow it.

One cookie per bouquet lets you, and only you, edit your bouquet and open the page with your links. It is kept for thirty days while the bouquet is unpaid, and for a little over a year after that. If you buy credit, a cookie remembers for thirty days that you are the buyer, so you can find your code again. If you pick a language yourself, a cookie remembers that choice for a year, so the home page opens in that language next time. On the site owner's own devices, a link from our admin page sets a cookie (bloei_intern, 400 days) that keeps those devices out of the counts; visitors never get this cookie.

In your browser itself we remember whether you turned the music off, what you chose about the TikTok pixel and whether you ticked “Don't count my visits”, and, only for the tab you are working in, a few technical details such as a credit code you are using, which bouquets you have already opened and, when you start a bouquet from one you received, the name of the person who sent it, so we can fill it in for you.

The TikTok pixel

On the home page, on the page where you make a bouquet and on the legal pages (privacy, terms and legal notice) we use TikTok's pixel, but only if you agree to it in the banner. It lets us measure whether our ads on TikTok work: how many people come to the site after an ad. TikTok also uses the same data itself: to improve the delivery of ads and to personalise ads, including for you on TikTok if you have an account there.

On the page where you make a bouquet, TikTok sees the address with the number of your draft and the step you are on, but never your manage link or a credit code; what you write in or upload to the bouquet we do not give to TikTok. Never on the pages where you manage your bouquet after paying or view it, and not in the credit shop: the address of those pages can hold a secret code, and TikTok never gets to see it. If you go from a page with the pixel to one of those pages, or the other way round, your browser loads an entirely new page. If you opened or paid for a bouquet or used a credit code in a tab, your browser keeps a code for it in that tab, and the pixel no longer loads in that tab.

If you agree, TikTok receives from your browser, among other things, your IP address, details about your browser and device, the address of the page (with an ad code such as ttclid, if there is one, and during a test of the first page which version of the page you got: utm_arm), what you click on that page and a cookie ID. For that, TikTok sets these cookies on our site: _ttp (recognises your browser), ttcsid and ttcsid_ followed by the pixel's code (your visit), ttclid (the ad you clicked) and _tt_enable_cookie (whether cookies work). They stay for up to 13 months after they were last used. TikTok also keeps data in your browser's storage, and may read and set cookies of its own: _ttp on tiktok.com and _pangle on analytics.pangle-ads.com (TikTok's ad network), also for up to 13 months. If you then pay through Stripe, our server reports that purchase to TikTok: the size, the amount and the cookie IDs _ttp and ttclid, without your name, your email address or the address of your bouquet.

The data goes to TikTok Technology Limited in Ireland and TikTok Information Technologies UK Limited in the United Kingdom, which according to TikTok's privacy policy are jointly responsible. The United Kingdom is outside the European Economic Area, and TikTok may also process the data in other countries outside it. We and TikTok are jointly responsible for collecting the data and passing it on (Court of Justice of the EU, case C-40/17, Fashion ID); what TikTok does with it after that falls under TikTok's own privacy policy, and that is also where you can exercise your rights.

Legal basis: your consent (Article 6(1)(a) GDPR and, for the cookies and the access to your device, Article 10/2 of the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data). Declining changes nothing about what you can do on the site.

We remember your choice in your browser for six months; after that we ask again. You can change or withdraw it at any time with the Cookie settings button at the bottom of the page or next to the links to this text. If you withdraw your consent, we erase TikTok's cookies on our site and reload the page, without the pixel. We cannot erase TikTok's cookies on tiktok.com and pangle-ads.com: you can do that in your browser or with TikTok.

How long

A bouquet stays up for a year, counted from the payment or the scheduled delivery date, whichever is later; if you buy “Keep for 10 years”, ten years. After that we automatically erase the photo, the audio, the message and the names.

What a bouquet keeps about how it was counted is erased by itself: the kind of browser within two days, the ad, the version of the builder and whether it started through ‘Open in browser’ thirty days after the bouquet was made. The code your browser made a new bouquet with is erased within two days as well. The version of the first page from a test is erased thirty days after that test stopped. Whether a bouquet counts stays as long as the bouquet does. The daily counts themselves hold nothing about you and are kept.

Want one gone sooner? Send the link to hello@mybouquet.io and ask, and we will take it down within a week.

Your rights

You may ask what we hold, have it corrected, or have it erased. Write to hello@mybouquet.io for that. Because there is no account, we need your bouquet's link to do it.

If you disagree with how we handle this, you can complain to the Belgian Data Protection Authority.