> For the complete documentation index, see [llms.txt](https://docs.zata.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zata.ai/account/ingress-and-egress-policy.md).

# Ingress and Egress Policy

#### Ingress Policy

Ingress refers to data uploaded into Zata.ai, such as files, backups, or objects transferred from applications and systems to Zata storage.

* Data uploads to Zata.ai are free and unlimited.
* There are no bandwidth restrictions on incoming data.
* Users can upload any amount of data without additional charges.

***

#### Egress Policy

Egress refers to data downloaded or transferred out from Zata.ai storage to external systems or users.

* Users get free egress equal to their active storage volume per month.
* If egress usage exceeds the active storage volume, the account will be temporarily suspended.
* Service will resume after upgrading the storage plan or when the next billing cycle begins.

**Example:**\
If a user has 100 TB of active storage, they can download up to 100 TB for free in a month.\
If downloads exceed 100 TB, the account will be suspended until the plan is upgraded or the next billing cycle starts.


---

# 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.zata.ai/account/ingress-and-egress-policy.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.