For us it is the same problem.

Like already mentioned in the comments the function to restrict the access to analytics does not solve the data privacy problem.

We need to be able to anonymize the data so teams can just track if their page is being visited and used.

Unfortunatley we are loosing a full feature

I would like to have an "Anonymize" Setting which makes sure that no names are shown in any page analytics so that it is impossible to trace the work habits of individual persons.
Only the total numbers and graphs are shown. I don't even need to see anonymized names, I don't want to see any individual.
There is no exception for this setting for any user.

Business Reason: For a lot of enterprise companies in countries with strong workers councils, this is a legal requirement. It is illegal to track individual work and you could get in real troubles if you do so.

The only exception is for OrgAdmins as they could have a requirement of product liability to be able in the case of a lawsuit to proof access to data by an individual. But there I don't need page analytics either, because I would check in the Org Audit log.

To Restrict the view of the analytics doesn´t help. You can trace work habits of individual persons and that is simply not allowed for anyone, except for org admins. Without an anonymization mode the whole analytics feature is of no use for my company and that is a big issue.

This is an existing feature with Confluence Data Center,
https://confluence.atlassian.com/doc/administer-analytics-1044780575.html

The additional setting we need is hide the username that is displayed in the analytics data for the entire site.
This should be a setting for Site admins, same as on Datacenter.

mwang@atlassian.com , look at MS 365. There are analytics but you have no usernames inside. So, a mode which shows only numbers without personal data will be fine. Having e.g. the number of views is very useful! 

Thank you all for the feedback!

Today, Space Admins can turn off Analytics within Space Settings by navigating to (see screenshots):

1. Space Settings
2. Space Permissions
3. Analytics Permissions
4. Restricting View Analytics to specific users

At the Global Level, Product Admins can restrict View Analytics to specific User Groups under Analytics Permissions.

Questions to further clarify:

• What additional settings would you like to see?
• What is the expected behavior of this setting?
• Who should be able to anonymize View Analytics and at what granularity?

Thank you!
Morgan, Confluence Product Manager

++ for this one, we've had to restrict access to admins only due to privacy concerns. 

We use analytics a lot in our old on-prem site. Not having a security feature like this is pretty much a killer for this feature. Its disabled now and we would like to use it again, but without anonymisation its a no no right now.