Trust Centre

Privacy, security and legal information for andy.boura.uk

This site is run by Andy Boura as a private individual, not trading. It is not run by, or on behalf of, any employer or company. Views on it are my own, not my employer's, and nothing on it is investment advice.

At a glance

  • No cookiesNothing is stored in your browser
  • No trackingNo analytics scripts, adverts or third-party scripts
  • One formThe blog's optional mailing list; no accounts, logins or comments
  • 90 daysRequest logs are deleted automatically

andy.boura.uk is my personal site: a profile page, a page about the companies I have invested in, and a blog of my articles and talks, with an RSS feed and an optional mailing list. The pages are static: plain files served over HTTPS. The mailing list is the one part that keeps anything you give it: your email address, if you choose to join.

Privacy

I, Andy Boura, am responsible for the personal data this site handles, acting as an individual and not trading.

What is collected

No cookies, analytics scripts, adverts or third-party content. Like almost every website, the site keeps a log of the requests it answers, including your IP address, the time, the page requested, the page that linked to it and your browser type. The logs are private and are deleted automatically after 90 days.

From the logs, the site produces anonymous statistics about how it is used, such as how often each page is viewed, how visitors move from page to page, and which sites they arrive from (by the site's name only, and only for sites many visitors arrive from). It keeps only these totals: not your IP address, your browser or anything else about you, and no record of the pages any one visitor saw. The statistics are not personal data, so they are kept indefinitely, with a nightly backup.

The blog's Listen button reads an article aloud with your own device's voice: your browser does the reading, and the site receives nothing from it. If you choose a voice marked "online", your browser may send the text it reads, which is the published article, to the company that provides that voice, under its own terms; the site has no part in it. With autoplay on, the player fetches the next article from this site, as following its link would. Nothing about your listening is stored, in your browser or on the site.

If your browser blocks something on a page because of the site's security policy, it may send the site a short report. From each report the site keeps only which rule was broken, where the blocked content came from and which page it was on: not your IP address, your browser or anything else about you. These records are deleted automatically after 30 days.

If you join the mailing list

The blog's sign-up form asks for your email address and nothing else. It sends you one email with a link; you join only if you open it and press its button, so no one can sign you up without you. After that the list sends you each new post, from blog@andy.boura.uk: each email holds an item's title, a summary and a link. The emails contain no tracking: nothing records whether you open them or follow their links. Every email has a link to unsubscribe, which also works in one click from most mail apps.

What is kept: your email address, a random ID for you, when and where on the site you signed up, and which version of the sign-up wording you saw (that is the record of your consent); and, for each email sent, a copy of the email and the IDs of the people it went to, with whether it was delivered or bounced.

How long: your address is kept for as long as you stay subscribed. When you unsubscribe, or your address bounces for good or you report an email as spam, your address is deleted; only a scrambled form of it (a hash) is kept, so the record of what was sent stays complete. You can sign up again at any time. If you never confirm a sign-up, your address is deleted within a week. If you ask me to erase your data, I delete it.

The lawful basis is your consent, given by confirming, which you can withdraw at any time by unsubscribing; and, for the record of what was sent and the limits on sign-ups, my legitimate interest in showing what was sent and stopping misuse of the form. Amazon Web Services stores the list and sends the emails on my behalf, in the United States; no mailing list company is involved, and the list is never shared, sold or used for anything but these emails.

How it is used

The request logs and reports are used only to keep the site working and secure, to investigate errors, abuse and attacks, and to produce anonymous statistics about how the site is used. The lawful basis is my legitimate interest in running a secure website and in understanding how it is used, so I can improve it. Producing those statistics is a statistical purpose, which the law treats as compatible with the reason the logs are kept (Data (Use and Access) Act 2025, section 71). Nothing is sold, used for advertising or used to profile visitors, and individual IP addresses are not copied out of the logs.

Who else is involved

Amazon Web Services hosts the site and stores the logs, incoming mail and the mailing list on my behalf, in the United States, under its data processing terms. Links to other sites, such as LinkedIn, X, the companies on the investments page, the talks and articles listed on the blog (on YouTube, for example) and the Share menu's links, take you to services with their own privacy terms; nothing is sent to them unless you follow a link.

If you email me

Mail to the trust centre address below goes straight to my own mailbox, which Google hosts. Google checks it for spam and viruses and stores it in its data centres, which may be outside the UK, under its own data processing terms. Mail to an andy.boura.uk address, such as a reply to one of the mailing list's emails, is received by Amazon Web Services, which checks it for spam and viruses, keeps it for 7 days and forwards it to that same mailbox. The lawful basis is my legitimate interest in reading and answering mail you choose to send.

Your rights

You can ask for a copy of data about you, ask me to correct it if it is wrong, ask me to delete it, ask me to restrict how it is used, or object to its use.

Before acting on a request I will ask you to show that the data is yours, so that no one can obtain or delete someone else's. For request logs, that means showing you control the IP address concerned, for example by opening a link I send you from that connection, and telling me roughly when you visited, within the last 90 days. For mail and the mailing list, it means writing to me from the email address concerned.

Complaints

If you are unhappy with how your data has been handled, please tell me first, at andy+trustcentre@boura.uk. I will acknowledge your complaint within 30 days and look into it without undue delay. You can also complain to the Information Commissioner's Office at ico.org.uk.

Changes to this notice

This notice may be updated from time to time. The date it was last reviewed is at the foot of the page.

Security

The site is deliberately simple, so there is little to attack: no logins and nothing to upload. The one data store is the mailing list's, holding what the Privacy section describes, and readable only by the list's own functions and the account's administrators.

How a page reaches you

  • Your browserHTTPS only, modern TLS
  • Delivery networkAdds strict security headers to every response
  • Private storagePages readable only by the delivery network; the mailing list only by its own functions

How a change goes live

  • CodeSite and infrastructure defined as code
  • ReviewPull request and automated checks
  • StagingChecked on a test copy first
  • ProductionShort-lived, narrowly scoped deploy access

In the browser

The page loads only its own files, and fetches only this site's own pages (the Listen player's autoplay and the blog's one check that its sign-up form has somewhere to post to); the sign-up form posts only to this site. Security headers tell your browser to use HTTPS, refuse framing and content sniffing, keep other sites' windows apart, and turn off features the page does not need, such as the camera, microphone and location.

Controls behind the scenes

  • Access: least-privilege, role-based access control. Interactive access always requires multi-factor authentication, and automated deploys use short-lived credentials, issued only to this site's own repository and limited to its own storage. Each role's purpose and permissions are tracked and recorded.
  • Change: every change, to the site or to the hosting, is made in code, reviewed through a pull request with automated checks, and checked on staging before it goes live; earlier versions are kept, so a change can be rolled back.
  • Monitoring: account activity is recorded in a tamper-evident audit trail kept for a year, and threat detection, configuration recording and access analysis report anything unexpected.
  • Testing: automated tools watch the site's libraries and its build tools and propose updates; every change to the hosting is checked against security rules before it can deploy; and after every deploy an automated test confirms the security headers are in place.
  • Logs: request logs cannot be deleted early by anyone; only their 90-day expiry removes them.
  • Backups: the mailing list and the statistics are copied every night to a separate, locked backup store; each copy is kept for up to 90 days.

Keeping up to date

The libraries the site serves are pinned to exact versions and monitored for advisories. I aim to fix known vulnerabilities in them within these times, though as a private individual it may sometimes take longer:

SeverityTargetAt the latest
Critical1 day7 days
High14 days30 days
Medium90 days6 months
LowNext routine update12 months

If a fix for a critical or high vulnerability in them is not live by the latest date, the site goes offline and shows a short maintenance page until it is. Better briefly broken than vulnerable and open, because a few hours offline harms no one, while a known hole could harm everyone who visits.

Assessment

The site and its hosting are self-assessed against the OWASP Application Security Verification Standard 5.0, with a mapping to the OWASP Top 10, and kept up to date as things change.

Reporting a vulnerability

If you find a security problem, please email andy+trustcentre@boura.uk with enough detail to reproduce it. I aim to acknowledge reports within 5 working days and to fix confirmed problems within the times above, though as a private individual it may sometimes take longer. I do not offer a bug bounty.

In scope

  • andy.boura.uk
  • staging.andy.boura.uk
  • Testing that reads only what the site serves to everyone

Not permitted

  • Denial of service, load or flood testing, or anything that slows the site for others
  • Automated scanning at volume
  • Social engineering, phishing or contacting anyone other than me
  • Physical attacks, or attacks on hosting providers or other customers
  • Accessing, changing or keeping anyone else's data
  • Publishing details before the problem is fixed, or 90 days after your report, whichever comes first

If you keep to these rules and act in good faith, I will not pursue legal action against you for your research. This policy is also linked from the site's security.txt.

Contact

For privacy requests and security reports, email andy+trustcentre@boura.uk.

For anything else, find me on X or LinkedIn.