Privacy

This privacy notice explains how Note Haven — my personal blog at notehaven.pro — handles information when you visit. I am Mei, the author and operator. There is no company behind this site, no Pte. Ltd., and no registration number to quote. Contact details sit on the Bell Pull page if you need them.

What this site is: a static collection of pages served like a small magazine shelf. I do not run accounts, checkout flows, or comment systems. You read; you leave; that is the usual contract.

Information I receive directly: only what you choose to send by email or phone. If you write to [email protected], your message lands in my inbox like any personal correspondence. I use it to reply and then keep or delete it the way anyone keeps or deletes mail. I do not sell email addresses or phone numbers. I do not add you to marketing lists because there are no marketing lists.

Information collected automatically: the web host may log standard server data — IP address, browser type, pages requested, timestamps — for security and troubleshooting. I treat those logs as technical housekeeping, not as a profile of you. I do not merge host logs with email identities.

Cookies and similar storage: the site uses a consent banner implemented in /js/main.js. Essential storage keeps the banner from reappearing after you choose. Functional storage controls whether Google Maps embeds load on your visit. Analytics storage exists as a category for honesty but no third-party analytics scripts run here — the toggle defaults off and stays off unless you explicitly enable it during customise.

The consent cookie is named sg_reader_consent with a JSON payload (essential, functional, analytics, timestamp, version). A mirror copy lives in localStorage as reader_consent_v1 for fast reads. Both expire after about six months. Details and controls are on /cookies.php, including a Manage cookies button that reopens the panel.

Google Maps: pages include an embedded map centred on the Sembawang neighbourhood. When you accept functional cookies, the iframe loads from Google and Google may process data according to its own policies. When you reject functional cookies, maps are replaced by a placeholder with a Load map button on this site — approach (a) — so nothing loads until you opt in for that view.

Legal basis (plain language): I publish this blog as a personal expression. Consent governs optional embeds. Legitimate interest covers keeping the site secure and responding to messages you initiate. I do not conduct automated decision-making or profiling.

Retention: consent records last about six months. Email correspondence lasts until the thread is resolved or I delete it. Server logs rotate on the host's schedule, typically weeks not years.

Sharing: I do not sell personal data. I do not share it with advertisers. Embedded Google Maps may receive technical data when enabled — that sharing is between your browser and Google, disclosed here so you can decide.

International transfers: the host and Google may process data outside Singapore. I choose providers with published safeguards but cannot control every subprocess.

Your rights: under the Personal Data Protection Act you may ask what I hold about you, request correction, or ask me to delete email threads that are not needed. Email [email protected] with the subject "Privacy request". I will respond within a reasonable time. Some technical logs may persist until rotation even after deletion requests because I do not always control raw server backups.

Children: this blog is written for general readers and is not directed at children. I do not knowingly collect data from children. If a young person emailed me, I would delete the thread unless a parent clarified otherwise.

Security: static pages reduce attack surface — no login, no database, no form POST endpoints. Consent logic is client-side with cookie flags set carefully. No system is perfect; I update files when issues are reported.

Third-party links: if I link to an external site in a note, that site has its own privacy practices. I do not control them. This notice covers notehaven.pro only.

Email metadata: messages you send include whatever your mail client attaches — subject line, body, possibly IP headers visible to mail providers. I do not extract metadata for profiling.

Do not track: I do not respond to DNT browser signals because there is no tracking to disable beyond optional maps. Functional consent is explicit through the banner.

Complaints: if you believe I mishandled personal data, email [email protected] first so we can sort it out directly. You may also contact the Personal Data Protection Commission in Singapore if a complaint remains unresolved.

Data minimisation: I collect only what a static personal blog needs — optional embed consent, server logs from the host, and correspondence you initiate. I do not run loyalty programmes, accounts, or behavioural ad networks.

Backups: the host may keep backup snapshots containing server logs for a short period. I cannot always purge a specific IP from every backup tape; I note this for completeness.

Publication ethics: blog posts are my personal impressions. They are not verified news. Where memory might be wrong, tell me and I will amend the text or add a correction line.

Changes: if I change this notice, I will update the date below and republish the page. Material changes about maps or cookies will also be reflected on /cookies.php.

Contact for privacy questions: [email protected] or +65 6472 8391. Postal address: Blk 337 Sembawang Crescent, #06-18, Singapore 750337.

Corrections: if you spot a factual error about my own experience in a blog post, email me with the page URL and the sentence. I will amend or add a dated correction line. I do not publish reader comments on-site, so email is the channel.

Accessibility: I aim for readable contrast, keyboard-reachable cookie controls, and alt text on photographs. If something fails your assistive technology, tell me — static HTML is easier to fix than a platform I do not control.

Last updated: 11 August 2026. For the personal blog disclaimer, see the Byline page.