> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-products/security/data-encryption-overview.md).

# Data Encryption Overview

NeevCloud ensures all data in transit is encrypted. For data at rest, NeevCloud provides the option to create encrypted storage volumes, giving you full control over your encryption posture.

### Encryption in Transit

All NeevCloud services are served over **HTTPS (TLS 1.2 / 1.3)** with certificates from a globally trusted Certificate Authority. This covers the Dashboard, API endpoints, Object Storage, and the Customer Portal. No action is required — encryption in transit is always enabled by default.

***

### Encryption at Rest

NeevCloud offers two volume types for block storage:

| Volume Type      | Encryption        | Use Case                                                                    |
| ---------------- | ----------------- | --------------------------------------------------------------------------- |
| **Default/NVMe** | Not encrypted     | General-purpose workloads where platform-level encryption is not required   |
| **Encrypted**    | AES-256 encrypted | Workloads handling sensitive or regulated data requiring encryption at rest |

When you select the **Encrypted** volume type during volume creation, all data written to that volume is automatically encrypted using **AES-256** at the platform level. Encryption and decryption happen transparently — no setup or key management is required from your side.

{% hint style="info" %}
**How to enable:** While [creating a volume](/neevcloud-products/volumes/create-a-volume.md) from the Dashboard, simply choose the **Encrypted** volume type. Your data will be encrypted at rest automatically.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.neevcloud.com/neevcloud-products/security/data-encryption-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.