# Data security with FHE and TEE

Data stored within the Inferix network is categorized into two types:

* *Session data* which includes input data along with temporary data generated during the rendering process. This data typically exists for a short duration, ranging from a few minutes to several hours.
* *Persistent data* which consists of the output from the rendering process and is stored long-term in the system. Examples of persistent data include images and videos after rendering, or VR scenes created after lightmap baking.

Inferix encrypts session data to ensure it remains secure against decryption attacks during data transfer. For persistent data, Inferix offers long-term hosting on its storage system and allows users to share the data publicly or with specific permissions over the Internet.

Our surveys show that, on average, over 80% of 3D model data from graphic artists are public data shared on the internet, while nearly 20% are their original creations and need to be protected. Therefore, Inferix will offer data security level options for end-users to choose from. Higher security level options will incur additional costs for computing resources, storage, and bandwidth, which will be added to the service fees that the end-user must pay.

There are three components related to data security in the Inferix network: the Manager, Worker and Verifier. We will present a security approach for each of these components below.


---

# 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.inferix.io/inferix-whitepaper/decentralized-visual-computing/data-security-with-fhe-and-tee.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.