Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Disable frequently used
I don't want any usage-related metadata stored with my 1Password items, including recency and frequency. I see it as a security risk. Is there any way to disable this?
The risk I see is that a bad actor can infer usage patterns and other information from how often or how recently something is accessed. I get that it's useful for most people, but disabling the collection of metadata like that should be an option IMO.
1P_Timothy
Community Manager
Community ManagerThanks for the additional details jamesn. Just to fill in the picture a bit more, are you picturing this in a "shoulder surfing" type of scenario where someone could hypothetically glean information without having direct access, or something else?
Yeah I think there's many different scenarios where it could matter.
- Someone glances over your shoulder and sees a list of your most used websites
- Someone briefly has access to your device and sorts by frequency to get a list of your most used websites
- You do something and your partner takes an opportunity to see what site you recently accessed by sorting by recent
- Border searches or law enforcement scenarios
I don't think any of these are likely to occur, but given I NEVER use recency/frequency, and only use search to find my items, why do I want that data being gathered? Just give me an option to turn it off at the account level
- 1P_Timothy
Thanks for sharing those examples jamesn, that's really helpful. As you alluded to, it can be difficult to plan for or anticipate every scenario, but I can definitely see the benefit in this option from what you described.
I can't promise an option to hide or disable use frequency will be added to 1Password, but I've shared the request along with your comments with the team. Thanks again!
2F47549404Seconding the original user's list. Given scenarios where we are required to grant access to untrusted actors and in cases of breach, this data presents a risk.
I would go further and request the ability to erase the usage history in app. The times when that data is useful are numerically inferior to time in which that data is harmful. Between matching autofill and search, the features are moot.
