These live in config/privacy.json. Until they are filled in, this page describes what happens to your data but does not fully identify who is responsible for it.
The short version: this site does not use Google Analytics, does not set tracking cookies, does not sell anything about you, and does not load a single asset from a third-party server. Fonts, scripts and statistics all come from this domain. What follows is the long version, because you are entitled to it.
Who is responsible. The controller of this data is not yet stated. For anything on this page — access, correction, deletion, objection — use the request form below. EU representative (Art. 27): not yet stated
Every page view is counted, by software running on this server. Here is exactly what is recorded, and it is deliberately little:
What is not recorded: your IP address, your full User-Agent string, and any identifier that survives the day. To count "visitors" rather than "page views", the server computes a hash of your IP address, your User-Agent and a random secret that is regenerated every day and never stored after that day ends. Once the day turns over, nothing in the statistics can be connected back to you, to your IP address, or to what you did yesterday. There is no cookie, nothing is written to your device, and no data leaves this server.
The practical consequence: if you write to us asking for a copy of your analytics data, the honest answer is that we cannot find any, because there is no identifier to search on. We are not allowed to start collecting more information about you just to be able to answer such a request (Art. 11), and we will not.
You do not have to justify this and nothing on the site stops working if you do.
Checking…
Your browser can also say this for you: if it sends a Global Privacy Control
(Sec-GPC) or Do Not Track signal, this server honours it and records
nothing at all. Most browsers that offer either setting have it off by default; both are respected
here without you having to ask.
The diagnostic is a questionnaire that computes a score with fixed rules. You can complete it and read the entire report without giving us any contact details.
Your answers and the resulting report are stored on this server under a random report ID, so that the report link keeps working when you come back to it. On its own that record contains no name and no email — it says which options someone picked, nothing about who. Anyone with the link can open the report, so treat the link the way you would treat any private link.
The diagnostic produces a score and a recommendation by fixed arithmetic. It is not a decision about you in the sense of Art. 22 — nothing is granted, refused or priced on the basis of it, and no profile is built. It is a worksheet.
Then we hold your email address, the name and message you chose to type, the report it was attached to, and a record of the consent itself: the exact sentence that was on screen when you ticked the box, the version of that sentence, and the time. That consent record exists because we have to be able to show that you actually agreed (Art. 7(1)).
The legal basis is your consent, and consent can be withdrawn at any moment, which costs nothing and requires no reason. Withdrawing stops future emails; it does not retroactively make the earlier ones unlawful. Every email we send carries a working unsubscribe route, and writing to the request form below works just as well.
We do not store your IP address or your browser's User-Agent with the lead. Both were once collected "in case they were useful for debugging"; they never were, so they are no longer collected.
The box on the front page takes a sentence in your own words and matches it against cases already in the index. What you typed is stored, together with the tags our matcher read out of it and the cases it matched — not to profile you, but because it is the honest answer to "what are people actually trying to build", which is what decides where this index goes next.
You can use that box without leaving an email, and if you do, the entry has nothing in it that points at a person: just a sentence and some tags. No IP address, no User-Agent. If you do add an email so we can send matching cases, that is consent, recorded the same way as in §3 and withdrawable the same way.
One caution that applies to any free-text box, ours included: please do not type things you would not want stored — client names, private figures, anything about your health or your staff. We do not want that data, we have no use for it, and the safest way for it not to leak is for it never to arrive. If you already typed something you regret, write to the request form below and it will be deleted.
Ad slots on this site are served by an ad server run by the same operator, on the operator's own infrastructure. Ads here are contextual: what is shown depends on the page, never on a profile of you, and we do not build, buy or sell audience segments.
To avoid showing you the same ad over and over, we would like to keep one random ID in your browser's local storage. That is storage on your device, so we ask first, and we only ask because we have to: it is not needed for the site to work. If you decline, ads still appear — they are simply not capped, so you may see one more often. If you accept and later change your mind, "Storage choices" in the footer of every page removes the ID immediately.
| Name | Type | What it is for | Consent | Lifetime |
|---|---|---|---|---|
aimi_consent | local storage | Remembers whether you accepted or declined the ad frequency ID, so we stop asking. | Not required — without it we could not honour your answer | Until you clear it |
aimi_uid | local storage | Random ID used to cap how often an ad is repeated. Contains nothing about you. | Required — only written after you accept | Until you clear it or decline |
aimi_optout | local storage | Set only if you use the opt-out button above; tells the page not to count the visit. | Not required — it exists solely to carry out your own request | Until you clear it |
aimoney_admin | cookie | Signed login session for the site operator's own admin dashboard. Visitors never receive it. | Not required — strictly necessary for a login | 7 days |
That is the complete list. There is no analytics cookie, because the analytics do not use one.
| Data | Why | Legal basis | Kept for |
|---|---|---|---|
| Page-view statistics (no identifiers) | Knowing which pages and sources are worth the effort | Legitimate interest, Art. 6(1)(f) — measurement with no cross-day identifier and no third party | 180 days, then deleted automatically |
| Diagnostic answers and the report | Producing the report and keeping its link working | Art. 6(1)(b) — the thing you asked for | Until you ask us to delete it, or the lead it belongs to is deleted |
| Email, name, message, consent record | Sending you the report and follow-ups | Consent, Art. 6(1)(a) | Until you withdraw; reviewed after 24 months of no contact |
| Copies of emails we sent you | Being able to show what was sent | Legitimate interest, Art. 6(1)(f) | 90 days |
| Author names and excerpts in the case index | A searchable index of publicly posted stories, each linking back to its source | Legitimate interest, Art. 6(1)(f) | Until removed on request — see §9 |
No analytics company, no ad network, no tag manager, no CDN, and no font service. Fonts are served from this domain precisely so that reading this site does not tell Google that you did.
The people who can technically reach the data are the operator, the hosting provider on whose machine it sits, and, once email is switched on, the mail provider that delivers it. Every such processor is listed below with the agreement that covers it (Art. 28). If an ad slot ever falls back to a third-party ad network, that network becomes a separate controller and this notice has to be updated to name it — as of the date below, none is in use.
| Processor | What they do | Country | Art. 28 agreement |
|---|---|---|---|
| Google Cloud Platform (Google LLC) | Hosting / infrastructure (Compute Engine, us-central1) | US | no agreement on file |
This site indexes stories that people published themselves on public forums. An entry holds the title, the link, the author's handle on that platform, a short excerpt, and figures the software extracted from the text. We do not republish article bodies, and every entry links back to the original.
You did not give us anything and we never asked you, so you should know two things. First, the basis for holding it is legitimate interest (Art. 6(1)(f)) — an index of public business writing. Second, and more usefully: you can object under Art. 21 and we will simply remove you. Write to the request form below with the link or your handle. Removal is permanent: entries are added to a block list, so the next crawl does not put them back. No justification is needed and we will not argue the point.
Use the request form below. You will get an answer within one month (Art. 12(3)). None of this costs anything, and you do not have to explain why. If the answer does not satisfy you, you can complain to the data protection authority in your own country — in the EU, the list is published by the European Data Protection Board — or go to court. You do not have to come to us first.
This form goes straight to the operator's dashboard, where it is timed against the one-month deadline. Nothing about this form is logged in the site statistics.
We keep the request itself until it is settled plus three years, because being able to show that a request was answered is the only proof that it was. That record holds what you typed here and nothing else.
Everything described here lives in files on the server that runs this site. The admin dashboard is behind a password and a signed, HTTP-only session cookie, with rate-limited logins. The data directory is not reachable from the web: only the public case index is served, and every other file in it returns 403.
Hosting: Google Cloud Platform (Google LLC) (US) — outside the EEA, covered by: Standard Contractual Clauses under the Google Cloud Data Processing Addendum.
If what we do with data changes, this page changes first, and the version number attached to the consent text goes up, which means anyone who consented under the old wording is asked again rather than silently carried over.
Last updated: 2026-08-31.