Read-only by design
PocketPilot has no payment capability. It cannot send money, set up a transfer, or touch a balance. Not as a policy, but because the ability was never built.
Security and your data
Receipts are personal. We treat them that way.
A receipt says where you were, when, and what you bought. A statement says the same thing for a year. This page sets out how PocketPilot handles that, what it deliberately cannot do, and which parts are still work in progress.
No bank credentials
Transactions arrive by CSV import, so PocketPilot never asks for a banking login, never holds one, and cannot be used to reach your bank.
Scoped to your household
Every record belongs to a household, and access is enforced in the database itself against the signed-in person, not only in the application code above it.
Receipt images stay private
Original photographs live in private storage scoped to your household. They are not public, not indexed, and not served from a guessable address.
Export and deletion
You can take your data out in a standard format, and you can ask for it to be deleted. Both are rights, not favours, and neither is buried.
Nothing sold, nothing tracked
We do not sell customer data or use it for advertising. This marketing site sets no cookies and loads no analytics, which is why it never asks you to accept anything.
Who touches your data
A short list, on purpose
Running a service means using infrastructure. We keep that list as short as it can reasonably be, and everyone on it is contractually limited to processing data for us, and they cannot use it for their own purposes.
The waitlist you are looking at today uses two: a hosting provider and a database provider. Both are named in the waitlist privacy notice, along with what each one holds.
Receipt reading may involve a processing provider. Which one, and under what terms, is being decided now, and it will be documented before real receipts from beta households go through it.
This website, right now
Live
Advertising trackersNone
AnalyticsNone
Cookies setNone
Third-party fontsNone
Third-party scriptsNone
Data stored if you joinName, email, answers
This is checked automatically before every release. A build that reintroduces a remote asset fails rather than shipping.
Being straight with you
Still in progress
A security page that only lists strengths is marketing. These are the things that are not finished, stated plainly, because you are being asked to trust a product that is still being built.
UK hosting is planned, not done
Production data is intended to be hosted in the UK. That is the plan of record, and it is not yet the deployed state.
Rights requests go through email today
Export and deletion inside the product are built but not yet released. Until they are, email hello@mypocketpilot.io and a person will action it.
The beta is a beta
Software this young has bugs. Keep your own records during the beta rather than relying on PocketPilot as your only copy of anything that matters.
No independent audit yet
Nobody external has certified any of this. We are not going to imply otherwise with a badge, and we will say so here when that changes.
Your rights
What you can ask for, and from whom
PocketPilot is the trading name of Pocket Pilot LTD, company number NI742666, a company registered in Northern Ireland. That company is the data controller.
Under UK data protection law you can ask what we hold about you, ask for it to be corrected, ask for a copy, ask for it to be deleted, withdraw consent, or object to how it is used. Beta participants have those rights from the first day, and so does anyone on the waitlist.
The route for all of it is hello@mypocketpilot.io. If we get it wrong, you can complain to the Information Commissioner’s Office.
Found something we have got wrong?
Security reports are welcome and taken seriously. Email hello@mypocketpilot.io and you will get a reply from a person.