{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicep3fjq5xs7arczum5uqaetdnyt7tbfoqcoryipubjnkzogwjc3m",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mktt4eujpkg2"
  },
  "path": "/t/cloudflare-concerns/37555#post_7",
  "publishedAt": "2026-05-02T03:35:45.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "Why should Cloudfare—or any “gatekeeping” web service with so much power — be trusted?\n\nWhen you visit a Cloudflare protected site, your HTTPS connection ends at Cloudflare’s server. Cloudflare then decrypts your transmitted data, inspects it, then re-encrypts it and forwards it to the actual website.\n\nCloudflare holds the TLS certificate and is able to read everything as plaintext, including your passwords, form fields, etc.\n\nAfter Snowden brought NSA’s PRISM to light, it would be surprising if the NSA is **not** harvesting the traffic passing through Cloudflare’s servers and have placed them under a gag order, like they have previously done with Google, Apple, Microaoft, etc.\n\nFor everyday users, escaping State-sponsored surveillance and maintaining security against State actors is next to impossible at this point, which is why I’m getting close to giving up the various Inconveniences that come with using GOS, and just switching to an iPhone with lockdown mode as my daily driver.",
  "title": "Cloudflare concerns"
}