Privacy

Privacy notice

This privacy notice explains how I, Kelvin, handle information when you visit Word Drift at worddrift.pro. I write and host this personal blog independently from a flat on Circuit Road in Singapore. There is no company behind the site, no registration number to quote, and no data broker sitting in the middle.

The Personal Data Protection Act 2012 (PDPA) applies in Singapore. I aim to treat visitor information with the same care I would want for my own — minimal collection, clear purpose, no selling, no surprise.

What I collect without you filling in a form: standard web server logs from my hosting provider (IP address, browser type, pages requested, timestamps). I use these logs only for security and to understand whether the site loads correctly. I do not run advertising trackers or social pixels on this blog.

What you choose to send: if you email [email protected], I receive your address, whatever you write, and any attachments you include. That correspondence is kept only as long as needed to reply or to remember a factual correction you asked for. I do not add you to a mailing list because there is no mailing list.

Cookies and local storage: the site uses a consent cookie named sg_notes_consent and a localStorage mirror cookie_consent_v1 to remember your cookie choices for about six months. Details live on the cookies page, including how Google Maps embeds are treated here.

Google Maps: every page includes a neighbourhood-scale embed centred on MacPherson rather than my exact unit. On this site, maps are classified as strictly functional and remain visible regardless of consent choice, because they anchor the blog to a real place. Google may process technical data when the embed loads. Their policies apply to that processing.

Analytics: the consent panel includes an analytics category for honesty and future-proofing, but this build does not load third-party analytics scripts. If that changes, this page will change first and the banner will still require a choice.

Third parties: hosting infrastructure, Google Fonts (requested by your browser from Google servers), and Google Maps embeds. No comment widgets, no newsletter platforms, no payment processors — there is nothing to pay for here.

Retention: server logs rotate on a schedule set by the host — typically weeks, not years. Email correspondence may be kept longer if it documents a factual correction. Cookie consent values expire after roughly one hundred eighty days unless you clear them sooner.

Your rights under the PDPA include asking what personal data I hold about you, requesting correction, and withdrawing consent where consent is the basis. Email me at [email protected] with the subject "Privacy request". I will respond in plain language, not legalese, as quickly as a one-person blog allows.

Children: this blog is written for general readers and is not directed at children. If you are under thirteen, please read with a parent or guardian who can explain what a personal blog is.

Security: HTTPS is expected in production. No system is perfectly secure; I choose hosting with reasonable defaults and keep software updated. Do not send sensitive identifiers by email.

Cross-border transfer: email and hosting may route through servers outside Singapore depending on providers. I choose reputable services and do not sell data to advertisers.

Changes: if I update this notice, the date at the bottom will change. Material changes will also be mentioned on the cookies page because that is where visitors already look for technical choices.

Contact for privacy matters: Kelvin, Blk 79 Circuit Road, #05-22, Singapore 370079, [email protected], +65 6597 4820.

This notice is written by me, not copied from a template factory. If something is unclear, tell me and I will rewrite it until it is plain.

Lawful basis in plain terms: I process server logs because they are necessary to operate a website safely. I process email because you chose to send it. I process cookie preferences because you chose a button on the banner or saved toggles in the panel. I do not process data for automated profiling or targeted advertising on this site.

Sensitive data: please do not send medical records, identity numbers, or financial account details through email linked from a personal blog. I cannot secure your data better than your own email provider does, and I have no need for those categories to correspond with readers.

Access requests: if you ask what I hold, I will check mailbox archives and any correction notes I keep in plain files. I do not operate a CRM. The answer may be "nothing beyond your emails" — that is often the honest answer.

Correction requests: if a post misstates a public fact unrelated to private individuals, tell me and I will edit the page with a note in the text or an updated date where appropriate. I do not run a formal corrections column; accuracy is handled inline.

Complaints: if you believe I handled personal data wrongly, contact me first. If we cannot resolve it, you may refer the matter to the Personal Data Protection Commission in Singapore. I hope it does not come to that because this site collects very little.

Links outward: if I link to an external site, their privacy practices apply once you leave worddrift.pro. I do not control third-party sites and I do not embed social feeds that track you across the web.

Images on this site are stored locally under /images/. They do not contain embedded location metadata tied to your device — they are static files I placed on disk. Your browser still requests them normally, which appears in server logs as any file request would.

No accounts: there is no login, no password reset, no profile page for visitors. That eliminates whole categories of breach risk at the cost of also eliminating comments. I accept that trade willingly.

Backups: hosting providers may back up the site on their schedule. Those backups can include server logs and site files. I do not separately archive visitor emails into cloud storage beyond my mailbox provider's defaults.

Data minimisation practice: when a visitor email resolves an issue, I delete thread clutter when cleaning the inbox — not instantly, but without hoarding. Minimisation is a habit, not a dashboard metric here.

Transparency about maps again because visitors ask: the iframe is a functional embed, not a tracker I operate. Google may receive technical information required to render tiles. I do not receive a report of who viewed which page map.

Version history: this notice was written for the August 2026 build. Earlier copies of the site under other prompts do not apply — if you have an old bookmark, read the date at the top of this page instead of assuming continuity.

Reading this notice together with the cookie page gives you the full technical picture. Neither page replaces the other — privacy is scope and rights; cookies are mechanics and buttons. Start here if you care why; start there if you care how.

If Singapore law changes how blogs like this should describe data, I will update this page in plain language first, before any jargon arrives from elsewhere. Your email asking for clarity always helps me rewrite better, shorter, and more honestly than I would alone.

Google Maps embeds are described on the cookie notice.

Corridor railing with late afternoon light