Knowledgebase

Privacy Considerations in Product Analytics Print

  • 0

Understanding usage without over-collecting.

WHAT PRODUCT ANALYTICS COLLECT

Which features are used By whom How often In what sequence

WHY THAT IS PERSONAL DATA

It is linked to identifiable accounts.

WHAT TO ESTABLISH

What decisions the data will inform.

WHY

It determines what you actually need.

WHAT MOST DECISIONS NEED

Aggregate patterns, not individual histories.

WHAT TO PREFER

Aggregated measures Sampling Shorter retention

WHAT TO AVOID

Recording every action of every user indefinitely Session recordings capturing everything typed

WHY SESSION RECORDING DESERVES CAUTION

It captures form contents, including data you never intended to collect.

WHAT TO DO IF YOU USE IT

Exclude sensitive fields explicitly, and verify the exclusion works.

WHAT TO NEVER CAPTURE

Passwords Payment details Anything in a field marked sensitive

WHAT TO CHECK

What the recording actually contains.

HOW

Watch one, looking for what should have been excluded.

WHAT TO TELL USERS

That usage is measured, and why.

WHAT TO ASSESS

Whether an impact assessment is required for detailed monitoring.

WHAT TO SET

Retention, and enforce it.

WHAT TO REVIEW

Whether anyone uses the data collected.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot