Last updated: 13 October 2026
This page covers jordangong.com and the services linked from its front page:
Sites you reach by following a link away from these pages have their own privacy practices, which this policy does not cover.
This site is plain HTML served from a server I run myself. It sets no cookies and loads nothing from anyone else. The only script is a one-line handler on the email link, which builds the address in your browser when you click it and sends nothing anywhere.
Like almost every web server, mine writes an access log. For each request it records:
I use these logs only to keep the server running and to deal with abuse, such as the bots that probe for leaked config files. The logs are rotated and deleted after about two weeks. I don't build visitor profiles from them or combine them with any other data.
The blog is a static site. It sets no cookies, runs no scripts and loads nothing beyond its own stylesheet.
It is hosted on GitHub Pages and served through Cloudflare, so unlike the main site it doesn't run on my own server. To deliver the pages, GitHub and Cloudflare necessarily process technical data such as your IP address and request details, under their own policies: the GitHub Privacy Statement and the Cloudflare Privacy Policy. Cloudflare may also ask your browser to report network errors if a page fails to load. I don't receive individual visitor logs from either service; at most I can see aggregate traffic numbers in Cloudflare's dashboard.
SearXNG is a metasearch engine: it passes your query to other search engines and combines what they return. You don't need an account and it keeps no search history.
RSSHub turns pages from other websites into RSS feeds. When you or your feed reader request a feed, my server fetches the source site on your behalf, so that site sees my server rather than you. Fetched content is cached for a few minutes to reduce load on the source sites.
Requests are recorded in the access log described above. Note also that the instance's front page publicly shows aggregate request counts, including the most-requested feed paths. It never shows IP addresses or anything else that identifies who made a request, but a feed path can contain the name or ID of the account being followed.
If you email me at
,
I'll receive your address, your message and the usual email headers.
I use them only to reply to you and keep them only as long as the
conversation is useful. My email provider stores messages on my
behalf. If you'd like the content to stay private in transit and at
rest, encrypt it with my GPG key
(fingerprint 5E80 7387 AF9F 1B91 27D1 EF91 2924 0254 0B06 968E).
I don't sell, rent or trade any data. I don't share it with anyone, except the hosting providers named above as part of serving the blog, or where the law requires me to.
You can ask me what data I hold about you, or ask me to delete it, by email. Since the logs don't contain names, I'll need your IP address and the rough time of your visit to find the relevant entries. Even if you never ask, server logs are deleted automatically after about two weeks.
All of these sites are served only over HTTPS, so what you request and what you send can't be read or altered by others on the network.
If my setup changes, I'll update this page and the date at the top.