Privacy policy

How hardcodd.net handles reader data. Updated 20 October 2026.

About the site and contact

hardcodd.net is a personal website about development, projects and tools. The site owner processes data to operate the website, communicate with readers and prevent abuse. For privacy questions or requests to correct or delete data, contact hello@hardcodd.net. Identify the relevant page or account; confirmation that you control the email address may be needed to protect your data.

Reading, search and ratings

You can read articles without an account. When you visit, the server receives your IP address, time, requested URL, browser information and technical request data. These may appear in web server and error logs used to operate and protect the site. Submitted search terms and their usage counts are stored to improve search. Do not enter passwords or other confidential information in search.

Rating an article stores your choice, its time and a random browser identifier that lets you change your vote. Ratings and searches do not require an account.

Comments and notifications

Commenting involves the comment text, chosen name, email address or account association, timestamps and moderation status. Published names, text and comment times are visible to other visitors. Email addresses are not displayed publicly. Do not include information you do not want to make public.

Your address is used to confirm actions and, if you subscribe, send reply notifications. You can unsubscribe using the link in an email. Comments are handled by Commentail on the site's server. Email is sent through Beget, which receives the recipient address and message content.

Signing in with Google, GitHub or email

This section applies when you use a sign-in method after it becomes available on the site. Sign-in supports reader accounts and participation in discussions. Google sign-in provides an account identifier, email address and available basic profile details such as a name and picture. GitHub sign-in provides an identifier, username, available profile details and email addresses needed to verify your address. These details are used to create and recognise your account, connect sign-in methods and display your chosen name.

The site does not receive your Google or GitHub password or request access to messages, contacts, calendars or repositories. Provider tokens are not retained for later API access. Google data is not sold or used for advertising or training artificial intelligence models. Choosing a provider takes you to that service, which processes data under its own policy: Google and GitHub.

Email sign-in uses the address you provide and a single-use link valid for 15 minutes. The link signs you in without a password; do not forward it. Reader sessions last 30 days. A comment draft may be stored temporarily in your browser and for up to 30 minutes in the session so that you can return to it after signing in.

Cookies, statistics and external videos

Necessary cookies protect forms, maintain sessions and remember your choices. Your theme preference is stored in your browser. Cookie choices and voting identifiers normally last 180 days. The current storage inventory, lifetimes and controls are available in cookie preferences.

First-party statistics run only with your permission. They record page views, GitHub clicks and downloads, page paths, times and the referring domain. A random identifier distinguishes browsers for up to 180 days. Statistical events do not store IP addresses, browser strings, full referrer URLs or URL parameters. Pseudonymous events are kept for 183 complete days plus the current day, then retained as aggregate figures without visitor identifiers.

External video players load after you allow external media. The selected video service then receives technical connection data and may use its own cookies. You can decline statistics and external media or change your choice in preferences. Withdrawal stops further collection or loading; it does not reverse data already transmitted or remove other domains' cookies. Ordinary external links open websites with their own privacy rules.

Storage, access and deletion

The site's main data is stored on a server hosted by Beget. Access is restricted to the owner and supporting services as needed to operate the site. Data is not sold. It may be shared with hosting and email providers to perform their functions, the sign-in or media provider you select, or where required by applicable law.

Accounts and comments are retained to support discussions until deletion or a relevant request is processed. Search terms and votes have no automatic deletion deadline. Application logs rotate with a 14-day retention setting; cleanup takes place on writes, so inactivity can delay it. Web server logs rotate daily with 14 archives retained. Backups rotate separately; deleted data may remain in them until those copies rotate.

To request access, correction or deletion, write to the address above. We will identify the records belonging to you and what can be deleted or anonymised, taking account of security, discussion integrity and applicable requirements. Clearing cookies does not itself delete server data. Changes to data handling will be reflected on this page with an updated date.