Privacy Policy

Last updated: August 31, 2026

This policy covers two separate things: this website, and the personal automation tooling I run for myself. They share a policy because they share an owner, but they are unrelated systems and no data moves between them.

This website

leixusam.com is a static site. There are no accounts, no sign-ups, no comment sections, and no forms — there is nothing here for you to submit, so there is nothing of yours for me to store.

The site uses Google Analytics to count visits and see which writing people actually read. It records things like the pages you view, roughly where in the world you are (derived from your IP address, which Google does not retain), and what browser and device you're on. It sets identifiers in your browser to do this. I see only aggregate reports; I can't identify individual readers from them, and I don't try to. Google's handling of this data is governed by Google's Privacy Policy, and you can opt out entirely with the Google Analytics opt-out add-on or by blocking analytics in your browser. The site works fine either way.

The site also stores one thing on your device: your light or dark theme preference, kept in your browser's local storage so the page doesn't flash the wrong colours next time. It never leaves your browser. Clearing site data removes it.

Some pages link out to places like GitHub, LinkedIn, and X. Once you follow a link, you're on their site under their policy, not mine.

My personal automation tooling

Separately, I run command-line utilities and scheduled agents that operate on my own accounts. These are not a product, are not offered to anyone else, and have no users other than me. This section exists because that software authenticates against Google APIs, and Google requires a published policy describing what it does.

When I authorize it, the software uses Google APIs to act on my own Google account — reading and sending mail, managing calendar events and tasks, and reading and writing files in Drive, Docs, Sheets, and Slides. It only ever accesses the single account that granted it access. It cannot access anyone else's account, and there is no way for anyone else to sign in to it.

It runs on hardware I own and control. OAuth credentials are stored locally on those machines and are never transmitted anywhere except to Google when authenticating. Data retrieved from Google APIs is processed on those same machines and is not copied into any hosted database.

One exception worth stating plainly: some of these tasks are performed by AI agents, so the content they work on — for example the text of an email I've asked to be summarized or answered — is sent to the AI providers whose models perform that work (Anthropic and OpenAI), under their respective API terms. That is the only circumstance in which data obtained through Google APIs leaves my machines.

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Because the account owner and the operator are the same person, access can be withdrawn at any time from Google Account permissions, which immediately and permanently invalidates the software's credentials.

What I don't do, in either case

I don't sell data, transfer it to anyone for advertising, use it for credit assessment, or share it with third parties beyond the analytics and AI providers named above. None of it is used to train any model.

Contact

Questions about this policy: leixusam.yuzu@gmail.com.