AHMAD:// Available for work — open to remote roles and contracts

Privacy — stated exactly, not legally

The shortest honest summary: this site is static HTML from a build pipeline. There is no account system, no analytics, no advertising, no third-party scripts, no fonts from a CDN, and no server-side code that could watch you read it. If a policy on the internet needs a paragraph to explain its tracking, it has too much tracking.

What is stored about you

  • Nothing on our side. No database. The only records this domain ever emits are the standard access logs the hosting provider keeps for security (IP, user-agent, timestamp, requested path) — the same as any website request, kept by the infrastructure, not by me, and not visible to me in normal operation.
  • On your device: four small preferences plus a search-index cache, all listed with purposes on the cookies & local storage page. All of it is strictly functional, local, and deletable by you at any second.

When you contact me

The contact flow is a mailto: link or a copy of the address — nothing is submitted "through the site." When you email me, your mail provider and I see what you chose to write. I use it solely to reply, don't forward it anywhere, and delete it on request if you'd rather it not exist.

Links out

Every claim links outward — GitHub, npm, deployments, certificates. The moment you click, the destination sees a visit from your browser under its policy, not mine. That exposure is deliberate: the alternative was screenshots, which lie better.

The nightly verifier, explained

A scheduled GitHub Actions job re-requests every public evidence URL on this site and commits the pass/fail report. It sends nothing about you — it runs from CI against public pages, on a schedule, forever. That's how the footer can carry a live pass/fail count without it being marketing.

Your rights, plainly

Ask me via the contact page for anything I hold about you (realistically: your email thread) and I'll export or delete it. GDPR/CCPA-style objections you'd normally raise are answered here in advance because the collection that triggers them doesn't happen.

Last revised: 2026-09-01 · this page is versioned in the site's git history, so "we quietly updated our policy" isn't available to me · questions: /contact

ahmad@xr:~% ask — grounded in this site · no LLM, no invented answers

try: