Learn how we collect, use, and protect your personal data when you visit our website.
Last updated: 10 October 2026
This Privacy Policy explains how Cristian Di Carlo ("I", "me") processes limited information when you visit this website or access its private content management system.
For questions regarding privacy or the processing of your data, contact:
Cristian Di Carlo
okazakee@proton.me
This website is hosted on Vercel.
As part of normal website delivery, security and infrastructure operation, Vercel may process technical request information such as IP addresses, browser and device information, request URLs, timestamps and other HTTP metadata.
This information is processed as part of the technical operation and security of the website and according to Vercel's applicable privacy and data-processing policies.
Vercel Speed Insights is used to monitor website performance and Core Web Vitals.
Performance monitoring may include anonymous or aggregated technical metrics related to page loading, browser, device, operating system, network conditions and approximate geographic region.
This information is used only to understand and improve the technical performance of the website.
This website uses a self-hosted instance of Umami for anonymous, privacy-focused analytics.
Umami does not use tracking cookies or cross-site tracking and does not receive names, email addresses or account identifiers from website visitors.
It may record anonymous information such as page views, referrer URLs, browser, operating system, device type, approximate geographic information and limited interaction events such as opening contact links, project links or sharing content.
It may also generate anonymous heatmaps showing where visitors click and how far they scroll on a page.
Where enabled, it may additionally record anonymous session replays, which reconstruct interaction patterns within a visit such as mouse movement, clicks, scrolling and navigation sequences. Session replays are used only to analyse and improve the usability of the website. They remain anonymous and cookie-less, involve no visitor identifiers and no cross-site tracking, and form and other sensitive areas are excluded from session recording. Input fields are masked.
Technical request information, including the visitor's IP address and user agent, may be used transiently to derive anonymous session or location information. The IP address itself is not stored as part of the analytics record.
The resulting analytics data is not intended to identify individual visitors.
The analytics instance is self-hosted and the collected analytics data remains under my control.
Where supported and configured, browser Do Not Track preferences are respected.
Access to the CMS is restricted to explicitly authorized users. Public self-registration is disabled.
Depending on the authentication method, the following information may be processed:
Passwords are handled by Supabase authentication and are not stored by this website in plain text.
When GitHub OAuth is used, the CMS may receive:
GitHub processes the OAuth authentication request according to its own privacy policy.
The CMS maintains an internal allowlist used exclusively for access control.
An allowlist record may contain:
The allowlist is not publicly accessible and is used only by trusted server-side authorization logic.
To protect the CMS login system from automated abuse, rate limiting is applied independently to the requesting IP address and login email.
Before persistence, both values are transformed into SHA-256 hashes. The raw IP address and raw email address are not stored in the rate-limiter database table.
The rate-limiter stores only the hashed identifier, attempt counters, timing information and temporary lockout state.
Successful authentication clears the corresponding rate-limit buckets. Stale rate-limit records are also subject to automated scheduled cleanup.
This information is used exclusively for authentication security and abuse prevention.
Two functional cookies are used to remember the selected appearance:
| Cookie | Purpose | Expiry |
|---|---|---|
themeMode | Stores the selected theme mode (light, dark or automatic) | 365 days |
resolvedTheme | Stores the resolved theme used during server-side rendering | 365 days |
These cookies are used only to remember a preference explicitly selected by the user.
When an authorized user logs into the CMS, Supabase authentication uses session cookies to maintain the authenticated session.
These cookies are used exclusively for authentication and session management and are not used for advertising or cross-site tracking.
Data is processed only where necessary for the following purposes:
| Processing | Purpose | Legal basis |
|---|---|---|
| Website infrastructure | Delivering, operating and securing the website | Legitimate interests, Art. 6(1)(f) GDPR |
| Performance monitoring | Diagnosing and improving website performance | Legitimate interests, Art. 6(1)(f) GDPR |
| Anonymous analytics | Understanding aggregate website usage and improving website usability | Legitimate interests, Art. 6(1)(f) GDPR |
| CMS authentication and access control | Operating and securing the private CMS | Legitimate interests, Art. 6(1)(f) GDPR |
| Login rate limiting | Preventing abuse and unauthorized access attempts | Legitimate interests, Art. 6(1)(f) GDPR |
Supabase provides database, storage and authentication infrastructure.
The Supabase project used by this website is deployed in the Central Europe (Zurich) region.
Switzerland is recognized by the European Commission as providing an adequate level of protection for personal data under Article 45 GDPR.
Supabase may also use subprocessors and perform limited operational processing in other jurisdictions according to its privacy policy, data-processing terms and applicable transfer safeguards.
Vercel provides website hosting and performance infrastructure.
Vercel is based in the United States and may process information outside the EU/EEA. Where required, Vercel provides international data-transfer mechanisms including Standard Contractual Clauses.
GitHub processes authentication information when an authorized CMS user chooses GitHub OAuth.
GitHub's processing is governed by its own privacy policy and OAuth terms.
Website analytics are processed by a self-hosted Umami instance rather than a third-party analytics service.
Umami is configured to collect anonymous usage information without advertising cookies, cross-site tracking or visitor account identifiers.
Authorized CMS users may request or initiate removal of their CMS access.
The current account-removal flow removes the user's CMS allowlist entry and website profile and terminates the active session.
For requests concerning any remaining authentication or stored data, contact:
Under the GDPR, where applicable, you may have the right to:
To exercise any applicable right, contact:
This Privacy Policy may be updated when the website, CMS, infrastructure or data-processing practices change.
The latest version will always be published on this page.