Unacceptable Response for my pull request and issue.

[Sid5]

Hi Community,

So I was told earlier by the community to open a pull request ( https://github.com/openvinotoolkit/openvino/pull/31297 ) for my patch which I did and then I was told by the pull request reviewers to open an issue for this which I also did but got the same response in the end after waiting for more than 6 months now. Here's the link to the issue: https://github.com/openvinotoolkit/openvino/issues/33137
I am sure there are many ways to locate logs of committed files in the Intel Developer Cloud but they claim everything has been deleted and nothing can be recovered. Are they really saying that they have deleted all their previous data without even taking snapshots fof the drive or creating physical backups? I don't think so. They also said since the intel solutions have been discontinued, they also deleted the solution file which I had downloaded locally on my laptop. This is completely unacceptable, unethical and a breach of trust from Intel. Please advise what can be done now...

[Hari_B_Intel]

Hi Sid5,

Thank you for sharing your concerns. I’d like to clarify a few points to ensure the situation is accurately represented.

Regarding the OpenVINO GitHub workflow, you were advised to submit a pull request with the actual code changes so that maintainers could review and validate the fix. While a PR was opened, it did not include the corresponding code changes. Without concrete changes in the repository, maintainers cannot review, approve, or merge a contribution. Opening an issue or PR alone is not sufficient without the associated code.

With respect to Intel Developer Cloud (IDC), the service has been formally discontinued, and the infrastructure fully decommissioned. In accordance with Intel’s privacy and compliance requirements, customer environments and data stored within IDC were sanitized as part of the shutdown process. As a result, there is no capability to access historical logs, snapshots, or recover files from the former IDC environment.

It is also important to clarify that Intel does not have the ability to access or delete files from a user’s personal device. Any files downloaded locally would remain under the user’s control, and Intel systems cannot remove data from a personal laptop.

We understand this is a frustrating outcome, especially given the time invested. However, without the code being available in the GitHub repository, there is no technical basis for review or validation. If you are able to re‑implement the fix and submit the corresponding code changes, the OpenVINO maintainers will be able to review it through the normal contribution process.

Thank you for your understanding.

[Sid5]

Okay I am still not convinced what you are saying actually did happen the way you are saying. If so, why was there no notice or email regarding the same?
I have proof (email) where Intel told me about the file that they deleted from my local machine, if you want I can show it as well.

[Hari_B_Intel]

Hi Sid5,

Thank you for your response.

I understand that you may not be convinced by the explanation provided. However, I want to be clear and consistent with our position.

Intel Developer Cloud (IDC) has been formally discontinued, and the infrastructure fully decommissioned. In accordance with Intel’s privacy, security, and compliance requirements, customer environments and data hosted on IDC were sanitized as part of the shutdown process. As a result, there is no technical capability to access historical logs, snapshots, or recover files from the former IDC environment.

Regarding notifications, service lifecycle communications are handled through official channels associated with the program or platform at the time. At this stage, regardless of prior notifications, the technical reality remains unchanged: the IDC systems no longer exist, and data recovery is not possible.

With respect to your statement about a local file being deleted, Intel does not have the ability to access or remove files from a customer’s personal machine without explicit authorization. We are not able to act on or validate claims related to local system changes.

At this point, we have provided all the information available, and there is no further action that can be taken on this request. Any future progress on OpenVINO contributions would require the code to be re‑implemented and submitted directly through GitHub for review.

Thank you for your understanding.