> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/getting-started/self-serve-dashboard/sprinto-policies/media-disposal-policy.md).

# Media Disposal Policy

## 1 Objective

Secure disposal of electronic and physical media adds a layer of protection to prevent critical data from being exposed to unauthorized individuals. This policy aims to mitigate the risk of unauthorized data recovery. It demonstrates to customers, \<Company Name> staff, and other partners that \<Company Name> protects their data even after it has fulfilled its purpose.

## 2 Scope&#x20;

This policy applies to all \<Company Name> issued devices or equipment that process, store, transmit, or serve as an access point for any critical data.  Specifically,  it applies to company-issued laptops/workstations that are being permanently decommissioned.&#x20;

## 3 Policy Statement

To securely dispose of company-issued laptops/workstations, the following steps can be followed:

* Encrypt the entire hard disk using a robust algorithm and a lengthy password.
* Securely delete all information by using software solutions.
* Physically destroy the device through methods such as incineration or shredding.
* It is recommended to use all three methods for extremely critical and sensitive data.
* For data with lower levels of criticality, one of these methods is sufficient.

## 4 Document Security Classification

Company Internal (please refer to the Data Classification policy for more details).

## 5 Non-Compliance

Compliance with this policy shall be verified through various methods, including but not limited to automated reporting, audits, and feedback to the policy owner. Any staff member found to be in violation of this policy may be subject to disciplinary action, up to and including termination of employment or contractual agreement. The disciplinary action shall depend on the extent, intent, and repercussions of the specific violation.

## 6 Responsibilities

The Information Security Officer is responsible for approving and reviewing policy and related procedures.  Supporting functions, departments, and staff members shall be responsible for implementing the relevant sections of the policy in their area of operation.

## 7 Schedule

This document shall be reviewed annually and whenever significant changes occur within the organization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/getting-started/self-serve-dashboard/sprinto-policies/media-disposal-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.