In short
The New Energy Wire is a publication, not a service you sign into. As it stands today:
- We set no cookies. Not one, not even a "necessary" one.
- We run no analytics. No Google Analytics, no tag manager, no pixel, no fingerprinting.
- We store nothing in your browser — no
localStorage, nosessionStorage, no IndexedDB. - There is no account to create, no newsletter to join and nothing to pay for.
- We do not sell or share personal data, and there is no advertising on the Wire.
What is left is the small amount of data that any web server sees, the email you send us if you write to us, and the personal data that appears inside the news we publish. Each is covered below. If this page ever stops being true, it changes on the day the thing changes — not later.
1. Who is responsible for your data
The New Energy Wire is published by Colibri Holdings Ltd, a company registered in England and Wales under number 09741137, whose registered office is at 71 Queen Victoria Street, London EC4V 4BE, United Kingdom. Our VAT registration number is GB271861001.
- Data protection contact: hello@axiom.vc
- ICO registration: ZB415775
"AXIOM" is a brand, not a company. AXIOM, AXIOM Venture Capital and the AXIOM New Energy Wire are names under which Colibri Holdings Ltd publishes. They are not separate legal entities.
We are the controller for the personal data described here. We have not appointed a Data Protection Officer and are not required to; the person accountable is the director, and the address above reaches them.
Representative in the EEA. We make the Wire available to people in the European Economic Area, so Article 27 of the EU GDPR is engaged. We have not appointed a representative, and we rely on the exemption in Article 27(2): our processing of EEA personal data is occasional, it involves no special category data and no criminal-offence data, it is carried out on a small scale, and it is unlikely to result in a risk to rights and freedoms. The Wire has no accounts, sets no cookies and runs no analytics, which is most of why that is true. This is a position we have taken deliberately and recorded, and we keep it under review: if we add accounts, a newsletter or payments, it is revisited before that ships.
2. What we collect, why, and on what lawful basis
2.1 Reading the Wire
| What | Why | Lawful basis |
|---|---|---|
| IP address, user-agent, the page requested, the time, the referring page | Server logs kept by our hosting provider. Security, abuse prevention, and knowing whether the site is up | Legitimate interests — running a website securely (Art. 6(1)(f)) |
That is the whole of it. No cookie is set and no identifier is written to your device, so we cannot recognise you on a second visit and we do not try to. We do not build a profile of you, we do not know how many people read a given story as distinct from how many requests arrived, and we have deliberately accepted that we know less about our readers than most publishers do.
The search box on the Wire runs entirely in your browser against data already downloaded with the page. What you type into it is never sent to us.
2.2 Writing to us
The Wire has two mailto: links — one for feedback, one to report a problem. If you use either, you send us an ordinary email.
| What | Why | Lawful basis |
|---|---|---|
| Your email address, your name if you give it, and whatever you write | To read it, answer it, and fix what you told us about | Legitimate interests — answering correspondence (Art. 6(1)(f)) |
We keep correspondence for as long as it is useful and then delete it (see section 6). We do not add you to anything. There is nothing to be added to.
2.3 Personal data inside the news
This is the part of the Wire that processes the most personal data, and it is not about you as a reader.
The Wire reports on the energy transition: companies, projects, financings, policy and the people who run and decide them. Reporting necessarily names people — a chief executive quoted in a trade publication, a minister announcing a scheme, an analyst whose research we cite.
| What | Why | Lawful basis |
|---|---|---|
| Names, roles, employers and publicly reported statements and actions of people in the energy sector | Journalism: reporting what has been published, and keeping a record of it | Legitimate interests (Art. 6(1)(f)), and the journalism exemption — Schedule 2, Part 5, paragraph 26 of the Data Protection Act 2018 |
Where we get it. From the 191 sources described in clause 6.2 of the Terms: trade publications, company newsrooms, government and regulator announcements, and research publications. We do not buy personal data, we do not scrape social networks for it, and we do not enrich it against third-party databases.
Our register holds organisations, not individuals. The register behind the Wire currently holds 96 organisations and 37 recorded claims. Its records describe companies — name, country, domain, regions, roles, technologies — and are not built around named individuals. People appear in the stories, as they do in any publication, rather than as entries in a database about them.
Your rights when you are in the news. Sections 7 and 8 apply, subject to the journalism exemption, which exists because reporting could not work if everyone written about could require their removal. We take corrections seriously and separately: clause 6.1 of the Terms is how to get something fixed, which is usually faster and more useful than a data protection request.
3. What we do not do
Stated positively, because the absence is the point:
- No advertising, and no advertising technology.
- No analytics or measurement of any kind.
- No cookies, no pixels, no fingerprinting, no
localStorage. - No sale or sharing of personal data. No data brokers.
- No automated decision-making with legal or similarly significant effects about any reader.
- No newsletter, no accounts, no payment data.
4. Cookies and what is stored on your device
Nothing is. The Wire sets no cookies and writes nothing to browser storage, which is why you have not been shown a consent banner: there is no consent to collect, and a banner asking for permission we do not need would be theatre.
If that changes — if we add accounts, a saved preference, or any measurement — this section changes first, and anything that is not strictly necessary will ask before it is set.
Do Not Track and Global Privacy Control. We have nothing to honour these signals with, because there is nothing to turn off. If we ever add anything measurable, a Global Privacy Control signal will be treated as an objection to it.
5. Who else processes data for us, and where
| Provider | What they do | Personal data involved | Where processed |
|---|---|---|---|
| Render Services, Inc. (US) | Hosts the site and the relay | Server logs: IP address, user-agent, request | The relay runs in Frankfurt. The static site declares no region, so the provider's default applies and we treat it as US |
| Supabase, Inc. | Verifies operator identities for the people who edit the Wire | Editor email and role. No reader data | Ireland (eu-west-1) |
| DeepSeek | Generates and checks parts of the published text from source material | See §5.1 — published professional information, which can name people | People's Republic of China — a restricted transfer, see §5.1 |
| GitHub, Inc. (US) | Stores the repository the Wire is built from, including the published record | Names appearing in published material | US |
There is no email provider, no analytics provider, no newsletter platform and no payment processor, because there is no email we send, nothing we measure, no newsletter and nothing to pay for.
5.1 The model provider, stated plainly
Parts of the Wire's text are drafted and checked by a large language model. The provider is DeepSeek, called over HTTPS at api.deepseek.com.
Nothing about you is ever sent to it. Not your email, not your correspondence, not a server log. There is no reader account to send, and if there were, it would not go. That is a line we do not intend to cross, and if it ever changes this section changes first.
What is sent is published material. Headlines and extracts from articles other publications have already put out, and structured facts about organisations from our register. Where a person is named in it, they are named because a publication named them, in their professional capacity — a chief executive announcing a project, a minister launching a scheme, an analyst whose research is being cited. It is the same material a reader sees on the Wire with the link back to where it came from.
Where it goes, and under what law. DeepSeek's Open Platform terms are governed by the law of the People's Republic of China, with disputes heard where Hangzhou DeepSeek Artificial Intelligence Co., Ltd. is registered. DeepSeek's privacy policy states that it "directly collect[s], process[es] and store[s] your Personal Data in People's Republic of China". The PRC has no UK adequacy decision, so this is a restricted transfer and we treat it as one.
What their terms do not say. Neither the Open Platform terms nor the privacy policy states a retention period for API inputs and outputs, or whether they may be used for training. The privacy policy does say personal data is used "to train and improve our technology" with a right to opt out — but it expressly excludes developer API processing from its scope: "The processing rules for Personal Data collected from end users when accessing downstream systems or applications developed by developers using our open platform services are not covered by this privacy policy." So the consumer-facing answer does not apply to us, and the API-facing answer is not published.
We tell you this rather than assert a guarantee we do not have.
[CONFIRM: obtain DeepSeek's written position on API retention and training, and record the transfer mechanism — the IDTA or the UK Addendum — with a transfer risk assessment for the PRC.]
5.2 International transfers
Where a provider above is outside the UK, we rely on the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with a transfer risk assessment.
You may ask us for a copy of the mechanism relied on for any particular provider.
6. How long we keep things
| What | How long |
|---|---|
| Server logs | A short fixed period set by our hosting plan, never more than 30 days. We do not extend it or copy the logs elsewhere |
| Correspondence you send us | Up to 24 months after the matter is closed, then deleted |
| Corrections and complaints, and what we did about them | 6 years, because the point of a correction is that the record of it survives |
| Published material, including the register and the archive | Indefinitely. A wire whose archive could be quietly edited would not be worth reading — see clause 6.1 of the Terms |
7. Your rights
Under UK GDPR you may ask us to: give you a copy of your data; correct it; erase it; restrict or object to how we use it; and port it. You may object to processing based on legitimate interests at any time.
Where the journalism exemption applies — broadly, where complying would stop us publishing something in the public interest — some of these rights are limited. We will always tell you when we are relying on it, and why, rather than simply declining.
To exercise any of them, write to hello@axiom.vc. We answer within one month. There is no charge unless a request is manifestly unfounded or excessive.
Complaining. If we get it wrong, please tell us first — we would rather fix it. You can also complain to the Information Commissioner's Office (ico.org.uk, 0303 123 1113), or to the supervisory authority where you live if that is in the EEA.
8. Security, and being honest about its limits
How access and data are protected is set out in clause 6.6 of the Terms. In summary: the site is served over HTTPS with a content security policy; the relay is protected and its operator access is verified server-side; there are no reader credentials to lose because there are no reader accounts.
What we cannot promise. No system is perfectly secure. If a breach occurs that is likely to risk your rights and freedoms, we will tell the ICO within 72 hours of becoming aware and tell you without undue delay where the risk to you is high.
9. Changes to this policy
When this changes we update the version and the date at the top. Where a change materially affects you, we will say so on the Wire itself rather than relying on you to re-read this page. Previous versions are available on request.
*Questions about anything here: hello@axiom.vc.*