Go to main content

This information site's privacy policy

Learn how the current Cloudflare/Server/WAF Cookie, Technical Log, and content feedback email can work while reading 87bd.asia and what Sensitive Data should not be sent.

This Policy only explains the limits of Technical Data and Content Feedback on the 87bd.asia information site; it is not a Policy of any Brand Account.

Who this privacy policy is for

This policy applies only to the Frontend use of the 87bd.asia independent information site and content feedback. It does not explain the Data Practices of the 87BD brand Operator, any external accounts, Apps, payment Services, or other Domains. There is no need to provide an 87BD account, password, OTP, PIN, payment Information, or identity Document to read this site.

Current technical configuration

  • The site uses WordPress and has the Yoast SEO Plugin activated.
  • Public Response is being served through the Cloudflare network.
  • Server/WAF is setting a server_name_session Cookie; the observed Response had a Max-Age of 86400 seconds and an HTTP-only Attribute.
  • There are no account, login, registration, payment, or content Submission forms on the Public page.
  • In the Frontend Review of 2026-08-05, Google Analytics, Tag Manager, Meta Pixel, Clarity, Hotjar, Matomo, or Plausible Tags were not found.
  • Content feedback can be sent via the email Link in the Footer; a Dedicated SMTP Plugin was not found, and the Server Sendmail Path was Configured.

This Observation is not a guarantee of future Configuration. The policy will be updated after a Review if technology changes.

Information that may be Processed for request management and security

Cloudflare, Web Server, and Security/WAF Service may Process IP Address, browser/User Agent, device Type, Requested URL, time, Response status, network/Security Signal, and Cookie Identifier to reach a Request, prevent Abuse, and diagnose issues. Nginx Access/error Log and Security Monitoring are Configured.

The full Retention Period for Server, Security Log, or email from Public Configuration could not be determined; therefore, no specific time is being claimed. Hosting, Cloudflare, and Security Service may Process Technical Data according to their own Service Conditions and Configuration.

What to send in an email and what not to send

Feedback content sent to [email protected] is used for Review of content errors, Broken Links, or unclear explanations. You can provide the page URL, Section Heading, correction sentence, Explanation, proof Type, and proof Date. Feedback may be kept via email or relevant records for as long as necessary for Review and Correction; the specific Automatic Deletion Period is currently not confirmed.

Do not send Full Phone, Full Account ID, Password, OTP, PIN, Recovery Code, Full Document, QR, Full Transaction Number or Balance. If you provide a Screenshot, cover Sensitive parts.

For Deletion or Privacy Request, write the page URL of this site and the Request in the same email; do not send any Brand Account Secret.

Contact regarding Privacy or Content Record

You can request to identify, modify, or delete your content feedback sent to this site. Use the email from which you sent the feedback to verify the Request and provide Subject/Date. This site does not control Data of Brand Accounts or Third-party Services.

See Contact Limits and Feedback Steps
Before sending personal information

Provide only necessary and non-sensitive information in content feedback. Do not send Account Secret or Full Document.

See Contact Limits