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
I did this dance a while back and they all will use your data to some degree, so I opted to change the other side of the equation and maximized the utility as best I could and to do that I looked for a tracker that didn't require a subscription for features that are already in the watch.
I opted for a Garmin watch, (a refurbished Vivoactive4S, specifically), specifically for that reason and also for long battery life (My wife recharges her Apple watch daily but my watch lasts all week and newer models last even longer).
If you are privacy-minded, you can obviously set up your Google connect account with a burner email, but much of the workout tracking does utilize GPS. You may be able to turn that off but I haven't experimented there.
I’m personally of mixed opinions about Garmin.
On the one hand, I think they make the best products. Both their hardware and software as far as fitness tracking features is just brilliant. Not having any subscription is also an absolute must-have for me.
On the other hand, they operate their no-subscription business model by being extremely stingy with software updates. You might get one year of feature updates to your watch or bike computer, and maybe some critical security updates after that. But that’s about it. Apple has a mostly-undeserved reputation for planned obsolescence, but Garmin absolutely lives by that model. Sure, my Forerunner 935 isn’t going to suddenly be able to do digital payments without an NFC chip in there, but there’s no reason it shouldn’t be able to guesstimate my heat adaptation or do the same Body Battery calculations that the device from one year later is capable of using the same wrist heart rate monitor.
I’m also not sure I’d trust them on privacy too much. I trust them not to deliberately send your data to anyone malicious, or even use the data indirectly for non-customer-centric reasons. Their business model is much more like Apple than Google or Facebook in that respect. And that’s certainly a very good thing from a privacy standpoint. But I don’t think they’re a company that takes security very seriously. The rumour is that they probably had to pay the ransom when they were hit by ransomware a year or two ago, because they lacked the technical ability to restore from backups (though we don’t know for sure if that’s what happened). And with lax security comes an enhanced risk of your data being obtained by malicious actors.
How in the world do you figure Apple hasn't earned their reputation for planned obsolescence when they serialize every part in the device, don't allow for 3rd party repairs, constantly refuse to repair devices, constantly make them harder to repair, don't make absolutely any repair documentation available, sue the people who find said documentation and make it available, and send ICE to raid businesses who are able to actually get their hands on replacement parts?
Blinders are a powerful thing unfortunately.
Personally I wouldn't describe being against right to repair as the same thing as planned obsolescence. It's a bad behaviour, but a different category of bad.
Planned obsolescence is more things like failing to provide support (software updates—since hardware repairs or replacement type support are legally mandated in civilised countries, so that doesn't enter the equation) for the reasonable lifetime of the device—which in a smartphone is probably 3–5 years, or in the extreme case designing things to fail after a certain time.
The example a lot of people point to with Apple is the throttling that came out around 2017. But I don't agree that it's fair to characterise that as an example of planned obsolescence because in fact, it was something they did to extend the life of the device. Giving users the ability to make a fully informed choice for themselves would be much better, but taking action that they think will have a minimal impact on moment-to-moment UX while extending battery life could hardly be described as planned obsolescence.
And fwiw, I'm writing this from my Android phone. I'm not in the Apple ecosystem myself.
I would. And I do.
The fact is that is what apple says is the reason. Maybe they are trying to influence the user into buying new hardware by making the phone seem more sluggish.