It’s a great option, but it’s debatable whether or not it’s privacy improving. On one hand it’s your domain. You don’t need to worry about moving email services, and as you control it, you can have as many addresses as you want. One for each service, catch all, and so on. On the other hand it’s YOUR domain. Only you have access to it. It’s quite easy to filter out the first part, before the @ sign, and identify exactly who you are. It’s a unique data point, tied to you. It’s arguably as bad as handing out a phone number.
myusername+token@gmail.com — easy to filter out the plus and everything after, and it’s very likely more people use this format than uniqueusername@my-own-domain.com, making more likely that this filtering would actually be automatically applied.
What about email relays? Kdhrbrk@mozmail.com doesn’t seem like it could be tied to me, then firefox relay forwards the email to my actual email address.
Yeah, email relays are probably better. I wasn’t necessarily considering those in my comment. But there are tradeoffs there too; now all your incoming mail can be read by a 3rd party, and there’s one more server between you and your email that needs to be up and working for you to properly receive mail.
This is very useful for identifying which services might have sold your email to third parties.
Another downside may be that once you’re using your domain for emails, you better make sure you don’t accidentally let it expire or mess up some configuration and start missing emails, which may be important, sent to you
The bit about moving email services can help privacy indirectly at least… If a provider no longer meets your privacy needs you can move to another that does.
That’s much harder when you don’t have your own personal domain
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.
It’s a great option, but it’s debatable whether or not it’s privacy improving. On one hand it’s your domain. You don’t need to worry about moving email services, and as you control it, you can have as many addresses as you want. One for each service, catch all, and so on. On the other hand it’s YOUR domain. Only you have access to it. It’s quite easy to filter out the first part, before the @ sign, and identify exactly who you are. It’s a unique data point, tied to you. It’s arguably as bad as handing out a phone number.
I agree with the tradeoffs stated here, but I’d argue that any email address you hand out can serve as a unique data point, tied to you.
myusername@gmail.com for obvious reasons.
myusername+token@gmail.com — easy to filter out the plus and everything after, and it’s very likely more people use this format than uniqueusername@my-own-domain.com, making more likely that this filtering would actually be automatically applied.
What about email relays? Kdhrbrk@mozmail.com doesn’t seem like it could be tied to me, then firefox relay forwards the email to my actual email address.
Yeah, email relays are probably better. I wasn’t necessarily considering those in my comment. But there are tradeoffs there too; now all your incoming mail can be read by a 3rd party, and there’s one more server between you and your email that needs to be up and working for you to properly receive mail.
This is very useful for identifying which services might have sold your email to third parties.
Another downside may be that once you’re using your domain for emails, you better make sure you don’t accidentally let it expire or mess up some configuration and start missing emails, which may be important, sent to you
The bit about moving email services can help privacy indirectly at least… If a provider no longer meets your privacy needs you can move to another that does.
That’s much harder when you don’t have your own personal domain