Last updated: 5 October 2026
This site is run by Richard Hodgson, a sole trader based in Cleckheaton, West Yorkshire, United Kingdom, trading as Point of Control. Richard Hodgson is the data controller for the information described below. Point of Control is a trading name, not a separate company.
To ask about anything here, contact privacy@pointofcontrol.app.
POC has no accounts and no database. There is nothing to sign up for, no password, no email address to give me, and nowhere on my side that your work is stored. I don’t use cookies at all, I don’t run advertising, I don’t sell data, and I don’t share it with anyone for marketing.
Everything you type into a tool stays in your browser. The only information that reaches me is the ordinary technical data any web server records, plus anonymous usage totals that cannot identify you.
All the tools, lessons and glossary work without an account. Three things are stored by your browser, and none of them is ever sent to me:
| What | Where | Why |
|---|---|---|
poc-theme | Local storage | Remembers whether you chose light or dark |
poc_scenarios | Local storage | Plans you save in “My scenarios”, kept on your device only |
poc_map | Local storage | Your trading map — the strategy, figures, risk settings and goals you enter, either on the map itself or by saving them from a tool. It never leaves your device, and I cannot see it or recover it |
All three exist because you asked for them — a theme you selected, and work you chose to save. You can clear them at any time in your browser settings, and the trading map has its own delete button. Because they live only in your browser, clearing them deletes that work permanently, and it will not be there if you open POC on another device or in a private window.
Nothing in your browser measures you. There is no analytics script on this site — nothing that runs on your device to count you, and nothing loaded from an analytics company.
I use Cloudflare Web Analytics, which works server-side. Cloudflare already delivers these pages, so it counts the requests it is already handling. It is cookieless by design and stores nothing on your device. There is no analytics beacon to block, because the counting does not happen in your browser at all.
One script is on the page, and it is worth being precise about. Cloudflare adds a small piece of JavaScript that scrambles email addresses in the HTML and unscrambles them for you, so that automated scrapers cannot harvest them. It is served from this site, it measures nothing, it stores nothing, and it is not analytics. With JavaScript turned off the addresses are still written out in plain text on the pages that give one — you just cannot click them.
What it tells me, and that is the whole of it:
| What | What it tells me |
|---|---|
| Page views | Which pages were opened, and how often |
| Referrer | The site that linked you here, where one did |
| Country, browser, device type | Coarse buckets only — never anything that narrows down to a person |
| Page performance | How quickly pages loaded, so I can tell if the site is slow |
I cannot tell whether you have been here before. There is no identifier, no cookie and no stored state, so a return visit is indistinguishable from a first one. I see totals rising or falling. I cannot follow anyone between visits, and I could not single you out if I wanted to.
I do not record the numbers you type into any tool, the plans you save, the results a tool produces, where your mouse moves, or anything identifying you. There are no session recordings and no scroll tracking.
What changed, and why this page got shorter. Until 5 October 2026 this site used Plausible Analytics, which loaded a script and recorded a list of named events — which tool was opened, which lesson, whether a suggested next step was taken. That has been removed. Cloudflare supports no custom events at all, so those are simply no longer collected by anyone. The trade is less detail for me and less of your browser involved, and on a site this size the detail was never telling me much.
Like any website, POC runs on servers that keep ordinary access logs. These are generated by my hosting provider as a normal part of delivering pages and can include IP addresses, timestamps and which page was requested. I do not use these logs to build a picture of individuals, and they are not combined with anything else. These logs are the only personal data POC involves, apart from an email you choose to send me.
If you write to privacy@pointofcontrol.app, I hold your message and your email address for as long as it takes to deal with it, and for a reasonable period afterwards in case you follow up. I don’t add you to any list — there isn’t one.
Separately from this site, I take on paid technical work — see services. If you hire me, I necessarily hold more than the site does: your name and contact details, the scope document, correspondence, invoices, and whatever material you send me for the job.
I use it to do the work you asked for and for nothing else. It is not used for marketing, not added to any list, not used in my own research, and not shared with anyone. Invoices and the records behind them are kept for six years because tax law requires it. Project material is deleted on request once the work is finished, and the terms say the same about data held under the off-site backup service.
AI tools are used in that work and your material may pass through them, under terms that do not permit it to be used to train models. This is set out properly in the terms, and you can ask for an engagement to run without them before scope is agreed. None of this applies to visiting the site — nothing you type into a tool reaches me at all.
POC sets no cookies whatsoever. Not for signing in — there is no sign-in. Not for analytics — the analytics are server-side and there is no script. Not for advertising — there is none.
That is why you have never seen a cookie banner here: there is nothing to ask you to consent to.
| Service | What it does |
|---|---|
| Cloudflare | Hosts the site; produces the server logs described above |
| Cloudflare (analytics) | Server-side page counts, from the requests Cloudflare already handles to deliver these pages. Same company as the hosting above — listed separately only because it is a different purpose |
That is the complete list — and as of 5 October 2026 it is one company, which is the shortest this list has ever been. Cloudflare processes data under its own standard data-processing terms. It runs global infrastructure, so the technical logs described above may be processed outside the UK — where they are, that transfer relies on the UK International Data Transfer Addendum to the European Commission’s standard contractual clauses, which forms part of Cloudflare’s data-processing terms.
I do not sell data, share it with advertisers, or use it for advertising or profiling. POC currently carries no advertising and no affiliate links; if that changes, this page will be updated first.
The law requires me to tell you the basis I rely on, not just what I hold. In plain terms:
Where I rely on legitimate interests you can object, and I will stop unless there is a compelling reason not to. For the site there almost never will be.
Under UK data protection law you can ask me for a copy of your data, to correct it, to delete it, to restrict how I use it, or to object to my using it. There is no charge and I will respond within one month.
In practice I hold very little: the server logs described above, and any email you have sent me. Because there are no accounts, I usually have no way to connect a request to a particular visitor — if you ask me to find something, I may need details from you to identify it, and sometimes there will simply be nothing to find.
Contact privacy@pointofcontrol.app.
If you are unhappy with how I have handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk.
POC is not aimed at children and I do not knowingly collect data about them.
If this policy changes I will update the date at the top, and note anything material on this page.