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:
Learn more…
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:
- 1 user online
- 1 user / day
- 1 user / week
- 76 users / month
- 696 users / 6 months
- 1 subscriber
- 663 Posts
- 11.1K Comments
- Modlog
https://cloudzy.com/anonymous-vps/
This site for example advertises itself as privacy friendly. Is there any reason not to trust it?
And I am not talking about illegal stuff just want to make sure they dont snoop into what services I am selfhosting without reason
What are you wanting to host? There are some ways to limit what they have access to, or increase the amount of work to access it, but it’s pretty dependent on the actual services.
The main thing I would like to host is a VPN. I pay for mullvad but a lot of their ips are blacklisted. Which is why I’d like a cheap vps to selfhost openvpn to circumvent censorships on some free wifi networks that I use, while also keeping my data private.
In that case, you’d be connecting to the vps without a VPN. So the company would have your ip, and anonymous payment won’t do anything about that. It would help your blacklisting problem, and your WiFi censorship problem though. Just stick with a reputable company. I use hetzner and dedipath and i’m happy with both of them.
Any VPS provider can access your data via the hypervisor if they want, there’s just no way to prevent it. It has nothing to do with what payment methods are accepted.
If you want to be sure, you need your own hardware on your own premises.
Then you move your privacy concerns to your ISP.
Not really. Your IPS cannot look at the contents of your server. Any VPS provider can look at the contents of your RAM, and in turn, break any encryption you use on the device.
But an ISP can get all that sweet meta-data from your packets - where they are going, and maybe from your DNS queries.