Privacy Policy
Last updated: 8 November 2026
This is my personal and professional website. I am Gabrielle Pochon, an individual based between Luxembourg and France, not a company. This page explains, plainly, what happens to data when you visit the site, and what my private tooling does with the creator accounts I connect to it.
Visiting this site
This site is a set of static files. There is no server-side code, no database and no account system behind it, so nothing you do here is recorded by the site itself.
It is hosted by OVH in France. Like any web server, theirs keeps standard access logs: IP address, date and time, the page requested, browser user agent and referring page. These exist so the hosting can run and stay secure, and they are kept and controlled by OVH under their own terms.
Cookies, storage and tracking
This site sets no cookies. It writes nothing to local storage, session storage or any other browser storage, and it runs no tracking or advertising scripts.
Fonts are served from this domain rather than from a font CDN, so loading a page contacts no one but this site. That is also why there is no cookie banner here: there is nothing to consent to.
Analytics
There is currently no analytics on this site at all.
If I add any, it will be a cookieless, aggregate measurement that does not track people across sites, and this page will say so before it goes live.
Contact
There is no contact form. My address, hello@gabriellep.ch, is a plain link. Opening it uses your own email program, and nothing is sent anywhere until you choose to send it.
If you do email me, I receive your address and whatever you write. It is delivered and stored by my email provider, and I use it to reply to you and to keep the thread of our conversation. I do not add it to a mailing list.
Links to other platforms
The site links out to profiles on TikTok, Instagram, Discord, GitHub and LinkedIn. These are ordinary links, not embeds: nothing is loaded from those platforms and nothing is sent to them while you are here.
Once you follow one, you are on their service and their privacy policy applies, not this one.
Connected platforms and Creator OS
Separately from this website, I build and use a private tool I call Creator OS, to analyse my own creator accounts. It is not part of this site, it is not reachable from it, and it has no public interface. This page describes it because it connects to platform APIs, not because you can use it.
It only ever reaches an account after that account has explicitly granted access through the platform's own official OAuth flow. Nothing is obtained by scraping.
For a connected platform, currently TikTok and Instagram, the data that may be processed includes:
- the account identifier, username and display name
- public profile statistics
- public information about videos and posts
- view, like, comment and share counts
- historical snapshots created locally from those values, so change over time can be seen
OAuth credentials and access tokens
OAuth credentials are never published on this website, and nothing on this site reads, stores or transmits them.
Access tokens for connected platforms are held inside Creator OS's own private infrastructure. They are not exposed to the public browser, and they are used only to reach the accounts that explicitly authorised them.
How the data is used
Only for the thing that was asked for: analytics about a connected account, for the person who owns that account.
I do not sell personal data. I do not use data obtained from TikTok, or from Meta's APIs, for targeted advertising. I do not share it commercially with third parties.
Data deletion requests
A platform is only ever connected to Creator OS after the person who owns that account has authorised it explicitly, through the platform's own official flow. There is no other route in.
To delete what is held for a connected account, disconnect that account inside Creator OS and use the option to remove its stored history. You can also write to me at hello@gabriellep.ch and ask for the data associated with your account to be deleted. Once I have checked that the request comes from the account holder, the data stored locally for that account is deleted.
Both routes remove the same things:
- the stored access token for that account
- the account identifier, username and display name held for it
- the profile, post and video statistics stored for it
- the historical snapshots built from those values, which exist so performance can be followed over time
Access can also be withdrawn from the platform's own settings, without going through me. On TikTok that is under Security and permissions, in the list of apps you have authorised. For Instagram it is in your Instagram or Meta account settings, in the list of apps and websites that have access. Withdrawing it there stops Creator OS reaching the account at all.
Instagram data is obtained through Meta's official APIs, after the account holder has consented to it. Removing the connection in Creator OS deletes the access and the data held locally for that account. It does not by itself clear the authorisation recorded on Meta's side, which is what the setting above is for.
Third-party services
Only two are involved in the public site: OVH, which hosts it, and my email provider, which handles mail sent to the address above. Connected platforms such as TikTok and Instagram are involved only through the authorised API access described above.
Changes
This page changes when the site or the integrations change. If an analytics script, an embed or a richer API is added, it is updated first. The date at the top is the date of the version you are reading.