Privacy

The publisher named in the legal notice is responsible for the data described on this page.

Microsoft Clarity loads only after you click Accept in the banner. It records how pages are used (clicks, scrolling, session recordings) and sets its own cookies (_clck, _clsk). If you decline, it does not load.

Once you have accepted, the site also sends Clarity a few reading events: the objectives ticked, the audience you picked, the campaign tags of the link you followed.

Your choice is kept in your browser under cookie-consent. You can reset it here at any time.

Cloudflare hosts and delivers the site. To do so it processes technical request data, such as your IP address and browser type, under its own privacy policy.

The site keeps its own daily count of visits: each page opened, its language, the website you came from (its name only) and whether the visitor is a robot. A link with campaign tags (utm_source, utm_content) adds its tags. Three clicks are counted too, with the details listed under “What the site keeps in your browser”: the audience you pick, a calendar link, a request sent through the form. The count keeps no IP address, no browser details and no identifier.

The contact form sends your request to my mailbox through the email service Resend (servers in Ireland), which delivers it and keeps a delivery log under its own privacy policy. The site keeps no copy of it. If sending fails, the form opens your own email app with the message written, and you decide whether to send it.

Emails you send me are processed under the GDPR and used only to reply to you. Calendar bookings go through Cal.com, under its own privacy policy.

There is no newsletter and no mailing list.

Only one of these values is a cookie, lang: your browser sends it to the site so the home page opens in the language you picked, and the site does not store it. None of the others is sent to me on its own, with two exceptions. The last line of a request made through the form gives the audience, the points ticked, the first page of your visit, the number of pages opened, whether you arrived from a search and the campaign tags. That line is added to the request the form sends me (when your email app takes over, it sits in the message, so you see it before sending), and the calendar link passes the audience, the link clicked, the first page and the campaign tags to Cal.com. And when you pick an audience, click a calendar link or send a request, the site’s own count (Hosting, above) adds it to that day’s total, with the audience, the link, the first page, the number of pages opened, whether you arrived from a search and the campaign tags. Values in sessionStorage disappear when you close the tab.

Under the GDPR you can ask to access, correct or delete your data, and object to its use. Write to hello@sebastientang.com. You can also lodge a complaint with the CNIL, the French data protection authority (cnil.fr).

My personal productivity tools connect to the Oura API for my own use. They retrieve readiness and sleep scores, sleep stages, heart rate variability, stress scores, and activity and recovery metrics.

This data feeds a private, single-user dashboard. It is never shared with third parties, and never sold, licensed or monetised.

It is stored in Cloudflare D1, encrypted at rest and in transit, with access restricted to authenticated sessions. I can delete it at any time. If you think data was collected in error, write to me and I will delete it.

When access is authorised through Oura, Oura may collect usage data under its own privacy policy (ouraring.com/privacy-policy).