Privacy Guides
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.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- 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.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
Small nuance:
"Later this summer, you’ll see the option to participate in our telemetry system and help improve 1Password. You don’t need to take any action right now, and we won’t collect any usage data without your awareness and consent first. Participation will be optional for Individual and Family plan customers. And at this time, our telemetry system won’t be rolled out to any team or business using 1Password."
Aka, it's an opt-in that you can simply not opt-in to and if you don't nothing changes and then it won't be used on you.
For now. This is step one of enshittification. Step 2 is enabling it for new accounts by default. Step 3 is removing the ability for new accounts to turn it off. Step 4 is defaulting it on for legacy users, and step 5 makes it mandatory for everyone that isn't paying for something.
As such, we're better off just opting out of using 1Password.
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.
Because if I'm a CEO I can't confirm that my other employees won't opt in. Is the opt-in at an admin only level? Then you haven't gained consent of the individual. So it's a bit more complicated to roll out functionality to these classes of customers.
Maybe they just straight up don't care about data from those users?
Also the decision to exempt business and teams makes no business sense. Companies derive the lion’s share of their revenue from enterprise. If a company wants to optimize their product offering, you’d do so with your most desireable, profitable segment in mind. This just seems like a backwards decision.
I think more probably, they’re dogfooding it on the consumer segment and then after they’ve worked out the “oops, we shouldn’t have collected that bit of data” errors, they’ll move to include enterprise. But I’d guess that consumers are the guinea pigs here.