Binmage is my personal blog about AI, hardware and hands-on experiments, operated from Singapore. I publish as buffer and handle the blog’s personal-information processing. This page explains what happens to your information when you use it. For privacy requests, contact [email protected].
Reading the blog
You do not need an account to read articles. The server and Cloudflare, which delivers and protects the site, process connection and request information: IP address, requested page, time, response status, referring page and browser information. This supports page delivery, troubleshooting and protection against abuse.
The site’s fonts and ordinary article images are served from Binmage rather than fetched from a third-party font service. The site does not currently run Google Analytics, Tag Manager or AdSense, or sell visitor data.
Information you choose to provide
If you email me, I receive your address, message and any information you include. I use them to reply and deal with your request; an email to the blog does not subscribe you to marketing.
Where comments are open, WordPress collects your chosen name, email, optional website, comment, IP address and browser information. Your name, comment and any website link may become public after moderation. Your email is not displayed. A name and email are required to submit a comment, but you can read without commenting. Please avoid posting private information about yourself or others.
Preferences and optional external content
The blog can remember your language, appearance and privacy choices in browser storage. The cookie page lists the storage used and explains how to clear it.
X posts are loaded only when you choose to load them. Loading connects your browser to X, which can receive technical and page information and use its own cookies or similar storage. Opening a source link takes you to the external site. Declining external content does not prevent you from reading the blog.
Comment avatars are handled locally; this blog does not automatically ask Gravatar for a public commenter’s avatar or send it the commenter’s email hash.
Accepting external media does not by itself contact X: you must still choose to load an embed. If you later withdraw the choice, loaded X frames are removed and future loads are blocked until you allow them again. This cannot erase information already received by X.
Why information is processed
Where GDPR applies, basic delivery, security, handling correspondence and moderating requested comments rely on the legitimate interests of running and protecting this personal blog and responding to readers. Optional external content relies on your choice and, where required, consent. Legal obligations may require certain records to be kept. Information is not used here for automated decisions producing legal or similarly significant effects about you.
Who may receive information
Hosting, delivery, security and email providers process information needed to perform those services. Cloudflare is involved in delivery and security. X receives information when you load its content or visit it; its processing is governed by its own policy. A lawful request may require disclosure to a competent authority.
Providers can operate internationally, including outside your country or the European Economic Area. Their processing locations and transfer arrangements depend on the provider and service. This page does not promise that every request or record stays in one country. Relevant details are available in Cloudflare’s privacy policy and X’s embedded-content privacy information; you can also contact me about the services used by the blog.
How long information is kept
Server logs rotate monthly or when their size limit is reached, with 12 compressed archives retained in addition to the current log. Rotation by size can make the history shorter; it is not an exact expiry for each visit. Cloudflare’s own records follow its policies.
Correspondence is kept for as long as needed to handle the conversation or request and any relevant dispute or legal obligation. Approved comments remain with the discussion until removed, the article is removed or a deletion request is dealt with; restricted backups can take time to age out. Browser-storage periods are listed on the cookie page. Retention is reviewed according to purpose, security needs and applicable legal obligations.
Your choices and rights
Use Cookie settings to change optional-content choices. Withdrawing consent stops future consent-based loading; it does not undo data already sent to an external provider. Browser controls can delete local storage and cookies.
Where applicable, you can request access, correction or deletion, object to processing, restrict it or ask for a portable copy. Contact [email protected]; include enough information to identify the relevant email or comment without sending unnecessary identity documents. Applicable deadlines will be followed, normally within one month under GDPR. You may also complain to the relevant data-protection authority.
Changes to this page
If the blog adds analytics, advertising or another service that changes this description, the notice and relevant controls will be updated before it is used. The update date shows when this page was last revised.