Holding your buyers' addresses responsibly, without becoming a lawyer
Every physical order leaves you holding somebody's home address. A few plain rules about where it lives, who sees it and when it goes.

You sold eleven tote bags at a market and forty more online, and somewhere in that pleasant fortnight you became the custodian of fifty-one people's home addresses. They are on your laptop, in a spreadsheet, in your downloads folder, and probably in a screenshot you sent to a friend to show off the order. None of that was malicious and all of it is normal. It is also the moment a small creative business quietly acquires a duty it never signed up for, and the duty does not go away because the business is small.
What makes this awkward for one-person shops
Data protection rules were written with organisations in mind, and they land on a person selling candles from a spare room with exactly the same wording. There is no small-shop exemption that switches everything off. At the same time, nobody expects a solo maker to appoint a data protection officer. The honest position sits in between: apply the principles, keep the paperwork proportionate, and do not pretend the obligation is somebody else's.
The genuinely difficult bit is not the storefront. It is everything downstream of it. The address is safe enough inside your account; it becomes fragile the moment it is copied into a spreadsheet on a shared laptop, pasted into a group chat with a packing volunteer, or exported to a CSV that sits in Downloads for three years next to your tax returns. Almost every small-business data incident is a copy, not a breach.
The second difficulty is deletion. People do occasionally ask you to remove their details, and if your data lives in nine places you cannot honestly tell them you have. Keeping fewer copies is not tidiness for its own sake — it is what makes an honest answer possible.
Where the address actually lives
The customer list assembles itself as you sell: every buyer, every member, everyone who took a free download, with lifetime value per person and a full CSV export on every plan. Contrast that with the arrangement most people fall into by accident.
| The usual arrangement | With store.fan |
|---|---|
| Addresses scattered across DMs, emails and three spreadsheets | One customer list built automatically from purchases, memberships and free downloads |
| No idea who a person is beyond the current order | Every order and lifetime value attached to the same person, so context does not require a search |
| Existing contacts stranded on an old platform | Import from any CSV, so previous buyers live alongside the new ones |
| Export locked behind an upgrade, so people screenshot instead | Full CSV export on every plan including Free, so there is no reason to improvise |
| Payment and address data mixed together in your own files | Card details are handled by Stripe and never sit with you; payments go straight into your own Stripe account |
Six rules that cover most of it
None of these require software or a policy document. They require a decision made once, written somewhere you will see it, and applied when you are busy — which is the only time it matters.
- 1Collect only what the parcel needs. If an order-form question does not change what you pack or how it reaches them, do not ask it.
- 2Treat the customer list as the original and everything else as a copy. Work from it directly rather than from a spreadsheet whenever you can.
- 3Give every export a job and an end date. Export for a packing session, use it, delete it that week — do not keep a rolling master file in Downloads.
- 4Never paste an address into a group chat. If a helper needs to pack orders, hand them one printed sheet and take it back afterwards.
- 5Set a retention rule you can state in a sentence, such as deleting address data from your own copies once the return window and tax record period have passed.
- 6Say in your product description or shop page what you collect, why, and how long you keep it. Two sentences, in plain words, does more for trust than a page of boilerplate.
What a tidy version looks like in practice
A maker with roughly 300 orders a year runs it like this. Physical orders collect a name, an address and a phone number, and nothing else. Every Sunday she exports a CSV of the week's unfulfilled orders, packs from it, and deletes the file when the last parcel is sealed. Her partner helps with the December rush from a printed list that goes in the recycling on the second of January.
Once a year, in the same session where she does her accounts, she reviews what she is still holding and removes what has aged past her stated retention period. When somebody emails asking to be removed, she can answer honestly in one reply, because there are only two places to look. None of this took a system. It took deciding, in advance, that the customer list is the one true copy and that a CSV is a temporary tool rather than a filing cabinet.
Keep every buyer in one list instead of five spreadsheets, from your first sale.
Start free todayThe mistake most people make
They keep everything, forever, in case it becomes useful. It is an understandable instinct — a list feels like an asset, and deleting anything feels like throwing away growth. But an address from a one-off order four years ago is not marketing value, it is somebody's home stored on a laptop that has since been to three airports. The part of the list that is genuinely valuable is the email, the purchase history and the lifetime value, all of which you keep. Addresses are operational data with a short useful life. Treat them like the packing tape rather than the accounts.
They are collected at checkout for your physical orders and stored with the order and the customer record so you can post the parcel. store.fan never handles the parcel itself and generates no carrier labels or tracking, so the address exists for your fulfilment, not for anyone else's.
With Stripe. Payments go directly into your own Stripe account and store.fan never holds funds, which also means card numbers are never in your customer list or your CSV export. That is one whole category of risk you simply do not carry.
Find them in your customer list, remove what you are able to remove, then hunt down your copies — exports, spreadsheets, chat threads — and delete those too. Note that records tied to a completed sale may need to be retained for tax purposes for a period; be honest about that rather than promising a clean wipe you cannot deliver.
No. Export is genuinely useful, and it is on every plan including Free for a reason: your list should never be trapped anywhere, including here. The rule is not to avoid exporting but to give every export a purpose and a deletion date.
Handling addresses well is mostly a matter of resisting copies. Keep one list, take from it what you need for the job in front of you, and put it back. The people who bought from you gave you their front door because they wanted the thing you made, and treating that as a small trust rather than a database is both the decent position and the easy one. If you are moving from somewhere else, the migration guide covers bringing existing contacts across, and the pricing page confirms what is included at each level.
Build a customer list that assembles itself, with the export always yours to take.
Open a free accountTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



