Skip to content

JRAM

  • Work
  • About
  • Contact
  • FAQ
JRAM

Legal

Privacy & Legal

Last updated 28 September 2026

On this page

  • Part One: This Website
  • Part Two: Client Projects
  • Your Rights
  • International Transfers
  • Security
  • How Long Things Are Kept
  • Copyright
  • Contact
Back to the site

This is the personal portfolio of Joshua Ramdhanie (JRAM), a web developer based in Trinidad and Tobago. This page covers two separate things: how I handle information on this site, and how I handle information inside the client projects I build. They work differently, so they’re set out separately.

Part One: This Website

What This Site Collects

  • Anything you send me. If you email me or use a contact form on this site, I receive your name, email address and message, and I keep them so I can reply and refer back to them.
  • Server logs. My host records IP address, browser type, referring page and the URLs requested. That is standard for any web server and is used for security and troubleshooting.
  • Visit statistics. Google Analytics, connected through Google’s Site Kit plugin, records how the site is used: pages viewed, device and browser type, approximate location and how you arrived. It sets cookies to do this. I use it to see which pages are useful, not to profile individual visitors.
  • Essential cookies. WordPress and the caching layer may set cookies needed to serve pages. There are no advertising cookies on this site.

What This Site Does Not Do

  • No selling, renting or trading of your information.
  • No advertising networks or ad-tracking pixels.
  • No advertising or marketing profiles built from your visit.

Services That Touch This Site

  • Hostinger hosts the site and processes server logs on my behalf.
  • Google Fonts serves the typefaces, so your browser makes a request to Google to fetch them.
  • Google Analytics measures visits as described above. Google’s own privacy policy covers the data it collects.
  • Outbound links to LinkedIn and to project sites hand you over to services with their own policies. Once you leave, theirs applies, not mine.

Part Two: Client Projects

Who Is Responsible For What

When I build or maintain a website for a client, the client decides what personal data their site collects and why. In data protection terms the client is the controller and I act as a processor working on their instructions. I do not use client visitor data for my own purposes, and I do not keep it after an engagement ends unless the client asks me to.

Access And Credentials

Building and maintaining a site means I usually hold administrative access to it. I treat those credentials as confidential, I do not share them, and I hand over or surrender access at the end of an engagement on request. Where a project involves a database of real people, I work against test or anonymised data wherever the task allows.

Subprocessors

Client work commonly involves third-party services such as hosting, email delivery, backups and error reporting. Where such a service processes personal data on a client’s behalf, that relationship needs its own agreement between the client and that provider, and I will tell the client which services a build depends on before it goes live.

Written Terms

This page is not a contract. Anything I take on is governed by what we agree in writing for that project, including who is responsible for data protection obligations, what happens to data at the end, and what I am and am not liable for.

Your Rights

You can ask me what information I hold about you, ask me to correct it, ask for a copy, or ask me to delete it. Email the address below and I’ll take care of it. I don’t charge for this.

Trinidad and Tobago. The Data Protection Act 2011 governs personal information here. Note that the Act is only partially in force: Part I and a set of sections in Part II and Part III were brought into operation in 2012, and the remainder has not been proclaimed. I follow its general privacy principles anyway. Oversight sits with the Office of the Information Commissioner.

UK and EU visitors. The GDPR applies to organisations outside Europe when they offer services to, or process the data of, people in Europe. If you are covered by it, you have the rights to access, rectification, erasure, restriction, portability and objection, and you may complain to your national supervisory authority. My lawful basis for replying to your message is legitimate interest in responding to an enquiry you started; for client work, it is the performance of a contract.

Opting out of analytics. You can block analytics cookies in your browser settings, or install Google’s Analytics opt-out browser add-on, and the rest of the site will work exactly the same.

International Transfers

My hosting and email providers may store or process data on servers outside Trinidad and Tobago. Where that involves personal data from the UK or EU, the transfer relies on the provider’s own safeguards, such as standard contractual clauses.

Security

The site runs over HTTPS. Administrative access uses strong, unique credentials, and I limit who holds access to any project to the people who actually need it. No system is perfectly secure, but if a breach affected your personal information I would tell you and the relevant authority without undue delay.

How Long Things Are Kept

Messages are kept while they’re useful to the conversation or project they belong to, and are deleted on request. Server logs rotate on the host’s schedule. Analytics data is kept by Google for the retention period set on my Analytics account. Client project data is retained only for the life of the engagement unless the client instructs otherwise.

Copyright

The design, code and writing on this site are mine unless stated otherwise. Project names and screenshots belong to the projects and organisations they represent and appear here to describe work I contributed to. If you own something shown here and want it removed, contact me and I will take it down.

Contact

For anything on this page, including data requests and takedowns, email josh@jnram.com.

Back to the site

© 2026 JRAM

  • Work
  • About
  • Contact
  • FAQ