Privacy
What this site stores, what its services count, and how to ask me to remove something.
1 What this site stores
- Leaderboard entries. If you choose to save an arcade score, your chosen name and score are stored in Firebase under that game’s leaderboard. Leaderboard names and scores are public and can be removed on request.
- Your theme choice. The light or dark theme you choose is saved in your browser’s local storage under
wp-theme. It stays in your browser; it is not sent to the database.
These are the only things the site itself stores about visitors, and the site itself does not set cookies. Optional analytics and hosting logs are described separately below.
The Studio is a private admin area. Sign-in is with Google, or with an email address and password, through Firebase Authentication. When someone signs in, Google, which provides Firebase, processes and keeps their sign-in account: the email address, a user ID, sign-in dates and, for Google sign-in, the name and profile photo on their Google account. That account stays until it is deleted. Firebase keeps the session in the browser’s IndexedDB until they sign out. An account without a Studio role sees a “No access” screen. The site’s database stores nothing about it, and I will delete the sign-in account on request.
2 Analytics
Cloudflare Web Analytics, if enabled, provides cookieless, aggregate statistics: page views, referrer, country and browser. Cloudflare describes it as privacy-first: it does not use cookies or personal identifiers to track visitors.
The analytics beacon is only included when it has been configured; it is not always enabled.
3 Hosting
This site is hosted on Render. Render may process standard server logs to operate and secure its hosting service.
4 Third parties
Firebase, provided by Google, supplies the site’s database and the Studio sign-in. For how Google handles information in its services, see Google’s privacy policy.
Render provides hosting, and Cloudflare provides the optional analytics described here.
The GitHub statistics page shows a contribution image served by GitHub (raw.githubusercontent.com), so opening that page sends your IP address and browser details to GitHub. No referrer is sent.
The LeetCode notes page reads the notes from the database when you open it, and the Lab game pages read and write their leaderboards, so opening any of these pages connects your browser to Firebase, which receives your IP address and browser details and keeps them for a few days; the site itself stores nothing about you.
5 Your choices
To object to how your information is used, or to ask for a leaderboard entry or a Studio sign-in account to be deleted, email JideOyelayo0@gmail.com. Tell me which leaderboard entry or sign-in email address you mean.
You can clear this site’s local storage in your browser to forget your theme choice and the two technical keys the Firebase SDK writes there on the Lab and LeetCode pages, firebase:host:… and firebase:previous_websocket_failure (connection details, no personal data). The Firebase SDK also keeps a small heartbeat record (the date and the SDK version) in the browser’s IndexedDB; clearing the site’s data removes it too.
6 Changes
I will update this statement when the way the site stores or uses information changes.