LegalVersion 1.1
Privacy Policy
What this workspace remembers, what you send through its forms, and the services that process it.
1. Who runs this site
This website is a personal engineering portfolio and writing workspace operated by Prasad Madhuranga (“I”, “me” or “the operator”), based in Sri Lanka. I am responsible for deciding how personal data described in this policy is used on this site.
You can contact me about privacy through the Contact page. Please do not send passwords, government identifiers, payment-card details or other highly sensitive information through the contact form.
2. At a glance
- There are no visitor accounts, advertising cookies, advertising identifiers, social-media tracking pixels or third-party analytics scripts on this site.
- Most appearance and reading preferences stay in your browser. The cookie and browser-storage register lists them.
- Opening an article or other entry can add to first-party aggregate read counts by entry, day, country code and referring website hostname. Those aggregates are stored in Firebase; they are not an advertising profile.
- Personal data is sent to me only when you use an interactive feature — principally the contact form or guest comments — or when technical processing is needed to deliver and protect the site.
- I do not sell or rent personal data.
3. Information you give me
3.1 Contact enquiries
When you use the contact form, I receive your name, email address, subject and message. A telephone number and one attachment (PDF, PNG, JPEG or text file up to 8 MB) are optional. The site relays the enquiry and any attachment to me through Telegram so I can read and reply to it. The site itself does not write the enquiry to a separate application database.
I use contact enquiries only to understand and respond to your message, follow up where reasonably necessary, and keep a proportionate record of the correspondence. Please avoid sending information that is not needed for your enquiry.
The protected “reveal email” control does not ask for your email address. It verifies a one-time Cloudflare Turnstile token before showing my contact address.
3.2 Comments
Comments are public. If you post a guest comment, the site publishes your chosen display name, comment text and posting time with the entry. If you provide a GitHub, X (formerly Twitter) or LinkedIn handle and choose it as your comment source, that handle may be linked beside the comment and an avatar may be shown.
Your email address is required for a guest comment so I can identify abuse, moderate the discussion and reply where needed. Your email address is stripped from the public comment feed and is not intended to be displayed publicly. The address is stored with the comment record in Notion and is included in the private operator notification sent through Telegram. An operator notification may also include the IP address and country code associated with the submission for moderation and security.
If you provide a supported social handle, the server may query GitHub’s public API, an X profile lookup service or Unavatar to find the corresponding public avatar. The avatar URL can be stored with the comment and loaded by readers’ browsers from the relevant avatar host.
The comment composer can remember your name, email address and optional handles in the pm_commenter cookie for 180 days so you do not have to re-type them. It also keeps an unsent draft in your browser’s session storage. You can use the composer’s Forget me control to clear the remembered identity and local draft.
Comments may be hidden or retained for moderation, security, context and record-keeping. If you want a comment corrected or deleted, contact me with the page address and the email address used for the comment so I can locate it.
3.3 Direct correspondence
If you contact me directly — for example by email or through a linked professional profile — I will receive the information you choose to send through that channel. The provider of that channel also processes the communication under its own terms and privacy policy.
4. Information processed automatically
4.1 Delivery, security and abuse prevention
To serve pages and protect interactive features, the hosting and application servers necessarily process technical information such as IP address, browser/user-agent details, requested address, date and time, response status and similar request data. The application also uses IP-derived rate limits and short-lived in-memory abuse checks for comments, contact submissions, email reveal and owner sign-in.
Cloudflare Turnstile may process browser and interaction signals to decide whether a protected action appears automated. The site verifies the resulting token with Cloudflare and does not store that token after the request.
4.2 Aggregate readership counts
When an entry page is opened and remains visible briefly, the reader sends a first-party read “pulse”. The server increments aggregate counters in Google Firebase Realtime Database for:
- the entry and collection;
- the calendar day;
- the country code supplied by the hosting/network provider; and
- the hostname of the referring website, when the browser provides one — the full referring address is reduced to a hostname before storage.
The server uses the IP address and user-agent only to create a keyed hash that discourages repeat counting within a 12-hour period. That hash is kept in server-process memory for de-duplication and is not written as a raw IP address or user-agent to the readership database. Known bots, prefetch requests and operator sessions are excluded by the application where they can be recognised.
Readership counters help me understand which work is useful and where readers arrived from in aggregate. They are not used to build visitor profiles or target advertising. Because the stored counters are aggregated, I generally cannot identify or remove one person’s contribution to a counter after it has been added.
4.3 Content and external media requests
Pages, images and files may be delivered from Notion or other media hosts. Entries can also contain YouTube embeds or remote media. When your browser loads that content, it communicates with the relevant host, which receives normal network and browser information and may set its own cookies or use similar technology under its own policy.
4.4 Owner-only administration
Operator sign-in uses HttpOnly session cookies and, where enabled by the operator, a trusted-browser cookie bound to browser/network context. Authentication alerts and administrative notifications may be sent to the operator through Telegram. Visitor browsing does not create an account or an administrator session.
5. Cookies and browser storage
Cookies are small files stored by your browser. Local storage, session storage and Cache Storage are browser storage areas controlled by this site’s code. The site uses the following first-party items for functionality, remembered preferences, offline reading and security:
| Name or key | Type | Purpose | Duration |
|---|---|---|---|
pm-cookie-notice | Cookie | Remembers which version of the cookie notice you acknowledged | 1 year |
pm-theme | Cookie + local storage | Light/dark appearance | Cookie: 1 year; local copy until cleared |
pm-desktop-wallpaper | Cookie + local storage | Selected desktop wallpaper | Cookie: 1 year; local copy until cleared |
pm-wallpaper-intensity | Cookie + local storage | Wallpaper visibility intensity | Cookie: 1 year; local copy until cleared |
pm-wallpaper-slideshow | Cookie + local storage | Wallpaper slideshow on/off | Cookie: 1 year; local copy until cleared |
pm-wallpaper-interval | Cookie + local storage | Wallpaper slideshow interval | Cookie: 1 year; local copy until cleared |
pm-window-layout-v2 | Local storage | Desktop window position, size and maximised state | Until cleared |
pm-content-bookmarks-v1 | Local storage | Entries you save, including entry title, date, description and image reference | Until removed or cleared |
pm-listing-prefs-v1:<collection> | Local storage | Collection view and sort choices | Until cleared |
pm-reader-preferences-v1 | Local storage | Reader text size, line height, serif and contrast choices | Until cleared |
pm-reader-outline-v1 | Local storage | Whether the reader outline is shown | Until cleared |
quiz_status_<id> | Local storage | Quiz completion, score and completion date | Until cleared |
pm_commenter | Cookie | Guest-comment name, email and optional handles for prefill | 180 days |
pm_comment_draft:<page> | Session storage | Unsent comment draft for that entry | Browser session/tab lifetime |
pm_rdr_seen:<type>:<slug> | Session storage | Avoids repeating the read pulse for an entry in the same session | Browser session/tab lifetime |
pm-core-v3 | Cache Storage | Essential offline page, app manifest, font and core icons | Until cache-version cleanup, Settings clear, or browser eviction |
pm-static-v3 | Cache Storage | Same-origin scripts, styles, fonts and public text assets needed to reopen cached pages | Until cache cap/version cleanup, Settings clear, or browser eviction |
pm-pages-v3 | Cache Storage | Public HTML pages you have visited, for offline reading | Until cache cap/version cleanup, Settings clear, or browser eviction |
pm-images-v3 | Cache Storage | Public same-origin images shown on pages you have visited | Until cache cap/version cleanup, Settings clear, or browser eviction |
pm-pwa-install-hint-v1 | Local storage | Counts workspace visits and remembers whether the one-time install hint was dismissed | Until cleared |
Owner session/trust cookies | HttpOnly cookies | Operator authentication and optional trusted-browser recognition | Session default 12 hours; trust default 30 days |
pm_admin_hint | Cookie | Non-sensitive boolean hint ('1') set only after operator sign-in so public visitors skip session checks | Matches operator session (default 12 hours) |
The service-worker caches contain copies of public pages and assets already delivered to your browser. API responses, form submissions, the Bookmarks page and owner tools are not stored in or served from those caches.
The site does not use first-party advertising or cross-site tracking cookies. Third-party media or avatar hosts may use their own technology when your browser requests their content, as described in section 4.3.
You can delete or block cookies and site storage in your browser settings. The Reset preferences on this device control in Settings clears this site’s named cookies and local storage and removes visited offline pages and images. Reading public content does not require accepting optional preferences, but blocking storage can prevent appearance, window layout, saved items, reader preferences, offline reading and commenter prefill from persisting.
6. Why I use personal data
I use the information described above only for these purposes:
- to present the portfolio, articles and interactive workspace;
- to remember preferences and items you choose to save;
- to publish, attribute and moderate comments you choose to post;
- to receive, respond to and administer enquiries;
- to count readership in aggregate and improve the site;
- to prevent spam, abuse, unauthorised access and technical misuse;
- to maintain security, diagnose faults and keep proportionate operational records; and
- to comply with a legal obligation or protect legal rights where necessary.
Where a legal basis is required, I rely as appropriate on your consent for information you voluntarily submit or ask the browser to remember, my legitimate interests in operating, securing and improving a public portfolio, and legal obligations. You may withdraw consent for browser-saved information by clearing it; withdrawal does not automatically erase a comment or message already sent, but you may request deletion under section 10.
7. Who receives information
I do not sell or rent personal data. Information is disclosed only to service providers and recipients needed for the purposes above:
| Recipient | Role on this site |
|---|---|
| Vercel | Hosting, content delivery and request processing for the current deployment |
| Notion | Content management; native comment records; the operator's private workspace records |
| Google Firebase | Aggregate readership counters and hidden-comment moderation state |
| Telegram | Delivery of contact enquiries/attachments and operator notifications |
| Cloudflare | Turnstile bot-protection verification for protected actions |
| GitHub, FXTwitter and Unavatar | Public avatar lookup when you supply a supported comment handle |
| YouTube and remote media/avatar hosts | Delivery of embedded videos, images and avatars requested by your browser |
These providers act under their own terms and security practices. I may also disclose information if required by law, to respond to a lawful request, to protect people or property, or to establish, exercise or defend legal claims.
8. International processing
I operate the site from Sri Lanka, but the providers above may process and store information in other countries, including countries whose privacy protections differ from Sri Lanka. By using an interactive feature that relies on one of those providers, your information will be transmitted as technically necessary to provide the feature.
9. How long information is kept
- Browser storage: for the periods in section 5, or until you remove/clear it.
- Contact enquiries: only for as long as reasonably needed to respond, administer the enquiry and keep a proportionate correspondence record; Telegram also retains delivered messages under its own operation.
- Comments: while the relevant entry/comment remains published or retained for moderation and records, until I remove it or accept a deletion request. A hidden comment can remain in the underlying comment store while it is hidden from public view.
- Aggregate readership: until I reset or delete the aggregate counters; individual contributions are not separately identifiable in the stored totals.
- Moderation/security records: for as long as reasonably needed to moderate the comment, prevent abuse and protect the site.
- Host/provider logs: according to the relevant provider’s operation and retention schedules.
Backups, provider systems and content copied or quoted by others before deletion may take additional time to disappear and may not be within my sole control.
10. Security
I use proportionate measures such as HTTPS, restricted owner authentication, HttpOnly administrator cookies, rate limits, input validation, public-field stripping for comment email addresses and provider access controls. No internet service or transmission method is completely secure. Please do not submit highly sensitive information through public comments or the contact form.
11. Your choices and rights
You can contact me to ask, where applicable:
- what identifiable information I hold about you;
- to correct inaccurate information;
- to delete a comment, enquiry or other identifiable record;
- to restrict or object to a particular use; or
- to withdraw consent for future use of information you voluntarily provided.
I may need enough detail to locate the record and reasonably verify that the request relates to you — for a comment, the entry address and email address used are normally sufficient. I will respond within a reasonable time. Some information may need to be retained where required for security, accounting, legal claims or another lawful obligation, and aggregate read counts generally cannot be traced back to one visitor for removal.
For browser-held data, the quickest route is to use Forget me in the comment composer, Reset preferences on this device in Settings, or your browser’s site-data controls.
If you are in Sri Lanka, you may also contact the Data Protection Authority of Sri Lanka about data-protection concerns. Visitors elsewhere may have a right to contact their local data-protection authority.
12. Children
This is a general-audience portfolio and is not directed at children. If you are under 18, please obtain a parent’s or guardian’s permission before sending personal information through comments or the contact form. If I learn that a child’s personal information was submitted without appropriate permission, I will delete it where reasonably practicable after being notified.
13. External links and embeds
Entries may link to or embed material from other websites. I do not control those sites’ privacy practices. Please review the policy of any external service you visit or use.
14. Changes to this policy
I may update this policy when the site’s features, providers or legal obligations change. The updated version will be published on this page with a new “last updated” date. Material changes to cookie or storage use will be highlighted through a new version of the site’s cookie notice. Please review this page periodically.
15. Contact
For a privacy question or request, use the Contact page and include “Privacy” in the subject where possible.
