Privacy

When you open a page, four things are written down: which page it was, the two-letter country your network reports, the website you followed a link from if there was one, and the time.

That’s the complete list. There is no fifth field.

Your IP address isn’t stored. It’s used for a few milliseconds to stop one machine from flooding the site with requests, and it’s never written to the database.

No cookies are set for analytics. No browser or device information, no screen size, no language, no timezone. No city or precise location — country only. No advertising network, no tracking pixel, no fingerprinting. Nothing is shared with or sold to anyone.

The records carry no identifier of any kind — no cookie, no session, no visitor number. Two visits from the same person are two unrelated rows, and nothing distinguishes them from two visits by two different people.

That’s a deliberate limitation rather than an oversight. It means I can see that a case study was read forty times, and I cannot see who read it — including if I wanted to.

Some client work is behind an access code. If you enter a valid one, a single cookie is set so the page stays open on that browser for thirty days. It contains a reference to the project and an expiry date, and nothing about you.

Which code was used is recorded, so I can tell if one has been passed around. Who used it is not recorded, because it isn’t known.

The About page embeds a scheduling widget from Cal.com so you can book a call. That loads from Cal.com and is covered by their privacy policy, not this one. Every other part of the site is served from here, including the fonts.

Page records are deleted after twelve months. Access codes and their use are kept while the code is active.

Email phonepyaenaing99@gmail.com. There’s no data attached to you to send or delete — that isn’t a policy, it’s a consequence of how the site is built — but if something here isn’t clear, ask.