We’ll soon be rolling out a privacy-preserving telemetry system to customer accounts. Learn how the rollout is going to work, and the steps we’ve taken to protect your privacy.
And at this time, our telemetry system won’t be rolled out to any team or business using 1Password.
Uhh, what? If it’s opt-in why does it matter if team or business doesn’t have this? Different standards? To go through such lengths to explain this telemetry stuff to convince people, “Oh, no worries, yo! It’s OPT-IN! Trust us!” feels very dirty to me.
Business software has very different requirements. It’s much harder to implement stuff for them without breaking those requirements. Think compliances like (ISO) norms and laws regarding commercial businesses, contracts, or even the software being made to work and be administrated on a whole different scale. You can’t compare really…
While I agree it could go worse from here into a downwards spiral of enshitification, all I meant was that the title is a bit misleading into the other direction; making it sound like they would force telemetry onto users. If they wouldn’t say shit about this option, no one would sign up, even if they wouldn’t mind it. And basically, they’re explaining how they tried to make it as anonymous as possible and that’s it’s opt-in, which would also be a way to go if you legitimatly want to get data for improvement only. If that’s truly what they want, time will tell.
The moment it stops being optional I’m looking for a different password manager right away, I switched more complex and important things for similar reasons. But since my experience with them has been good, I’ll give them the benefit of the doubt for now.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Says them, I guess. Feels kinda weird to me.
Uhh, what? If it’s opt-in why does it matter if team or business doesn’t have this? Different standards? To go through such lengths to explain this telemetry stuff to convince people, “Oh, no worries, yo! It’s OPT-IN! Trust us!” feels very dirty to me.
Business software has very different requirements. It’s much harder to implement stuff for them without breaking those requirements. Think compliances like (ISO) norms and laws regarding commercial businesses, contracts, or even the software being made to work and be administrated on a whole different scale. You can’t compare really…
While I agree it could go worse from here into a downwards spiral of enshitification, all I meant was that the title is a bit misleading into the other direction; making it sound like they would force telemetry onto users. If they wouldn’t say shit about this option, no one would sign up, even if they wouldn’t mind it. And basically, they’re explaining how they tried to make it as anonymous as possible and that’s it’s opt-in, which would also be a way to go if you legitimatly want to get data for improvement only. If that’s truly what they want, time will tell.
The moment it stops being optional I’m looking for a different password manager right away, I switched more complex and important things for similar reasons. But since my experience with them has been good, I’ll give them the benefit of the doubt for now.