Privacy policy
Last updated: 27 juillet 2026
This site is a documentation database. It has no interest in profiling you, and it does not. What follows describes exactly what the code records — no more, no less.
1. Who is responsible
The data controller is the site publisher, a private individual acting in a non-professional capacity, whose identity is held by the host (French LCEN, art. 6 III 2°). You can exercise your rights at this address, which is monitored: contact@keep.repair.
2. Browsing without giving anything
Reading a manual, a repairability index, a spare part or a safety recall requires no account and no personal data. You can use most of the site without ever being identified.
One caveat, which we would rather write here than let you discover: the site is funded by advertising, and the ad network’s script (Google AdSense) loads on every page — including before you answer the consent request, since it is what displays it. Google therefore learns your IP address and the page you are reading, even if you then decline. What declining prevents: advertising cookies and personalisation.
3. What you give us on purpose
| When | What is recorded | Why | How long |
|---|---|---|---|
| You post a review | The display name you choose, your review text, the rating. | Publishing the review. It is public. | Until you ask for deletion. |
| You ask a question | Your question, and your email if you ask to be notified of the answer. | Publishing the question, and notifying you. The email is never displayed. | The email is deleted once the notification is sent. |
| You request a product | The brand, reference and category you give, and your email if you ask to be notified. | Finding and adding the product, then letting you know when its page is online. The email is used for nothing else. | The email is deleted once the notification is sent. |
| You email yourself a manual | Your email, and the page concerned. No free-text message: the email body is composed by us. | Sending you that one email, and nothing else. You will never be contacted again. | The address is not stored. Only an irreversible fingerprint is kept for 90 days, to prevent bulk sending. |
| You create a manufacturer account | Your work email and a password (hashed, never readable by us). | Authenticating you and letting you manage your product pages. | As long as the account exists. |
4. Audience measurement
We count what gets used — a product page opened, a manual viewed, a search run. This records the TYPE of event and the product identifier. It does not record your IP address, your browser, or any session identifier. Two visits from the same device are indistinguishable: we are technically unable to reconstruct your journey.
Your IP address is used in passing, in memory, to cap how many calls a minute are accepted — that is what stops a third party manufacturing our statistics. It is never stored, never logged, never written to the database: it disappears with the request.
These raw events are kept for 90 days, then deleted. All that is left afterwards is daily totals per product — "this manual was opened 14 times on 3 March". A total no longer describes anyone.
These counters also feed the statistics we make available to manufacturers (how often their manual was opened). They are aggregated and never concern an individual.
We do not ask your permission for this measurement, and here is why. The law exempts audience measurement that stays strictly that: a single purpose — knowing what gets read —, for this site alone, with no cross-referencing against other data, no transmission to anyone, no tracking you from one site to the next, and for a limited time. Ours meets those conditions. But the exemption also requires that you be told: that is exactly what this paragraph does, and why it exists.
We also use Vercel Analytics and Vercel Speed Insights, which measure traffic and load times without cookies. Your IP address is processed transiently, then hashed without being stored. Vercel acts as a processor.
Finally, we use Google Analytics, to understand where our visitors come from. That one, unlike the two above, sets cookies and sends your data to a third party: it therefore falls outside the exemption described above, and your agreement is asked for — through the same banner as advertising, the only one on the site. Until you accept, Google Analytics writes no cookie, assigns you no identifier, and receives only an anonymous, aggregated signal.
5. What is stored in your browser
None of the following is a Google cookie: these are our own records, they stay on your device and are never sent to us. Google’s cookies — the ad network’s and the audience measurement’s — are described in sections 4 and 6.
Without consent — you asked for it with a click
These records serve exactly what you just did, and nothing else: "I own this product" (to find your appliances again), your "this answer helped" votes (so you cannot vote twice), and the fact that you dismissed a prompt (so we do not show it again). The law exempts them from consent because they are necessary for a service you expressly requested.
With your consent
Only one banner asks for your agreement: Google’s, displayed by the ad network’s script. It is certified and required for advertising, and we use it for the two features below as well. In other words: what you answer Google applies to the whole site. There used to be a second banner, ours; it has been removed, because two banners that ignore each other can have you decline on one side what you accepted on the other.
Of its answers, we read only one: the one that allows or refuses storing and reading information on your device. That is exactly the scope of the two features below.
- Recently viewed products — the list of pages you opened, to hand them back to you. It is recorded without you asking: it therefore requires your agreement, and is erased if you decline.
- Video tutorial thumbnails — they are hosted by Google (i.ytimg.com). Displaying them means your IP address and the page you are reading are sent to Google. Without your agreement, the thumbnail stays blank and no request is sent. The video still plays: if you click it, it opens on youtube-nocookie.com — your click is the request.
You can change your mind at any time by clearing your browser’s site data: the banner will reappear and ask again. If you decline after having accepted, the list of recently viewed products is erased from your device — declining is not only "stop recording".
And if that banner never appears — an ad blocker stops the script that carries it, or Google does not show it in your country — we treat it as you having agreed to nothing. You will then have neither the history nor the tutorial thumbnails. Everything else works normally: manuals, repairability indices, spare parts, recalls, questions, votes, "I own this product", and the videos themselves, which still play on click.
6. Who else sees this data
- Vercel — site hosting and cookieless audience measurement.
- Supabase — database and authentication (data hosted in the European Union).
- Google — the ad network (AdSense) loads on every page, including before your choice: it is what displays the consent request. Google therefore receives your IP address and the page address. Until you accept, no advertising cookie is set and ads are not personalised. Google Analytics, also loaded on every page, measures traffic: until you accept, it writes no cookie and assigns you no identifier (section 4).
- YouTube — video thumbnails and playback, if you accept them or start a video. YouTube belongs to Google.
We sell no data, and pass none to anyone else. The public data we republish (repairability indices, safety recalls) comes from data.gouv.fr and RappelConso: it is not about you, it is about products.
7. Your rights
You can request access to your data, its rectification, its erasure, or object to its processing. Write to contact@keep.repair. We answer within one month. In practice most requests take minutes: we have almost nothing on you.
If our answer does not satisfy you, you can lodge a complaint with the CNIL — cnil.fr.
8. If this page changes
This policy describes the code as it works today. If the code changes, this page changes with it — the date at the top is authoritative.