PRIVACY, VULNERABILITIES & INCIDENTS

Report a concern.

A proposed process for submitting, tracking, investigating, and resolving data privacy and security concerns.

Draft version: 19 October 2026 · Not yet effective

1. Submit a report

Send reports about privacy concerns, suspected misuse of advertising data, security vulnerabilities, or incidents to:

Use the subject “Security or privacy report”. Include:

• A description of the concern and the affected service or page.
• When the issue occurred or was observed, including your time zone.
• Steps to reproduce the issue, where appropriate, without accessing other parties' data.
• Redacted evidence and a contact address for follow-up.

Do not email passwords, verification codes, access tokens, full customer datasets, or unnecessary personal information. Ask for an agreed secure transfer method if evidence is sensitive.

2. Acknowledge and track

A designated company contact monitors admin@diguanglongtech.com and coordinates incoming reports. Under this proposed process, the contact should acknowledge receipt, assign a reference to the report, record its status in a restricted incident register, and request any information needed to assess it. An email thread can be used for follow-up using the reference.

3. Assess and respond

Reports concerning a particular tool are routed to that tool's developer for technical investigation and corrective action. The company contact should coordinate this work, including identifying affected systems and data and prioritizing any required containment. Access to incident information should be limited to those who need it for investigation and resolution.

Where an incident involves Amazon data or services, the company must follow applicable Amazon agreements, reporting requirements, and the relevant official support or security channels. Reports to this mailbox are not a substitute for contacting Amazon directly where required.

4. Resolve and close

The company should record the investigation outcome and corrective actions, verify the resolution, and update the reporter where appropriate. Incident records should include relevant dates, assigned responsibility, status changes, and closure details. Necessary changes to access permissions, procedures, or safeguards should be documented.

5. Responsible reporting

Please avoid disruptive testing, accessing other people's information, or publicly disclosing sensitive evidence. This page does not authorize security testing, grant access to systems, or establish a bug bounty program.

6. Privacy enquiries

For general privacy questions and information requests, see our privacy notice and use the same contact address.