Policy · Privacy
Privacy
What the site records, for how long, and what it does not.
No IP address in the clear
The submission form needs to limit abuse, but it never stores an IP address: only an irreversible fingerprint, computed with a salt regenerated daily. The site erases both the fingerprint and the salt after 48 hours.
Audience measurement, and nothing before you agree
The site measures its traffic with one third-party tool, Google Analytics, which counts page views. It does not load until you answer the banner, and refusing is as easy as accepting. You can change your mind at any time through “Manage trackers”, at the bottom of every page.
No ad network, and no resale or commercial profiling.
The site sets a cookie even when you refuse: it remembers your answer, and its only purpose is to stop asking. The banner’s panel lists the cookies each tool sets; it is the open-source CookieConsent, which we serve from our own servers rather than its. Apart from that one, the site sets a single other cookie, the back-office session, which concerns the moderation team alone.
The support page is the one exception: it embeds a donation panel served by Ko-fi, which takes the payment and sets its own cookies. It loads there and on no other page of the site. The payment form lives on their end, so nothing you enter in it passes through this server, and we see none of it.
The anti-robot check on our forms uses Cloudflare Turnstile, which does not profile the person filling them in.
What is kept
The content of published events, which is public by nature. Moderation decisions, with their date and the name of the person who made them.
Messages sent through the contact form, with your email address if you left one, which is optional. Their address fingerprint follows the same rule and disappears after 48 hours.
Each message triggers a notification sent through a third-party email delivery service, which therefore sees its content. The same goes for the title and date of an event sent through the submission form. These are the only places on the site where a third party reads what you write: the measurement tools receive none of it.
Search engines and archives
The site is indexable, which is the whole point. It does, however, ask engines not to cache or archive it, and blocks archiving robots by name.
Without that, a removed event would live on in a search engine’s cache and in the Wayback Machine, and our removal commitment would be worthless.
Notifications and favourites
Your favourites, the city you picked, what you follow and your notification centre live on your phone. Boucle does not save them until you turn notifications on.
If you turn notifications on, we keep what it takes to send them. The technical address your phone gives us, your language, your city, the categories and hours you chose, the organizations you follow, the events you saved. No IP address or account, and no name.
A subscription whose sends fail for seven days is deleted. So is one that has received nothing for a year. Turning notifications off, or “Clear everything” in the settings, deletes it right away.
Your favourites are encrypted on your phone before they leave, under a key of four words, and what we receive is that encrypted bundle. We keep only a fingerprint of the key. Without the key, nobody can read the bundle, ourselves included, and working back to it from its fingerprint would take years of computing, even for someone with our servers in hand. A backup neither written nor read for twelve months is deleted.
To know whether the home screen is worth it, we keep totals per day, per city, per language and per kind of notification: home screen launches, sends, failures, subscriptions created and removed. No line describes a device.