Hisense / VIDAA · captured 2026-09-05T17:15:50Z hisense·PIT·0da660 CAP-01241

VIDAA USA Inc Vulnerability Disclosure Policy

The text as it stood on 2026-09-05. This document was captured 3 times that day, so the date on its own does not name one of them — it returns the last. To cite exactly this capture, use /d/hisense-vidaa-usa-inc-vulnerability-disclosure-policy/v/cap-01241, which will always mean this one and nothing else.

Captured: 2026-09-05
Words: 518
HTTP: 200
Size: 107.7 KB
State: Unchanged

HTML (as served) Extracted text

Cite this capture

Everything a footnote needs, including the checksum, so a reader can confirm they are looking at the same bytes you did. Select and copy.

Hisense / VIDAA, “VIDAA USA Inc Vulnerability Disclosure Policy”.
Captured 2026-09-05T17:15:50Z by Terms Accepted.
Permalink: https://termsaccepted.org/d/hisense-vidaa-usa-inc-vulnerability-disclosure-policy/v/cap-01241
Original:  https://www.vidaa.com/vidaa-usa-inc-vulnerability-disclosure-policy
SHA-256:   879b7a9ab1d79e141a4899ebdeffa0603ab8f2f88c60f16a06103adb3c6b3294
Provenance: captured directly from the publisher.

Verify this file — SHA-256

The file below is stored under this checksum, so altering it would change its name. Download the copy above and run sha256sum on it: if the value differs from this one, you are not looking at what we captured.

879b7a9ab1d79e141a4899ebdeffa0603ab8f2f88c60f16a06103adb3c6b3294

Also captured that day

Every reading of this document on 2026-09-05. They may be identical; where they are not, the difference is a change the publisher made within a single day.

Captured Permalink Words State

2026-09-05T11:33:07Z cap-00135 891 First capture

2026-09-05T15:22:50Z cap-00510 518 Captured a different way (not a content change)

Captured	Permalink	Words	State
2026-09-05T11:33:07Z	`cap-00135`	891	First capture
2026-09-05T15:22:50Z	`cap-00510`	518	Captured a different way (not a content change)

The document

VIDAA USA Inc. Vulnerability Disclosure Policy - VIDAA VIDAA USA Inc. Vulnerability Disclosure Policy Last Updated: January 14, 2024 INTRODUCTION This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us. We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it. We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures. REPORTING If you believe you have found a security vulnerability, please submit your report to us using the following link email: VIDAASecurity@vidaa.com. In your report please include: Model number on which the vulnerability can be observed Title of vulnerability (mandatory) Description of vulnerability (this should include a summary, supporting files and possible mitigations or recommendations) (mandatory) Impact (what could an attacker do?) (mandatory) Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers. Contact Information. If you would like us to follow-up with you with status reports, please provide us with sufficient contact information, such as contact name and email address, so that we can keep in touch with you. You are not required to provide contact information to submit a report. Please note your contact information will only be used to contact you regarding the vulnerability you reported and will not be used for any other purpose. Your personal information will be protected as described in Privacy Policy (https://www.vidaa.com/privacy/). WHAT TO EXPECT After you have submitted your report, and if you provide contact information, we will respond to your report within 7 calendar days to acknowledge the receipt of your report and aim to triage your report within 15 working days. We’ll also keep you informed of our progress, including but not limited to: Status update of your report. Significant new information regarding to your report. Changes to existing fix plans. Disclosure plans, if any Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation. We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately. Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us. GUIDANCE You must NOT: Break any applicable law or regulations. Access unnecessary, excessive or significant amounts of data. Modify data in the organization’s systems or services. Use high-intensity invasive or destructive scanning tools to find vulnerabilities. Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests. Disrupt the organization’s services or systems.