Chinafy does not store requests or responses that are defined as private in your cache controls just as we respect the other rules in your cache header.
In order for us to optimize your content, we first decrypt, parse, then re-encrypt your data for delivery. Our practice is standard and identical to how content delivery networks (CDNs) optimize for data delivery, except with an added feature that scans it for China web resource incompatibilities.
It’s not possible to run a CDN, or more specifically, our multi-CDN and/or operate any proxying without processing that data as per above, seeing as this is the basis on which CDNs operate.
We need to store every web page and file temporarily to facilitate the Chinafying process, that is the scanning, identification, and replacement of resources. This typically takes 1-3 minutes (depending on the load/queue) following which it is then immediately purged thereafter.
Similarly for web socket and API calls, as a proxy, we’d need to modify the host headers as well which can only occur by encryption/decryption and subsequently reading/updating.
It is for that reason we place emphasis on putting security measures in place instead of avoidance of content. These measures include
- Data encryption in Transit and at Rest
- Enforced two-factor authentication (2FA)
- Adherence to industry cloud security standards
Visit our Trust Center for more information.
Comments
0 comments
Please sign in to leave a comment.