# Security Compliance

### Exciting News: Proxyman Achieves SOC 2 Type 2 Compliance!

<figure><img src="/files/AZmhRbqFjI4pi5B8MDh2" alt=""><figcaption><p>Proxyman is now SOC 2 Compliant</p></figcaption></figure>

## What is SOC 2 Type 2 Compliance?

SOC 2 is a stringent audit by the AICPA. A Type 1 report confirms our security controls are well-designed at a specific time, evaluating five key criteria:

* **Security**: Protects against unauthorized access.
* **Availability**: Ensures system availability for use.
* **Processing Integrity**: Guarantees complete and accurate processing.
* **Confidentiality**: Safeguards confidential information.
* **Privacy**: Handles personal data per our privacy policy.

## Why SOC 2 Type 2 Compliance Matters

In today's digital world, strong security is essential. For a debugging proxy tool managing sensitive data, SOC 2 compliance:

* Validates security controls.
* Shows commitment to data protection.
* Offers independent verification.
* Demonstrates adherence to industry standards.

## What Does This Mean for You?

### **As a Customer**

* **Enhanced Security**: Your data enjoys robust protection.
* **Privacy Assurance**: Your information is handled responsibly.
* **Transparency**: Security practices are verified.
* **Trust**: Confidently use Proxyman in enterprises.

### **As a Reseller**

* **Credibility**: Assure customers of our security.
* **Enterprise-Ready**: Easily recommended to security-focused organizations.
* **Compliance**: Meet vendor assessment needs.
* **Documentation**: Access for sales support.

## Privacy Statement

#### You can find our [Privacy Policy](https://proxyman.io/privacy)

## What's Next?

This milestone is the first step. Our focus includes:

* Maintain SOC 2 Type 2 compliance.
* Conducting regular audits.
* Continuously enhancing security practices.

For more about our security and privacy policies, visit our Privacy Policy, Terms of Service, and SDLC Policy. Questions? Reach us at <support@proxyman.com>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.proxyman.com/security-compliance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
