Marketing & Sales
Customer & Member Data Handling: Collect, Use, Store, Delete, and Check Outside Tools
Intermediate | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
This template helps marketing and sales teams set rules for customer lists, member data, and trade show business cards across four stages: collect, use, store, and delete. Start by copying the field names and record counts from the mailing tool admin screen. Common pitfalls (mailing contacts without stating the purpose, spreadsheets passed around by email, contacts left on an ex-staffer's personal phone, old lists never deleted) each come with what happens, how to check, and how to prevent it. For outside tools, check that you pass only the fields needed, ask the vendor where data is stored and when it is deleted after cancelling, and remove people who left from the user list. Legal duties for personal data differ by country and region, so confirm the details with a specialist or a public office. The board has 4 pages: data inventory, four-stage rules, risk triage, and owners with a six-month review. The task board has 4 columns and 4 parent tasks with 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Customer and Member Data Handling Board
How to use (4 pages): ① Write the purpose and list the data you collect (frames①–⑤) → ② Write rules for the four stages and check outside tools (frames⑥–⑩) → ③ Check the pitfalls and set retention periods (frames⑪–⑮) → ④ Set owners and check dates, then review every six months (frames⑯–⑱)
1/4 List the data you collect
① Purpose of these rules (start here)
- Purpose e.g. Use information customers give us only within the purpose we told them, keep it safe, and delete it when it is no longer needed
- Lists in scope e.g. Mailing subscribers, member registration data, and trade show business cards held by Sales and Marketing
- Timeline e.g. Draft the rules in one month, then review them every six months
② List of data we collect (situation, purpose, storage place)
| When we collect | Fields collected | Purpose of use | Where it is kept | |
|---|---|---|---|---|
| Mailing sign-up | e.g. Sign-up form on the website | e.g. Email address, name, sign-up date | e.g. Announcing new features | e.g. Mailing tool |
| Member registration | e.g. Member registration screen | e.g. Name, address, purchase history | e.g. Providing the member service | e.g. Member admin screen |
| Trade show cards | e.g. Trade show reception | e.g. Company, name, phone number | e.g. Follow-up later (unclear whether this was stated at reception) | e.g. Staff desks and spreadsheet files |
| Inquiries | e.g. Inquiry form | e.g. Name, email address, message | e.g. Replying to the inquiry | e.g. Shared team inbox |
③ Mailing data (what we do not yet know)
- e.g. Where the list of people who stopped mailings is kept
- e.g. Whether the notice shown at sign-up still exists
- Write one unknown at a time
④ Member data (what we do not yet know)
- e.g. How long data of members who left stays
- e.g. How many people can see the admin screen
- Write one unknown at a time
⑤ Business card data (what we do not yet know)
- e.g. Which desks hold the stacks of cards we received
- e.g. How many spreadsheet files hold typed-in cards
- Write one unknown at a time
2/4 Map the four stages
⑥ Data lifecycle (the four stages the data in ② passes through)
- Collect e.g. Receive a card at the trade show reception, take sign-ups on a form
- Use e.g. Send announcements, get in touch about a deal
- Store e.g. Keep everything in one place in the CRM tool
- Delete e.g. Delete after the set period and keep a record of the deletion
⑦ Rules per stage (one row for each of the four stages in ⑥)
| Rule | What good looks like | How to check | |
|---|---|---|---|
| Collect | e.g. Tell people the purpose first, at the reception or on screen | e.g. The notice has one line on how data is used | e.g. Read the sign-up form and the reception sign |
| Use | e.g. Use data only within the purpose we told them | e.g. Never mail people who stopped mailings | e.g. Check the stop list in the mailing tool |
| Store | e.g. One place only, few people can see it, log any take-out | e.g. Never attach list files to email | e.g. Check the permission list of the shared folder |
| Delete | e.g. Delete once the guideline in ⑮ has passed | e.g. Shred paper and keep a record when deleting data | e.g. Check the dates in the deletion record |
⑧ Before handing over to outside tools (limit the fields)
- e.g. Pass only email address and name to the mailing tool, not the phone number
- e.g. Compare the fields you pass with the rules in ⑦
- Write in the register who passed what, and when
⑨ Check the vendor rules
- e.g. Check the vendor documents for the country or region where data is kept
- e.g. Check whether the vendor hands the work to another company
- e.g. Ask the vendor when the data is deleted after you cancel
⑩ Who can use it and when you stop
- e.g. Check the admin user list and remove people who left or moved teams
- e.g. If the tool supports it, log in with an authenticator app or a passkey. SMS codes beat nothing but are weaker (check the available methods in the tool guide)
- e.g. When you stop using a tool, keep a record of the export and the deletion
3/4 Narrow down the risks
⑪ Pitfall: collecting without stating the purpose (compare with ⑦)
- What happens | e.g. Mailing starts with no warning to people who gave a card, and complaints and opt-outs rise
- How to check | e.g. Read whether the sign-up form and the trade show notice say how data is used
- How to prevent | e.g. Add one line on how data is used to the reception notice, and ask separately from the card whether you may send announcements (a checkbox, for example)
- Rules on wording differ by country, so confirm with a specialist or a public office
⑫ Pitfall: spreadsheets circulate by email
- What happens | e.g. Nobody knows which is the latest, and mail goes to people who stopped mailings
- How to check | e.g. Search sent mail for "list" and count the attachments
- How to prevent | e.g. Pick one place, and write only the place name in email instead of the file
- e.g. A month after choosing the place, run the same search and count whether attachments dropped
⑬ Pitfall: contacts remain on the personal phone of someone who left
- What happens | e.g. Even after leaving, that person can reach customers and the company cannot stop it
- How to check | e.g. See whether the exit checklist has a line for customer contacts on personal devices
- How to prevent | e.g. Keep contacts in the CRM tool and tell new hires the rule not to save them on personal phones
- e.g. On the last day, check together with the person that they were deleted, and record it
⑭ Sort the pitfalls of ⑪–⑬ by impact and likelihood
Vertical axis: Impact (bigger ↑) / Horizontal axis: Likelihood (more likely →)
- Be prepared e.g. Contacts left on a personal phone (⑬). It happens only when people leave, but once out it cannot be taken back
- Act now e.g. List files circulating by email (⑫). It happens almost weekly, and a wrong address sends it outside
- Keep watching e.g. The wording of an old notice is unclear. Fix it together at the next review
- Reduce by procedure e.g. Collecting cards at a trade show without stating the purpose (⑪). It happens every time, so settle the reception notice wording in advance
⑮ Retention guideline (pitfall: never deleting lists you no longer use)
- What happens e.g. The sign-up list of a finished campaign stays in the shared folder with nobody using it
- Internal guideline e.g. Review two years after the last contact. Dispose of the paper card three months after typing it in
- How to check and prevent e.g. Every six months, look at when each list in the shared folder was last opened. For periods set by law, confirm with a specialist or a public office
4/4 Assign owners and roll out
⑯ Each team takes the lists in ② and the 'Act now' items of ⑭
| Lists and fixes it owns | Owner | Check date | |
|---|---|---|---|
| Sales | e.g. Trade show cards and deal contacts. Move the list files of ⑫ to one place | e.g. One list keeper in Sales | e.g. Monday of the 1st week each month |
| Marketing | e.g. Mailing subscribers | e.g. The mailing owner | e.g. Tuesday of the 2nd week each month |
| Member desk | e.g. Member registration data | e.g. The desk leader | e.g. Wednesday of the 3rd week each month |
| IT | e.g. User lists of each tool | e.g. The tool admin | e.g. The business day after someone leaves |
⑰ Six-month review flow
- Fix the list Bring the table in ② up to date e.g. Add a row for the seminar sign-ups you started
- Check the tools Check ⑧–⑩ once more e.g. Remove the two people who moved teams from the user list
- Delete Delete lists past the guideline in ⑮ e.g. Delete last year's trade show card table and keep a record
- Pass it on Tell the teams about the changed rules e.g. Take five minutes in the team meeting and explain only what changed
⑱ Whom to ask when in doubt
- Internal contact e.g. Legal or general affairs. Ask them to read the first version
- Outside specialist or public office e.g. A lawyer or similar. Legal duties differ by country, so check the latest guidance
- Tool vendor desk e.g. The support desk of the mailing tool. Ask where data is stored and when it is deleted after cancelling
Task board contents
Not started 16 items
List collected data
On page 1, write the purpose of the rules and turn the customer data your team collects into a table of situation, purpose, and storage place. Once you can see everything you hold, build the stage rules on page 2. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Copy tool fields
Open the admin screen of your mailing tool, look at the field names of the subscriber list (e.g. email address, name, sign-up date) and the record count, and copy them into the "Mailing sign-up" row of frame ② under fields collected and where it is kept (add the count to the place). Copy only the count and field names, never the personal data itself.
Set purpose, scope
In frame ①, write the purpose of the rules, the lists in scope, and the period for the first version. Done when all three notes are filled.
List unknowns
Fill the remaining rows of frame ②, then write in frames ③–⑤ what you do not yet know about mailing, member, and business card data. Done when each frame has at least one item.
Draw four stages
On page 2, draw how the data in frame ② passes through collect, use, store, and delete, then write the rule for each stage and the checks for handing data to outside tools. What you decide here becomes the yardstick for the review on page 3.
Add stage examples
In the four steps of frame ⑥, write one concrete situation from your own team for each. Done when all four steps describe your team.
Fill rules table
In the table of frame ⑦, write the rule, what good looks like, and how to check for each stage. Done when each check can be seen in a register or a settings screen.
Check outside tools
Following frames ⑧–⑩, check the fields you pass to the mailing and CRM tools, the vendor rules, and the user list. Note anything left to ask the vendor on a sticky note.
Narrow the risks
On page 3, check the pitfalls that are likely to happen, sort them by impact and likelihood, and pick the ones to act on first. Also decide here when lists should be deleted.
Check each pitfall
For each of the three pitfalls in frames ⑪–⑬, rewrite what happens, how to check, and how to prevent it for your team. Done when you have run the check once and written down the result.
Rank the pitfalls
Place the pitfalls of ⑪–⑬ in the four zones of frame ⑭, and assign the ones in "Act now" to owners on page 4.
Set retention rules
In frame ⑮, write your internal guideline for when to review and delete mailing, member, and business card data. For periods set by law, confirm with a specialist or a public office.
Roll out the rules
On page 4, set owners and check dates for each team, then write the six-month review flow and whom to ask. Once the rules reach the teams, track them in the "Rolled out and running" column.
Assign team owners
In the table of frame ⑯, write for each team the lists it looks after, the fixes from "Act now" in ⑭, the owner, and the check date. Done when every team row is filled.
Set up review cycle
Decide the order of the review with the four steps of frame ⑰, and put it on the calendar for the week six months from now.
Write who to ask
In frame ⑱, write the internal contact, the outside specialist or public office, and the tool vendor desk. Done when you know whom to ask when in doubt.