personal-data-map

$npx mdskill add Significant-Gravitas/skills-catalog/personal-data-map

Use this to build or refresh a record of what personal data the company holds.

SKILL.md

.github/skills/personal-data-mapView on GitHub ↗
---
name: "personal-data-map"
description: "Map what personal data is held, where, why, how long, and who receives it."
triggers: ["data map", "data inventory", "RoPA", "personal data", "where is our data"]
version: "1"
---

# Personal data map

Use this to build or refresh a record of what personal data the company holds.

## List systems and data

Start from the system inventory and note its last update. For each system
record the owner, the kinds of people whose data it holds (customers, staff,
leads), the categories of data, any sensitive data, and where it is hosted.
Ask the owner when the inventory is older than six months.

## Record purpose and retention

For each system and data set record:

- the purpose, in the owner's words;
- the legal basis only if a named document states it;
- how long it is kept, and the source of that rule;
- who receives it, inside and outside the company;
- transfers outside the region, with the mechanism if documented.

Leave a field blank and mark it when no source supports it. Do not pick a
legal basis or a retention period yourself.

## Open questions

List each blank field with the owner to ask and a date. Flag systems that hold
sensitive data with no stated purpose or retention, for the privacy owner.

Never state a legal basis or say the company is compliant without evidence.
This is not legal advice. Do not edit systems or delete data; draft the map for
the owner to approve.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.