One file, one button, and a format somebody else can read.
Data portability is a right rather than a courtesy, and most implementations of it are a hostile PDF. This one is a zip containing structured data, the photographs, and a plain-English index explaining what every file in it is.
What is in the file.
| File | Contains | Format |
|---|---|---|
| index.html | A readable summary of everything else, with links | A web page that opens offline |
| account.json | Name, email, addresses, parish, preferences, settings | Structured, documented |
| orders.csv | Every order, every line, every price, every date | Opens in a spreadsheet |
| bushels.csv | Every earn and every burn, with running balance | Opens in a spreadsheet |
| holdings.json | Patches, casks, boxes, fosters, with their full records | Structured |
| photographs/ | Every monthly patch photograph, at full resolution | JPEG, dated filenames |
| provenance/ | The batch record behind everything you were sent | One HTML page per batch |
| consents.csv | Every consent given or withdrawn, with a timestamp | Opens in a spreadsheet |
| README.txt | What each of the above is, in plain English | Text |
How to get it.
Ask, in Faffing
One button. No form, no reason required, no retention conversation.
We confirm it is you
A link to the email address on the account. That is the only check.
It gets built
Usually within an hour. The law allows a month; an hour is what the machine actually takes.
You get a link
Valid for seven days, then it expires and the file is destroyed.
Ask again whenever
No limit, no cooling-off period, and no charge. Some people take a copy every January.
Why the photographs are in it.
The strictly legal reading of portability covers data you provided and data generated by your use of a service. Whether a photograph we took of a field you have a forward purchase on falls inside that is arguable.
We are not going to argue it. Twelve photographs from the same fence post across a season are the single thing people most want to keep, they are worthless to anybody else, and refusing to include them because a definition is ambiguous would be a genuinely petty way to behave.
The same reasoning puts the provenance pages in the file. They are ours rather than yours, and having a permanent offline copy of where your flour came from is obviously the right outcome.
In the file, and not in it.
Included
- Everything on Your Data, in full
- Every patch photograph at full resolution
- The provenance record behind every delivery
- A readable index that opens without a developer
- Consent history with timestamps
- As many copies as you want, free
Not included
- Anything about anybody else
- Internal notes about you, which do not exist
- Our own commercial data attached to your orders
- A tracked-changes history of your address book
- Anything from a system we do not control
This build produces no export, because it holds nothing.
Every control on this page is a placeholder. There is no account system here, no orders, no bushels and nothing to package up. The description above is of how a live version would behave.
Exporting, questioned.
No. A charge for a subject access request is only lawful in narrow circumstances and using them would be an unpleasant way to treat somebody exercising a right.
Usually under an hour. The statutory month is a ceiling, not a target, and a company that uses the whole month is telling you something about itself.
CSV and JSON are what there is. Both are readable by anything, which is the point of choosing them.
No. They are entirely separate buttons, deliberately far apart on the screen.
Or remove the lot.
Two taps, thirty days to change your mind, and then genuinely gone.
