Privacy Policy

This policy describes the personal data involved when you read RCSI USA Tech Notes or send us an email, why it is involved and what you can ask us to do about it. The blog was built to need as little of your data as possible, so the list is short.

Who to contact

The blog is run by its small editorial team. Questions about this policy or requests about your data go to inbox@rcsi-usa.com. Please mention "privacy" in the subject line so the message is handled first.

How the blog is built

Each page is built ahead of time and served to you as a finished document. That design has consequences for privacy worth spelling out. There are no reader accounts or logins, no comment system, no shop and no database that records what you click. The blog also does not run:

• analytics or visitor-statistics software;
• advertising networks or affiliate trackers;
• share widgets that pull in scripts from social networks;
• fingerprinting, session recording or similar techniques.

Your cookie choice

On a first visit a small card appears with two buttons, accept and decline. Your answer is saved in your browser's local storage so the notice does not reappear on every page. The entry holds only that answer, stays on your device and is not sent to us. Details are on About Stored Preferences.

Hosting logs

Like any website, the blog is delivered by a hosting provider whose servers keep technical logs of requests. A log entry typically contains the IP address, the date and time, the page requested, the browser's user-agent string and whether the request succeeded. The provider uses these logs to deliver pages, keep the service secure and investigate faults, and keeps them only for a limited period. We do not combine the logs with other information or use them to build profiles of readers. We rely on a legitimate interest here: a blog that loads reliably and resists abuse.

When you email us

If you write to us, directly or through the form on the Send a Message page (which only opens your own email program), we receive your address, your name if you give it and whatever you write. We use that to read and answer your message and, where you report an error, to correct the article. We do not add you to any list, and we delete correspondence once it is no longer needed, unless a message documents a correction we may need to refer back to.

Links to other websites

Some articles link to outside websites. Clicking through takes you to a site with its own privacy rules, and what that site collects is outside our reach.

Your rights

Under the GDPR and comparable laws, you may ask us:

1. to confirm whether any of your personal data sits with us, and to receive a copy;
2. to fix details about you that are inaccurate or missing something;
3. to erase anything we have no remaining need for;
4. to restrict how we use it, or to object to a particular use;
5. to send you the data you supplied in a format another service can read.

Write to the address above and we will respond within the period the law allows. You also have the right to complain to the data protection authority where you live or work.

Children

The blog is written for a general audience and does not knowingly collect data from children. A parent who believes a child has written to us can ask us to delete that message.

Changes

If the way the blog works ever changes, for example by adding a feature that stores more data, this policy will be updated before the change goes live.

Last updated: October 2026.