You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2026-06-15-pii-examples.md
+31-33Lines changed: 31 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Some information may become identifying when combined with other data:
51
51
52
52
Different privacy laws and internal policies may define personal data differently, so treat the examples in this article as a practical analytics hygiene guide rather than legal advice. When in doubt, collect less.
53
53
54
-
## PII vs personal data
54
+
###PII vs personal data
55
55
56
56
PII and personal data overlap a lot, which is why they often sound like the same thing. The difference is mostly about where the terms come from and how broadly they are used.
57
57
@@ -61,7 +61,36 @@ Personal data is the term used by GDPR. The [European Commission explains person
61
61
62
62
For example, `jane@example.com` is obviously both PII and personal data. A random-looking customer ID may not look personal on its own, but if your systems can connect it to one customer, it should be treated as personal data for analytics purposes too.
63
63
64
-
For website analytics, the practical rule is the same: if a value can identify, single out or be linked back to a person, do not send it to analytics.
64
+
### Sensitive PII and special category data
65
+
66
+
Some personal information needs extra care because misuse can create higher risk for the person involved.
67
+
68
+
In US-style PII language, this is often discussed as sensitive PII: information such as:
69
+
70
+
* government ID numbers
71
+
* financial account details
72
+
* medical records
73
+
* biometric data
74
+
* passwords
75
+
* other details that could lead to harm if exposed
76
+
77
+
Under GDPR and UK GDPR, some types of personal data are treated as special category data. The [ICO lists these categories](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/special-category-data/what-is-special-category-data/) as data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used for identification, health data, sex life and sexual orientation.
78
+
79
+
For analytics, the guidance is simple: do not send this type of data. For example, track:
80
+
81
+
```text
82
+
Appointment request submitted
83
+
Resource downloaded
84
+
Application form submitted
85
+
```
86
+
87
+
Do not track:
88
+
89
+
```text
90
+
Therapy appointment requested by Jane Smith
91
+
Diabetes guide downloaded by user_184291
92
+
Disability accommodation request from jane@example.com
93
+
```
65
94
66
95
## Common PII examples
67
96
@@ -223,37 +252,6 @@ If you track internal site search, avoid sending raw search terms when your user
223
252
224
253
For public content sites, tracking popular search terms can be useful. For logged-in tools, CRMs, support systems, health portals, finance apps or admin dashboards, it is safer to track only that a search happened, or to categorize searches without storing the exact query.
225
254
226
-
## Sensitive PII and special category data
227
-
228
-
Some personal information needs extra care because misuse can create higher risk for the person involved.
229
-
230
-
In US-style PII language, this is often discussed as sensitive PII: information such as:
231
-
232
-
* government ID numbers
233
-
* financial account details
234
-
* medical records
235
-
* biometric data
236
-
* passwords
237
-
* other details that could lead to harm if exposed
238
-
239
-
Under GDPR and UK GDPR, some types of personal data are treated as special category data. The [ICO lists these categories](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/special-category-data/what-is-special-category-data/) as data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used for identification, health data, sex life and sexual orientation.
240
-
241
-
For analytics, the guidance is simple: do not send this type of data. For example, track:
242
-
243
-
```text
244
-
Appointment request submitted
245
-
Resource downloaded
246
-
Application form submitted
247
-
```
248
-
249
-
Do not track:
250
-
251
-
```text
252
-
Therapy appointment requested by Jane Smith
253
-
Diabetes guide downloaded by user_184291
254
-
Disability accommodation request from jane@example.com
255
-
```
256
-
257
255
## What not to send to analytics
258
256
259
257
As a rule, do not send anything to analytics that identifies a person, account, household, transaction or private case.
0 commit comments