> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web2-integration/file-encryption.md).

# File encryption

Web2 file methods use the active session instead of a connected wallet. The lifecycle remains asynchronous:

1. Start an upload through the Web2 files wrapper.
2. Capture the returned job ID.
3. Poll with the jobs wrapper.
4. Download the completed encrypted or decrypted file.
5. Apply local integrity, retention, and access policies.

## Operational design

* Bind job IDs to the authenticated principal in your own database.
* Use bounded exponential backoff rather than aggressive polling.
* Set a timeout and expose a resumable state in the product.
* Validate file names, MIME types, and sizes before upload.
* Do not render decrypted content solely based on a user-controlled MIME type.
* Delete temporary plaintext as soon as the product workflow allows.

A successful upload only means the job was accepted. The completed job status is the authoritative signal that output is ready.


---

# 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web2-integration/file-encryption.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.