← Back to Articles

Protecting customer information without a legal department

Protecting customer information without a legal department

Names, emails, phone numbers, addresses, card details: what counts as personally identifiable information (PII), where small businesses actually leak it, and the short list of habits that prevent most of the trouble.

A customer fills in your contact form. Their name and phone number land in your email. You copy them into a spreadsheet to follow up. Someone helps you with bookings and gets the spreadsheet. A year later, the spreadsheet is in three inboxes, on a laptop you sold, and in a shared folder with a link that anyone can open.

Nobody did anything wrong on purpose. That is how most leaks of customer information start: no hacker, just a trail of copies nobody tracked.

This article is about the information your customers hand you, what the rules call it, and the habits that keep it safe. It is practical guidance from someone who builds websites, not legal advice. Where a law matters, I name it so you can look it up.

What PII is

PII stands for personally identifiable information: anything that can point to a specific person, alone or combined with other things.

Some of it is obvious: a full name, an email address, a phone number, a home address, a date of birth, a government ID number such as a Social Security number or a driver’s license number, a payment card number, a photo of someone’s face.

Some of it is less obvious but counts when it ties to a person: an IP address, a customer account number, a record of what someone bought, their location, the way they answered a health question on your intake form.

Two things follow. First, a list of first names alone is not much, but a list of first names with phone numbers is. Second, some categories are riskier than others. A leaked email address is an annoyance. A leaked Social Security number or card number can be used to commit fraud. Health details and ID scans can do lasting harm. Treat the dangerous kinds with more care, and, better, do not collect them at all.

Why a small business should care

There are three reasons, in the order I would weigh them.

Your customers trusted you with it. That is enough on its own.

A breach costs you customers. People forgive a late delivery. They rarely forgive “your information was exposed.”

There are rules, and they apply to small businesses too. In the US, every state has some form of data-breach notification law, which says that if certain kinds of personal information are exposed, you must tell the people affected, and sometimes a state agency. The details differ by state. If you serve people in the EU or UK, the GDPR or the UK’s version applies to you even if you are based elsewhere, and it covers what you collect, why, and how long you keep it. California’s privacy law has thresholds based on revenue and data volume, so many very small businesses fall below it, but you should check rather than assume. If you take card payments, the card brands’ security standard, PCI DSS, applies, and the easiest way to comply is not to touch card numbers at all (more on that below).

You do not need to become an expert in these. You need to know that they exist, and that the habits in this article are what they all ask for in different words.

The best protection is not having it

Every piece of information you collect is something you have to protect, forever. So the first question is not “how do I secure this?” but “do I need it?”

Go through each form on your site and each question on your intake sheet. For each field, ask what you do with it. If the honest answer is “nothing, it seemed normal to ask,” remove it.

A contact form needs a name, a way to reach the person and a message. It does not need a mailing address, a date of birth or a company size. A booking form needs a name, a time and a phone number or email. A newsletter signup needs an email address, and that is all.

Be especially hard on:

  • Social Security numbers, driver’s license numbers and passport numbers. Almost no small business needs these on a form. If a rule requires one (an employer collecting a tax form, a lender), collect it on paper or through a provider built for it, and never by email.
  • Date of birth, unless age is the point. Ask “are you over 18?” instead.
  • Card numbers in an email, a form or a text message. Never. Use a payment provider’s checkout.
  • Photos of IDs. If you must verify identity, look at it, note that you did, and do not keep the picture.

Let a payment company hold the card numbers

If you take payments online, use a provider such as Stripe, Square or PayPal, and use their hosted checkout or their embedded card form. The customer types the card number into the provider’s field, and it goes straight to the provider. It never touches your site or your email.

That one decision removes the most dangerous data from your business and shrinks your PCI paperwork to a short form. It is also cheaper than the alternative, which is building something secure yourself.

The same goes for taking a card number on the phone. Write it into your payment provider’s terminal or virtual-terminal page, not on a sticky note and not in a notes app.

Where small businesses really leak

Look for these, in rough order of how often I see them.

Email. Customers send things you did not ask for: a photo of a license, a card number “so you can charge me,” a medical note. Those sit in your inbox for years. Sent folders, forwarded copies and your phone’s mail app hold more copies.

Spreadsheets. A customer list in a spreadsheet gets copied, emailed, downloaded to a laptop and shared with a link that says “anyone with the link can view.” Check that setting now. It is often the first thing a stranger finds.

Shared logins. One password used by three people and a former employee. When someone leaves, nobody changes it.

Old devices and papers. A laptop sold without wiping it. An intake binder in a closet. A phone with the bookings app still signed in.

Website plugins and forms. A form plugin stores every submission in your site’s database, indefinitely, on a site that might not be updated. A contact form is a database of PII, even if you think of it as a way to get messages.

Third-party tools. Every tool you connect (scheduling, email marketing, a chat widget) receives some of your customers’ details. Each one is a place they live.

Backups. A backup of your site or computer contains everything. It needs the same care as the original.

Habits that prevent most of it

These are not exotic. They are the things a careful person does.

Keep a list of where customer information lives. One page: every place, who has access, how long you keep it. For a small business this takes ten minutes and is the most useful document you will write. You cannot protect what you cannot find.

Collect once, in one place. Pick the home for customer records (a booking tool, a customer-management tool, one spreadsheet with proper access) and keep it there. Do not copy it into emails and chats. Link to it instead.

Use two-step sign-in on email, your website, your payment provider, your booking tool, and anything else that holds customer data. A stolen password then does not get the thief in. An authenticator app is stronger than text messages, and either is far better than nothing.

Give each person their own login and the least access they need. The person who answers the phone does not need your payment settings. When someone leaves, remove them the same day.

Keep things updated. Your website software, its plugins, your computer, your phone. Many breaches use a flaw that was fixed months earlier.

Use encrypted connections. Your site should load at https, not http. Most hosts handle this for free now. Check the padlock.

Delete what you do not need. If you stopped working with a customer years ago and have no legal reason to keep their record, remove it. A database of old customers cannot leak what it does not have. Tax and legal rules require you to keep some records for a set time, so check that before deleting anything financial.

Have a short answer ready for “what do you do with my information?” If you can say it in two sentences, you are in good shape.

Your privacy policy has to be true

If you collect information on your site, you will need a privacy policy, and in some places the law requires one. A generator can give you a start. What matters is that the policy describes what you really do. A policy that says “we never share your data” while your site runs three trackers and a marketing tool is worse than no policy, because it is a promise you have already broken.

Say what you collect, why, who else gets it (your payment provider, your email tool, your analytics), how long you keep it, and how someone can ask you to delete it. In plain words. Then read it again whenever you add a tool.

If something goes wrong

Have the first steps in your head before you need them.

  1. Contain it. Change the passwords and sign-ins involved, remove the access that was misused, and take down an exposed file or link.
  2. Find out what was exposed, for whom, and since when. Your list of where information lives helps here.
  3. Tell the people affected, and a regulator or your payment provider if the rules say so. Do it quickly and plainly: what happened, what was exposed, what you have done, and what they should do. Do not hide it. People take a prompt, honest message far better than one that comes out later through someone else.
  4. Ask for help. A lawyer who knows privacy law, your insurer if you have a cyber policy, and your payment provider if cards were involved.
  5. Fix the cause, and write down what you changed.

Ten minutes: find where your customer information is

Do this today.

  1. Open a blank page and write down every place a customer’s name, phone number or email could be: your inbox, your phone, your website’s form submissions, your booking tool, your email marketing tool, spreadsheets, a paper binder.
  2. Search your email for “social security,” “SSN,” “date of birth” and “card number.” If you find messages with real numbers in them, delete them and tell the customers not to send those by email.
  3. Open the sharing settings on your customer spreadsheet. If “anyone with the link” is on, switch it to named people only.
  4. Turn on two-step sign-in for your email.
  5. Look at your website’s contact form. Remove every field you do not use.

Do the fifth step if you do nothing else. It costs nothing and cuts the amount you hold for good.

What to remember

You do not have to be perfect. You have to be careful about the few things that matter: collect less, keep it in few places, let a payment company hold the card numbers, protect your logins, delete what you no longer need, and write a privacy policy that tells the truth.

A small business that does those six things is already safer than many large ones.

Review the site I haveStart a site