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
Yes, that is a core aspect of how these "aliasing services" work.
You are able to simply hit the "reply" button, in which ever email provider the emails are routed to, and whatever you write will be delivered exactly like that to the person who sent you an email. From their perspective everything will look exactly as if they were talking to a regular email address.
This is a feature of both AnonAddy and SimpleLogin.
Regarding catch-all, that is basically also how I configured my usage of AnonAddy. Usually you would go and create a new alias, before you want to receive incoming mails on that address. All emails to aliases that are not already created will be dropped. But they also offer a, to me at least, superior version, where aliases are automatically created once the first email arrives on it.
This way you basically have a catch-all address, but with the benefits of being able to respond as all "identities", as well as toggle off individual ones if you start receiving spam. If you read below, avoiding spam is my ultimate goal with all of this. Your use-case may be different.
I have written a small add-on for Firefox, which will automatically generate a random
[email protected]for me, and create that alias in AnonAddy with the current URL as a note. But yesterday I was checking in to a hotel, and the reception asked for an email, so I just typed[email protected], which will clearly indicate to me that it was created for that hotel only. The downside to this is that it's easier to spot that it is indeed an alias address, but I'm also well aware of how spammers just buy active email-addresses in bulk, without caring about where the leaks come from, so I'm not too scared that it will stick out too much. You shouldn't do stuff like[email protected]or[email protected]though. That's gonna stick out like a sore thumb.Interesting, thanks!