{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifrjaxlikv4qk5kvbcrlrq4wrybdtfi6vgfewnrmgret73balooky",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkw57gbasfi2"
  },
  "path": "/t/my-grievances-with-proton/37526?page=4#post_75",
  "publishedAt": "2026-05-03T01:49:25.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "pm.me",
    "@pm.me",
    "@proton.me"
  ],
  "textContent": "ZenByte:\n\n> I think Proton is getting singled out unfairly.\n\nProton is being “singled out” because this thread was about my own experience with Proton and my grievances with them. I have a grievance with them specifically because I used their service.\n\nZenByte:\n\n> I don’t know if many people would bother with their additional pm.me etc aliases if they understood they would permanently lose them if they cancel their subscription.\n\nThis is wrong. I bothered with @pm.me aliases because when your subscription ends, you can still receive emails sent to your @pm.me variant; just not send. At least, if you can receive an email by that alias, you can inform your contacts that you are using the free @proton.me address moving forward. You do not “lose” your @pm.me aliases in the same way as you lose your other Proton aliases.\n\nAdditional Proton addresses are entirely disabled; you can’t send nor receive emails. So any prospective contacts who send emails to those aliases will be sending emails into a black hole. You will not be informed if contact was attempted, nor can you redirect them to your free address, or another address for future contact.\n\nThe reason this caught me so off-guard is because it’s a break of pattern of everything else Proton has set. When your subscription ends, your @pm.me alias becomes receive only, your SimpleLogin aliases remain functional, but your Proton aliases just simply die. And the reason why I made this mistake is because I trusted Proton to not make me feel trapped.",
  "title": "My grievances with Proton"
}