Privacy Notes for View Tracking
Overview
View tracking and notification tracking can contain sensitive information about user behavior, access patterns, IP addresses, and communication activity.
What this feature does
It helps administrators understand how to use tracking features responsibly.
Why it is useful
- It reduces privacy and compliance risk.
- It helps organizations create internal policies for audit data.
- It encourages limited access to sensitive tracking logs.
Who should read this?
System Owner, RISE Admin, Compliance Officer, Security Officer.
Where to find it
View Log, Notification Log, Auth Log, exports, reports, and privacy-related settings.
How to use it
- Limit access to View Log and Notification Log.
- Document how tracking data is used internally.
- Avoid exporting sensitive tracking data unless needed.
- Use retention settings to avoid keeping data longer than necessary.
- Follow your organization’s privacy and legal requirements.
Example workflow
A company allows only administrators and compliance staff to view record access logs because the logs reveal who accessed client or financial information.
Common mistakes
- Giving all staff access to tracking logs.
- Exporting view logs without protecting the file.
- Keeping sensitive tracking data forever without a retention policy.
Related articles
- Sensitive Data and Privacy Notes
- Data Retention Policy
- Permissions Overview
