> For the complete documentation index, see [llms.txt](https://doc.ozforensics.com/oz-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ozforensics.com/oz-knowledge/general/readme/proprietary-format-ozcapsula-data-container.md).

# Proprietary Format: OzCapsula Data Container

To improve the overall security level or Oz products, we’ve introduced a new **proprietary data exchange format** that provides improved data confidentiality and integrity: OzCapsula.

## How it works <a href="#how-it-works" id="how-it-works"></a>

A proprietary data exchange format is a container that safely stores and transmits transaction-related media data.

<figure><img src="/files/Baoomajml5tIxEqJzdkf" alt=""><figcaption></figcaption></figure>

When you capture video using Oz SDK, your media is placed into the OzCapsula container along with all required information. The package can be processed only in Oz API due to internal mechanisms, so it is significantly more difficult to access the package containing.

{% hint style="info" %}
Please note: we do not disclose specific technical details for security reasons.
{% endhint %}

## Benefits

* **Integrity and Authenticity Guaranteed**. Each container’s content is verified by the API, ensuring data arriving from the user device is genuine, untampered, and fully intact.
* **Full Confidentiality of Internal Data**. Multi-layered cryptographic protection keeps all data, metadata, and technical details hidden from unauthorized viewing, extraction, or interpretation.
* **Unified Data Package**. All content is stored in a single, secure file, simplifying transmission and enabling consistent, predictable processing.
* **Built-In Investigation Tools**. Every action within the container is logged, giving complete visibility for incident analysis and rapid troubleshooting.
* **Strict, Built-In Access Control**. Only authorized systems can open or use the container, preventing misuse, tampering attempts, or unauthorized integration.
* **Ready for High-Volume Workflows**. The container is designed to scale effortlessly, supporting any number of transmissions without performance or integration issues.

## Requirements <a href="#requirements" id="requirements"></a>

Minimal component versions:

* API: **6.6.1**.
* Web SDK: **1.9.10**.
* Native SDKs: **10.0.0**.

You will also require a new token: `session_token`.

## Usage

{% hint style="info" %}
Please note: currently, the container works with [single request mode](/oz-knowledge/guides/developer-guide/api/oz-api/single-request.md) only.
{% endhint %}

1. Configure SDK and API:
   * [Web SDK](/oz-knowledge/guides/developer-guide/sdk/oz-liveness-websdk/using-ozcapsula-data-container-in-web-sdk.md#configuration-overview)
   * [API](/oz-knowledge/guides/developer-guide/api/oz-api/ozcapsula-data-container.md)
   * Native SDK doesn't require additional configuration, you'll just need to use new methods.
2. On your backend, obtain a session token as described [here](/oz-knowledge/guides/developer-guide/api/oz-api/ozcapsula-data-container.md#obtaining-a-session-token) to use it on the frontend.
3. Using Oz SDK methods, take a video and package it along with all required data into container:
   * [Web SDK](/oz-knowledge/guides/developer-guide/sdk/oz-liveness-websdk/using-ozcapsula-data-container-in-web-sdk.md#flow-for-different-architectures)
   * [Native SDK](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/using-ozcapsula-data-container-in-native-sdk.md)
4. Send the container to Oz API using Oz SDK or through your backend (optional) and get the results.


---

# 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://doc.ozforensics.com/oz-knowledge/general/readme/proprietary-format-ozcapsula-data-container.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.