This policy covers reidmorrison.com, the website of
Reid Morrison Inc., a Florida corporation. It does not cover the
project documentation sites on subdomains, which serve open-source
documentation and are described below, and it is not the confidentiality term
in a client agreement: how client code and client data are handled is set out
on our security page and in the
agreement itself.
The short version
No cookies are set by this site. No analytics, no tag manager, no tracking pixel, no advertising network, no session recording, no fingerprinting. Nothing is written to your browser’s storage.
There is no account to create, and nothing to opt out of, because nothing is being collected in the first place. If you send an enquiry or book a call, we receive what you typed and nothing else.
Who your browser contacts
Loading a page means asking somebody for it, so visiting this site means a small number of other companies can see your IP address and your browser’s user agent. Each is here because the site needs it to work, and each publishes its own statement.
| Third party | Why it is involved | When |
|---|---|---|
| GitHub Pages | Hosts and serves this site. GitHub keeps its own server logs of requests, which we do not receive and cannot read. | Every page |
| Google Fonts | Serves the three typefaces the site is set in. Google states that the Fonts API logs requests and does not set cookies. | Every page |
| Web3Forms | Receives a submitted form and forwards it to us as email. It sees whatever you put in the fields. | Only when you press Send on a form |
| Google Calendar | Runs the booking page and creates the meeting. Everything from the click onward happens on Google's own page, under Google's terms. | Only when you follow "Book a video call" |
Nothing else is embedded. No fonts, scripts, images or frames are loaded from anywhere other than this site and the sources above.
The EOL exposure check
The check at /eol/ runs entirely in your
browser. The versions you select never leave the page: the dates, the days
unpatched, the controls and the upgrade path are all computed locally, nothing
is uploaded, and nothing is saved.
That is a property of how the page is built rather than a promise we are asking you to take on trust. The site is static and has no backend to receive anything, and you can confirm it in your browser’s network tab in about ten seconds. Printing the finding is your browser printing a page, not a request to us.
The check carries a separate, clearly marked form. That form is the only part of the page that sends anything anywhere, and only if you fill it in.
If you send us an enquiry
The forms on the contact page and on the EOL check ask for your name, work email, company, the version you are running, what is forcing your timeline, and anything else you want to add. They are the same questions we would ask on a first call, and they exist so that the reply is specific rather than generic.
What happens to it. It reaches us as email, through Web3Forms, and it is answered by a person. It is used to reply to you and to prepare for a conversation, and for nothing else. It is never sold, rented, shared for anyone else’s marketing, or added to a mailing list. There is no automated sequence, and pressing Send does not subscribe you to anything.
How long it is kept. While the conversation is live, and afterwards as a business record if it becomes an engagement, under the seven-year retention described on our security page. If it does not become an engagement and you would rather it were not kept, ask and we will delete it.
Ask us anything about it. To see what we hold about you, correct it, or have it deleted, use the contact form, or write to the address at the foot of this page. We do not require you to prove a legal basis for asking.
The documentation subdomains
Six subdomains (logger, encryption, rocketjob, config, iostreams and
minion) serve documentation for open-source Ruby libraries. They are static
sites hosted the same way, they set no cookies either, and they exist to
document software rather than to sell anything.
Changes to this policy
This page is dated at the top, and material changes are listed here rather than made quietly.
- 3 September 2026. First published.