privacyguides/privacyguides.org
1
1
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2026-09-29 18:12:53 +00:00
Code Issues Activity

[email services] re-remove custom domain requirement from "Minimum to Qualify" (#3281)

Browse Source 
Signed-off-by: pharaonic-faery <32229347+pharaonic-faery@users.noreply.github.com>
This commit is contained in:
pharaonic-faery
2026-09-28 12:48:07 -05:00
committed by GitHub
parent 9262e3401b
commit dbc140bd50
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/email.md
-1
View File
@@ -277,7 +277,6 @@ We regard these features as important in order to provide a safe and optimal ser
- Must encrypt email account data at rest with asymmetric encryption, where only the user has the private keys needed to decrypt it.
- Must be capable of exporting emails as [Mbox](https://en.wikipedia.org/wiki/Mbox) or individual .EML with [RFC5322](https://datatracker.ietf.org/doc/rfc5322) standard.
- Allow users to use their own [domain name](https://en.wikipedia.org/wiki/Domain_name). Custom domain names are important to users because it allows them to maintain their agency from the service, should it turn bad or be acquired by another company which doesn't prioritize privacy.
- Must operate on owned infrastructure, i.e. not built upon third-party email service providers.
**Best Case:**