How this site handles
your data.

1. 01.
   Visitor analytics

   Aggregate only.

   This site uses Cloudflare Web Analytics — a cookieless, privacy-first service that runs on Cloudflare's own edge. No cookies are set. No persistent identifiers are stored. What is collected at the page-view level: the page URL (including any query string), the referrer URL (where the visit came from), the visitor's country (resolved from IP at the edge — the IP itself is not stored against the page-view event), and aggregate browser/device family. I see only aggregate dashboards — page-view counts, top URLs, top countries, top referrers, daily totals. I cannot reconstruct an individual visit or identify a visitor. No Google Analytics, no Plausible, no Mixpanel, no LinkedIn Insight tag, no Meta Pixel, no behavioral tracking SDK.

2. 02.
   Cookies & local storage

   First-party only.

   No cookies are set by this site's code. Your browser's localStorage holds a single key — `theme` — recording your light/dark/system preference for the next visit. That key never leaves your browser; it is not transmitted to any server.

3. 03.
   Forms

   None.

   The site has no contact forms. Where it invites you to get in touch, it does so via a mailto: link that opens your own email client. Anything you send arrives in my regular inbox and is handled like any other personal email.

Two services see your traffic at the network layer. I do not control their data collection beyond what is described in their respective privacy notices.

1. 01.

   Cloudflare

   Hosting + CDN + Web Analytics

   This site is served from Cloudflare's edge network as static assets. Cloudflare collects standard request data — IP address, user agent, request path, timestamp, country — for security, abuse mitigation, and operational telemetry. Cloudflare Web Analytics is enabled for this site as a cookieless beacon, automatically injected at the edge (no script in this codebase). It reports aggregate page views, top URLs, top countries, and top referrers, with no cookies and no per-visitor reconstruction. I see only the aggregate dashboards Cloudflare provides; I do not have access to per-visit logs.

   Cloudflare Privacy Policy ↗

2. 02.

   Google Fonts

   Webfont CDN

   Two webfonts — JetBrains Mono and Atkinson Hyperlegible — load from fonts.googleapis.com and fonts.gstatic.com. Google receives your IP address and user agent at font-fetch time. I do not configure analytics on these requests and receive no data back from Google.

   Google Fonts privacy & data collection ↗

Every page embeds Schema.org Person JSON-LD describing me — name, role, employer, certifications, public profile URLs. This is structured data about me, intended to help search engines resolve who I am as a public entity. It is not information about you, and it does not change based on who is visiting.

If you are a California resident, the California Consumer Privacy Act (CCPA, as amended by CPRA) grants you specific rights:

• Right to know — What personal information has been collected about you.
• Right to delete — Personal information held about you.
• Right to non-discrimination — For exercising your CCPA rights.
• Global Privacy Control (GPC) — Signal honored by default — nothing on this site collects information that I could opt you out of.

In practice, the answer for this site is short: nothing personally identifiable is collected from you that I can access. Cloudflare and Google Fonts handle their own logging per their privacy notices linked above. To exercise any of these rights or ask a question, email vitor@vitormr.dev .

I do not sell personal information and do not share personal information for cross-context behavioral advertising as those terms are defined in California Civil Code §1798.140.

This notice will be updated when the site's data flows change. Edits are reflected in the Last updated date in the header and visible in the public commit history at github.com/VitorMRodovalho/vitormr-site .