Cookie Policy
Last updated: 8 October 2026 · the French version is authoritative.
Cookie Policy
Last updated: 8 October 2026.
The French version is the legal and original version; the NL/DE/EN versions are courtesy translations; in the event of any discrepancy, the French version prevails.
At bloo.Cards (a digital business card platform published by Molderez-Consult SRL), we respect your privacy. This Cookie Policy transparently explains the trackers we actually use on our platform, the legal basis for placing and reading them, as well as how you can control your preferences.
In this document, we clearly distinguish two technical mechanisms that are often confused:
- cookies in the strict sense (small files automatically sent back to the server);
- the browser's local storage (localStorage), which remains on your device and is not automatically transmitted to the server.
This policy is established in accordance with:
- the ePrivacy Directive 2002/58/EC (amended by Directive 2009/136/EC): protection of access to terminal equipment and tracking, Article 5(3);
- the General Data Protection Regulation, GDPR (Regulation (EU) 2016/679), in particular its Articles 6, 7 and 12 to 22, for the processing of personal data;
- the Belgian Act of 13 June 2005 on electronic communications (Article 129), which transposes the ePrivacy Directive into Belgian law;
- the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data;
- the recommendations of the Data Protection Authority (APD).
Contents
- Definitions and fundamental concepts
- Inventory of trackers actually used
- Browser local storage (localStorage)
- Third-party and partner cookies
- Legal bases
- Consent management
- Your rights and your control
- Disabling cookies from your browser
- Contact
- Language and language primacy
- Change history
1. Definitions and fundamental concepts
What is a cookie?
A cookie is a small text file placed on your device (computer, smartphone, tablet) when you visit a website. It generally contains an identifier or a value, an expiry date and the domain that created it. On each subsequent visit, your browser automatically sends the cookie back to the server, which makes it possible to recognise you or to remember certain actions.
Types of cookies according to their lifespan
| Type | Definition | Typical duration |
|---|---|---|
| Session cookie | Automatically deleted when the browser is closed | Duration of the session |
| Persistent cookie | Kept on the device for a defined period | From a few hours to several months |
| Third-party cookie | Placed by another domain (provider, integrated service) | Depending on the third party |
Types of cookies according to their purpose
- Essential / strictly necessary: indispensable to the operation of the site (session, security, storing the consent choice);
- Functional: improve the experience (language, theme preferences);
- Analytical: measure the audience and usage of the site;
- Marketing / advertising and social media: tracking for advertising purposes, not used to date by bloo.Cards (see section 2).
Cookies and local storage: an important distinction
In addition to cookies, a site may use the browser's local storage (localStorage). Unlike a cookie, data in localStorage is not automatically transmitted to the server on each request: it remains on your device and is only read by the page's code. On the website and the cards, bloo.Cards uses localStorage to store two interface preferences (language and theme) and, on public cards, information related to the features you use (chat, contact details form, document viewer); the Wallet application also keeps there what is strictly necessary to work offline. These elements are detailed in section 3 and are deliberately not presented as cookies, in order to faithfully reflect the technical reality.
2. Inventory of trackers actually used by bloo.Cards
This inventory reflects the trackers actually deployed in production. It does not describe any theoretical or non-installed tracker.
Category 1: essential cookies (strictly necessary)
Legal basis: Article 5(3) of the ePrivacy Directive (exemption for strictly necessary trackers) and Article 6(1)(f) of the GDPR (legitimate interest). Consent required: no.
| Name | Party | Purpose | Category | Duration |
|---|---|---|---|---|
| bloo_session | bloo.Cards (first party) | PHP session cookie. Maintains the state of your session between requests (login, form security). Placed with the Secure, HttpOnly and SameSite=Lax attributes. Without it, authentication and forms do not work. | Essential | Up to 4 hours after your last activity |
| bloo_wdev | bloo.Cards (first party, limited to blcrds.com, path /api/) | Wallet device cookie. Placed when you link your phone to the Wallet from the backoffice, it keeps that phone signed in to the Wallet. It contains the device identifier and a random token; only a hash (SHA-256) of the token is kept on our servers. Placed with the Secure, HttpOnly and SameSite=Lax attributes. It stops working as soon as you revoke the device in the backoffice and is erased when you log out of the Wallet. | Essential | 90 days |
| bloo_rs_ref | bloo.Cards (first party, limited to blcrds.com) | Partner reseller link. Only set when you open a reseller's sign-up link (address containing "?reseller="); it only contains that reseller's code, so that your account is attributed to them if you create it before closing your browser (see the Privacy Policy, Article 5.6). The reseller is shown on the page before any sign-up. Set with the Secure, HttpOnly and SameSite=Lax attributes; deleted as soon as the account is created. | Essential (requested service: sign-up through the reseller) | Browser session (deleted when the browser is closed or as soon as the account is created) |
| bloo-consent | bloo.Cards (first party, cookie + local storage) | Stores your choice (accept or refuse audience measurement) so as not to redisplay the banner on each visit. | Essential | 6 months |
| bloo_oauth_n | bloo.Cards (first party, limited to blcrds.com, path /api/auth/) | Sign-in or sign-up with Google or LinkedIn. Set when you choose to sign in with Google or LinkedIn, it contains a random single-use code used to check, when you come back, that the sign-in was indeed requested from your browser (protection against forged requests). It is deleted as soon as you come back. It is not used when the sign-in starts from the Wallet application. Set with the Secure, HttpOnly and SameSite=Lax attributes. | Essential | At most 10 minutes (deleted when you come back from Google or LinkedIn) |
| bloo_reg | bloo.Cards (first party, blcrds.com) | E-mail sign-up. Set when you create an account, it contains a random code that links the verification code received by e-mail to the browser used to sign up: the chosen password is only activated if the verification happens in that same browser (protection against account takeover by a third party). Deleted as soon as the verification is done. Set with the Secure, HttpOnly and SameSite=Lax attributes. | Essential | At most 2 hours (deleted once verified) |
| bloo_studio | bloo.Cards (first party, limited to blcrds.com) | "Studio" editing session of the CORPORATE offer. Only set when a studio session is opened from the administration console with a single-use link; it keeps this separate session, limited to the company's master card, without changing your usual session. Deleted when the studio is closed or expires. Set with the Secure, HttpOnly and SameSite=Strict attributes. | Essential | 60 minutes |
| bloo_rs_brand | bloo.Cards (first party) | Former reseller display cookie (logo and name), no longer set since 30 September 2026 and never used to attribute an account. If it remains in your browser from an earlier visit, it is ignored, then deleted as soon as it is sent back to us (sign-up and sign-in pages). | Essential (former cookie, being deleted) | No longer set; deleted on your next visit to a sign-up or sign-in page |
Category 2: analytical cookies (audience measurement)
Legal basis: Article 5(3) of the ePrivacy Directive (consent) and Article 6(1)(a) of the GDPR (consent). Consent required: yes. By default, no analytical cookie is placed: audience measurement is only activated after your explicit acceptance (see section 6, Google Consent Mode v2).
| Name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| _ga | Google · Google Analytics 4 (first-party cookie placed by the Google script; data transmitted to Google) | Statistically distinguishes visitors in order to measure the audience and usage of the site. Placed only after your consent. | Analytical | 13 months |
| _ga_<ID> | Google · Google Analytics 4 (first-party cookie placed by the Google script; data transmitted to Google) | Maintains the state of the audience-measurement session. Placed only after your consent. | Analytical | 13 months |
Trackers that bloo.Cards does NOT use to date
To be perfectly transparent, we specify that bloo.Cards does not currently deploy:
- marketing or advertising cookies;
- remarketing or targeted advertising;
- social media pixels (for example Meta / Facebook Pixel);
- "in-house" analytics cookies (internal behavioural profiling);
- automated profiling based on cookies alone.
Should any of these uses be introduced in the future, this policy would be updated and your prior consent would be sought, category by category.
Summary of trackers
| Category | Trackers | Mechanism | Consent |
|---|---|---|---|
| Essential | bloo_session, bloo_wdev, bloo_rs_ref, bloo-consent, bloo_oauth_n, bloo_reg, bloo_studio | Cookies (first party) | No |
| Functional | bloo-lang, bloo-theme, bloo-fx-cur | localStorage (first party), see section 3 | No (interface preference, without personal data) |
| Wallet operation | bw-ids, bw-active, bw-loy, bw-lang, bw-loyNotice, bw-intent; offline cache | localStorage and browser cache (first party, Wallet application), see section 3 | No (strictly necessary for the service requested) |
| Functional (public cards) | bloo_lang; bloo-chat:<card>, bloo-chat-lang, bloo_visitor, bloo_lead_sent_<card>, bloo_pdf_sound, bloo_pdf_hint; blooCh, bloo_lead_skip_<card>, bloo_notif_<…> | bloo_lang cookie, localStorage and sessionStorage (first party), see section 3 | No (only set when you use the feature concerned) |
| Embedded third-party content | YouTube and Vimeo videos, content from other sites and Google Maps maps placed by a card holder | Cookies and storage of the third-party service, only after your click, see section 4 | Yes (your click) |
| Analytical | _ga, _ga_<ID> (Google Analytics 4) | Cookies (placed after consent, refused by default) | Yes |
| Marketing / advertising / social media | None (not used to date) | - | - |
3. Browser local storage (localStorage)
On the website and the cards, bloo.Cards uses localStorage to store your interface preferences (language and theme). This is indeed local storage, not cookies: these values remain on your device, are not automatically transmitted to the server and contain no data enabling you to be identified.
| Key | Storage type | Purpose | Content | Duration |
|---|---|---|---|---|
| bloo-lang | localStorage (first party) | Stores the display language you have chosen (fr, nl, en, de, it, es, pt). | Language code (2 characters) | Until manually erased (browser settings) |
| bloo-fx-cur | localStorage (first party) | Stores the currency you have chosen to show prices for guidance (Pricing and home pages). You are still invoiced in euros (EUR). | Currency code (3 characters) | Until manually erased (browser settings) |
| bloo_lang | Cookie (first party, public cards, mybloo.cards) | Stores the language you chose to display the cards. Only set when you choose a language (the card's language selector or a link containing this choice); otherwise the card is displayed in your browser's language. | Language code (2 characters) | 1 year |
| bloo-theme | localStorage (first party) | Stores your display preference (light or dark theme). | Value "light" or "dark" | Until manually erased (browser settings) |
These preferences are recorded only following an action on your part (choice of language or theme), for purely functional purposes, and contain no personal data. You can erase them at any time by clearing your browser's site data (see section 8).
Public cards: features you use
On public cards (mybloo.cards), some features store information in your browser, only when you use them. They are needed for the feature you requested and are not cookies: they remain on your device and are not automatically transmitted to the server. Session storage (sessionStorage) is erased when you close the tab.
| Key | Storage type | Purpose | Content | Duration |
|---|---|---|---|---|
| bloo-chat:<card> | localStorage (first party, public cards) | Find your chat conversation with the card holder again when you come back to the card. Stored when you send your first message. | Conversation token (only its fingerprint is kept on our servers), the name you gave, whether or not you gave an e-mail address, the conversation language | Until you end the conversation or the holder deletes it; otherwise until manual deletion |
| bloo-chat-lang | localStorage (first party, public cards) | Store the language you chose for the chat. | Language code | Until manual deletion (browser settings) |
| bloo_visitor | localStorage if you tick “Remember me on this device” (unticked by default), otherwise sessionStorage (first party, public cards) | Pre-fill the contact details form offered by the cards. Stored when you send your contact details to a card holder with this form. | First name, last name and e-mail address you entered | Ticked: until you untick the box or clear your browser data; otherwise until the tab is closed |
| bloo_lead_sent_<card> | localStorage (first party, public cards) | Stop asking for your contact details on this card after you have sent them. | Date sent | Taken into account for 30 days; kept until manual deletion |
| bloo_pdf_sound, bloo_pdf_hint | localStorage (first party, public cards) | Document viewer of the cards: remember whether you turned off the page-turn sound and whether the touchscreen usage tip has already been shown to you. | Flags | Until manual deletion (browser settings) |
| blooCh | sessionStorage (first party, public cards) | Remember, during your visit, how you opened the card (QR code, NFC or link), which is indicated when you save the card or exchange your contact details. | Opening channel (qr, nfc or link) | Until the tab is closed |
| bloo_lead_skip_<card> | sessionStorage (first party, public cards) | Stop offering the contact details form during your visit if you skipped it. | Flag | Until the tab is closed |
| bloo_notif_<…> | sessionStorage (first party, public cards) | Stop showing, during your visit, a card notification that you closed. | Flag | Until the tab is closed |
You can erase this data at any time by clearing your browser's site data (see section 8).
Wallet application
The Wallet application (blcrds.com/wallet) also uses your phone's local storage in order to work offline. These keys relate only to your own account, remain on your device and are read only by the Wallet. The keys containing your identities and your loyalty tokens are erased when you log out of the Wallet.
| Key | Storage type | Purpose | Content | Duration |
|---|---|---|---|---|
| bw-ids, bw-active | localStorage (first party, Wallet) | Displaying your identities and your sharing QR code, even without a network connection. | Public information of your cards (name, job title, company, photo, card address, status) and selected identity | Until you log out of the Wallet |
| bw-loy | localStorage (first party, Wallet) | Showing your loyalty QR code at the checkout, even without a network connection. | Signed QR tokens covering the next 10 minutes | Replaced at each refresh; erased when you log out |
| bw-lang, bw-loyNotice | localStorage (first party, Wallet) | Remembering the Wallet language and the fact that you have read the loyalty information. | Language code; flag | Until manually erased (browser settings) |
| bw-intent | localStorage (first party, Wallet) | Resuming the requested action after you log in (saving a card, joining a loyalty programme). | Short address of the card concerned and channel used | Taken into account for 30 minutes at most; erased after login |
The Wallet also uses a service worker: it keeps a copy of the application and of the files displayed (icons, images) in the browser cache for offline use. No API response (contacts, loyalty tokens, session) is cached; the copy of the files displayed is cleared when you log out.
4. Third-party and integrated partner cookies
Certain features rely on third-party services that may place their own cookies. The placing of these cookies depends either on your consent or on the use of an optional feature by the card holder.
Google Analytics 4
When: only after your consent to analytical cookies. Role: Google acts as a processor for audience measurement. The data may be transferred to the United States, on the basis of the EU-US Data Privacy Framework and appropriate safeguards. Cookies concerned: _ga, _ga_<ID> (see section 2).
Google Maps / Google Places / Google Reviews (optional integrations)
When: only if a card holder has chosen to integrate a Google Maps map, a Google Places location or their Google reviews, and a visitor displays that integration: a Google Maps map only loads after a click on "Show the Google map" (without a click, only a frame hosted by bloo.Cards and a link to Google Maps are displayed); that click constitutes consent. In this case, Google may place its own cookies (for example NID) in accordance with its privacy policy. In the absence of such an integration on the card consulted, no Google Maps/Places cookie is placed.
Embedded third-party content (after click)
When: only if a card holder has placed a YouTube or Vimeo video or content from another site (embedded frame) on the card, and you click to display it. Before this click, only a frame hosted by bloo.Cards is shown: the video player or third-party content is not loaded (no thumbnail is loaded from YouTube or Vimeo) and that service sets no cookie. YouTube videos are played from the youtube-nocookie.com domain (YouTube's privacy-enhanced mode) and Vimeo videos with Vimeo's do-not-track parameter (dnt=1). Your click counts as consent: the third-party service (Google for YouTube, Vimeo, or the publisher of the embedded site) may then set its own cookies or use your browser's storage, in accordance with its own policy, over which bloo.Cards has no control. Google Maps maps follow the same rule (see above).
Mollie (payments)
When: when going through the payment gateway (subscription or renewal of a subscription). Mollie may place its own security and transaction-tracking cookies, on its domain, in accordance with its cookie policy. bloo.Cards does not store payment card numbers.
| Third party | Integration | Possible cookies | Trigger |
|---|---|---|---|
| Google Analytics | Audience measurement | _ga, _ga_<ID> | After analytical consent |
| Google (Maps, Places, Reviews) | Optional, integrated by the card holder | NID, other Google cookies | Only if the integration is present and displayed |
| Mollie | Subscription payment | Security / transaction cookies (Mollie domain) | Only during payment |
| YouTube (Google) | Video placed by the card holder (youtube-nocookie.com) | YouTube / Google cookies and local storage | Only after your click on the video |
| Vimeo | Video placed by the card holder | Vimeo cookies | Only after your click on the video |
| Other embedded sites | Content from another site placed by the card holder | Depending on the embedded site | Only after your click on the content |
5. Legal bases
ePrivacy Directive, Article 5(3)
The placing and reading of information on your terminal equipment are only permitted with your prior and informed consent, except where they are strictly necessary for the provision of a service that you have expressly requested. This is the main applicable basis for cookies.
Belgian Act of 13 June 2005 (Article 129)
This Act on electronic communications transposes the ePrivacy Directive into Belgian law. It requires prior consent for access to terminal equipment, except for trackers strictly necessary for the operation of the service.
GDPR (Regulation (EU) 2016/679)
- Article 6(1)(a), consent: basis for the processing of data from analytical cookies.
- Article 6(1)(f), legitimate interest: basis for essential cookies (session, device linked to the Wallet, security, storing the consent choice).
- Article 6(1)(b), performance of the contract: basis for the local storage and cache of the Wallet application (data of your own account).
- Articles 12 to 14, transparency: clear information on the identity of the controller (Molderez-Consult SRL), the purposes, the legal bases and your rights.
Summary table of legal bases
| Category | ePrivacy basis | GDPR legal basis | Consent |
|---|---|---|---|
| Essential cookies | Art. 5(3): exemption (strictly necessary) | Art. 6(1)(f): legitimate interest | No |
| Functional localStorage (bloo-lang, bloo-theme) | Art. 5(3): user-initiated interface preference, without personal data | Not applicable (no personal data) | No |
| Wallet local storage and cache | Art. 5(3): exemption (strictly necessary for the Wallet to work, including offline) | Art. 6(1)(b): performance of the contract | No |
| Analytical cookies | Art. 5(3): consent required | Art. 6(1)(a): consent | Yes |
| Functional cookie and storage of public cards (bloo_lang, chat, contact details form, document viewer) | Art. 5(3): exemption (needed for the feature you requested) | Art. 6(1)(f): legitimate interest | No |
| Embedded third-party content (YouTube, Vimeo, other sites, Google Maps) | Art. 5(3): consent (your click on the content) | Art. 6(1)(a): consent | Yes (your click) |
6. Consent management
Consent banner
On your first visit, a banner appears before any non-essential cookie is placed. It offers explicit choices:
- Accept: authorises analytical cookies (in addition to essential cookies);
- Refuse: only essential cookies are used.
Audience measurement is the only category requiring your consent: these two buttons are therefore enough for a complete choice. You can change your mind at any time via the « Manage cookies » link.
No box is pre-ticked and no analytical cookie is placed until you have given your agreement.
Google Consent Mode v2 (refused by default)
Google Analytics 4 (Google Ireland Ltd) is only loaded after you accept. As long as you have not made a choice, or if you refuse, no Google Analytics script is loaded and no data is sent to Google for audience measurement. Your acceptance applies only to audience measurement (analytics_storage): Google's advertising signals (ad_storage, ad_user_data, ad_personalization) remain refused and your data is not used for advertising. Google Consent Mode v2 is set to "refused" by default, everywhere.
Recording and withdrawal of consent
- Recording: your choice (acceptance or refusal of audience measurement) is stored in the bloo-consent cookie (root domain) and in your browser's local storage.
- Duration: 6 months, after which your consent is requested again.
- Withdrawal: you can change or withdraw your consent at any time, as easily as you gave it, via the "Manage cookies" link at the bottom of every page (website and cards), which reopens the choice panel. Withdrawal immediately stops audience measurement and deletes the _ga and _ga_<ID> cookies from our domains; it does not affect the lawfulness of processing carried out before withdrawal.
No "cookie wall"
bloo.Cards does not make access to its services or the consultation of public cards conditional on acceptance of non-essential cookies. You can refuse analytical cookies and continue browsing normally.
7. Your rights and your control
In accordance with the GDPR, you have the following rights over any personal data processed via cookies:
- Right of access (Art. 15): obtain confirmation and a copy of the data concerning you;
- Right to rectification (Art. 16): correct inaccurate data;
- Right to erasure (Art. 17): request the deletion of your data, subject to legal retention obligations;
- Right to restriction (Art. 18): restrict certain processing;
- Right to data portability (Art. 20): receive your data in a structured, machine-readable format;
- Right to object (Art. 21): object to certain processing;
- Automated decision-making (Art. 22): bloo.Cards carries out no automated profiling based on cookies alone.
Withdrawal of consent
You can withdraw your consent to cookies at any time via the "Manage cookies" link (footer). Analytical cookies then cease to be used. The withdrawal of consent does not affect the lawfulness of the processing carried out before that withdrawal.
Exercising your rights
To exercise your rights, write to privacy@bloo.cards. We respond within 30 calendar days (extendable to 60 days for complex requests), in accordance with Article 12 of the GDPR.
8. Disabling cookies from your browser
You can manage or delete cookies at any time via your browser settings. Disabling essential cookies may, however, log you out or disrupt the operation of the site.
- Google Chrome: Settings → Privacy and security → Cookies and other site data. Help Chrome
- Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data. Help Firefox
- Apple Safari: Settings → Safari → Privacy (or Preferences → Privacy on Mac). Help Safari
- Microsoft Edge: Settings → Cookies and site permissions. Help Edge
Clearing your browser's "site data" also erases local storage (localStorage), and therefore your language (bloo-lang) and theme (bloo-theme) preferences, as well as the Wallet's offline data. If you delete the bloo_wdev cookie, your phone is no longer recognised: you will need to log in to the Wallet again or link it again.
9. Contact
Data controller
Molderez-Consult SRL, Square Valère-Gille 13 box 5, 1050 Ixelles, Belgium. BCE / VAT: BE 0842.262.084.
Privacy contact point
For any question relating to the protection of your data or to cookies: privacy@bloo.cards.
No Data Protection Officer (DPO) is legally required within the meaning of Article 37 of the GDPR; a dedicated privacy contact point is nevertheless made available to you at the address above.
Legal and compliance contact
Legal and compliance requests: legal@bloo.cards. General contact: hello@bloo.cards.
Supervisory authority
If you consider that your rights are not being respected, you may lodge a complaint with the Belgian supervisory authority:
Data Protection Authority (APD), Rue de la Presse 35, 1000 Brussels, Belgium. E-mail: contact@apd-gba.be · Telephone: +32 (0)2 274 48 00 · Website: www.autoriteprotectiondonnees.be.
10. Language and language primacy
The French version is the legal and original version; the NL/DE/EN versions are courtesy translations; in the event of any discrepancy, the French version prevails.
11. Change history
| Date | Version | Changes |
|---|---|---|
| 8 October 2026 | 3.5 | Functional local storage added: bloo-fx-cur (currency chosen to show prices for guidance on the Pricing and home pages; you are still invoiced in euros). |
| 5 October 2026 | 3.4 | Essential cookies added: bloo_oauth_n (sign-in with Google or LinkedIn, at most 10 minutes) and bloo_studio (CORPORATE studio session, 60 minutes); former bloo_rs_brand cookie (no longer set); bloo_rs_ref limited to the browser session. Public cards: bloo_lang language cookie (1 year) and local storage for the features used (chat, contact details form, document viewer). New heading "Embedded third-party content (after click)": YouTube videos (youtube-nocookie.com), Vimeo videos and content from other sites loaded only after your click. |
| 24 September 2026 | 3.3 | Reseller programme: bloo_rs_ref cookie (30 days), only set when a reseller's sign-up link is opened, added to essential cookies. |
| 23 September 2026 | 3.2 | Wallet application: bloo_wdev device cookie (90 days) added to essential cookies; local storage and offline cache of the Wallet (section 3). Exact name of the session cookie (bloo_session) and corrected duration (up to 4 hours after the last activity). |
| 23 September 2026 | 3.1 | Audience measurement loaded only after acceptance (no data sent to Google before the choice or after a refusal); Google advertising signals refused; actual inventory (bloo-consent, _ga and _ga_<ID>, 13 months); withdrawal via "Manage cookies" on the website and cards; single banner on cards; Google Maps maps loaded on click. |
| 17 September 2026 | 3.0 | Compliance revision: inventory aligned with the trackers actually deployed (removal of non-installed trackers: "in-house" analytics, marketing, remarketing, social media pixels); cookie / localStorage distinction (bloo-lang, bloo-theme); description of Google Consent Mode v2 (refused by default); correction of the Belgian legal bases (Act of 13 June 2005, Art. 129); update of contacts; addition of the language primacy clause. |
| 4 April 2026 | 2.0 | Detailed inventory, ePrivacy/GDPR sections, granular consent management. |
| 25 February 2026 | 1.0 | Initial version, launch of bloo.Cards. |