> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zas.red/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Straight answers about what Zas is for, how it compares to Drive, Dropbox and WhatsApp, what it encrypts, and what it will not do.

## The product

<AccordionGroup>
  <Accordion title="What is Zas for?">
    Send something from one device, use it on another, done.

    No cables, no emailing yourself, no chat with yourself growing forever. Whatever you do not pin leaves on its own, so there is nothing to tidy up later.
  </Accordion>

  <Accordion title="Why not WhatsApp or Telegram?">
    Messengers are built for conversations. What you send yourself piles up in an endless chat, photos get compressed, and your files live on their servers.

    Zas sends the original, within the limit the app shows you, without compression. It encrypts the file before upload and deletes it when its time runs out.
  </Accordion>

  <Accordion title="Why not Drive or Dropbox?">
    Those are warehouses. You store, sort folders, manage quotas, and pay to keep everything forever.

    Zas is a corridor. Things pass through, get used, and leave. There is nothing to organize and nothing piling up.
  </Accordion>

  <Accordion title="Do I need an account?">
    No. Open [zas.red](https://zas.red) and send. An anonymous session gives you 30 MB and two days.

    An account raises that to 100 MB and five days, and works on phones and tablets. See [Without an account](/en/getting-started/anonymous-sessions).
  </Accordion>

  <Accordion title="Do I have to install anything?">
    No. Zas is a web page. That is deliberate, so it works on a locked-down work computer.

    Native apps exist for [iPhone and iPad](https://apps.apple.com/app/id6796492671) and for [Android](https://play.google.com/store/apps/details?id=com.zas.android), where Zas becomes a system share target.
  </Accordion>

  <Accordion title="Can a coding agent use Zas?">
    Yes. Claude Code, Codex or any MCP client can send files and notes into the channels you grant it, and read them back where you allow it.

    The agent gets an identity of its own that you approve and can revoke. It never holds your account key, and every item it sends carries the `>_` agent mark.

    It can also be either end of a [Direct transfer](/en/concepts/direct), and it can ask for a shorter life on what it sends — one day at the least. See [Agents](/en/agents/index).
  </Accordion>
</AccordionGroup>

## Files and limits

<AccordionGroup>
  <Accordion title="Does Zas compress my photos or video?">
    No. Zas does not compress and does not re-encode. What arrives is what you sent.
  </Accordion>

  <Accordion title="My file is larger than 50 MB. Now what?">
    Use [Direct transfer](/en/concepts/direct). It goes device to device, up to 10 GB on the free plan, and uses none of your storage.

    Both devices need Zas open at the same time.
  </Accordion>

  <Accordion title="What happens when I run out of storage?">
    Nothing breaks. Zas tells you before you send, not after.

    Storage frees itself as items expire. Deleting an item frees its space immediately. A pinned item holds its space until you release it.
  </Accordion>

  <Accordion title="Can I get back something that expired?">
    No. There is no trash, no undelete, and nobody at Zas can restore it.

    That is the product working as designed, not a support problem.
  </Accordion>
</AccordionGroup>

## Privacy and security

<AccordionGroup>
  <Accordion title="Is Zas end-to-end encrypted?">
    No, and Zas says so on purpose.

    Everything is encrypted on your device before it leaves. The database and object storage receive encrypted bytes, not open filenames, content or previews. But a separate service derives account keys, and an operator who controls that service and has account identifiers could reconstruct keys.

    Zas therefore does not call this design end-to-end encryption. See [Encryption](/en/concepts/encryption).
  </Accordion>

  <Accordion title="Can Zas read a public share link?">
    No. The key for a public link sits after the `#` in the address, and a normal web request does not send that part to a server.

    Anyone who has the whole link can open the item. Treat the link like the file.
  </Accordion>

  <Accordion title="Why are some notes covered?">
    Because the sending device marked the note as possibly holding a password. That check happens on the sending device, before encryption, and the mark stays inside the encrypted item.

    Tap the note to reveal it. It covers itself again when you switch channels or come back to the tab.

    This only protects against someone reading over your shoulder. A note with no mark is shown normally, and that does not mean it holds no password. You can turn covers off in Settings.
  </Accordion>

  <Accordion title="What does Zas measure about me?">
    Product events, not people. Zas can send an internal account ID, technical device or session IDs, versions, plan, language, storage use, and numbers such as size and duration.

    It never sends text, file or channel names, MIME type, profile photo, email address, name, content IDs, secret links or full addresses. There is no autocapture, no session recording, and no advertising.

    Analytics does not load at all on public links, in anonymous sessions, or in the Apple share extension and widget. See [What the server can see](/en/concepts/privacy).
  </Accordion>
</AccordionGroup>

## Sharing

<AccordionGroup>
  <Accordion title="Can I share with other people?">
    Yes, two ways.

    Share one item with a public link that dies when the item does. Or share a whole channel with someone, and choose whether they can send or only read.
  </Accordion>

  <Accordion title="How long does a channel invite last?">
    Seven days, or until the channel is full. A channel holds 50 people.

    You can revoke an invite link at any time. Revoking it does not remove anyone who already joined.
  </Accordion>

  <Accordion title="How do I get more pins?">
    Each person new to Zas who joins a channel you are in adds one permanent pin for everyone in that channel, up to 20.

    On the free plan that takes you from 15 pins to as many as 35.
  </Accordion>
</AccordionGroup>

## Plans and payment

<AccordionGroup>
  <Accordion title="What does Zas cost?">
    The consumer product is free, within the limits on the [Limits](/en/reference/limits) page.

    [Zas for Enterprise](/en/enterprise/index) is USD 8 per seat per month, with a 14-day trial.
  </Accordion>

  <Accordion title="Is there a Pro or Max plan?">
    Not for sale. Zas does not sell storage, retention, or recovery.
  </Accordion>

  <Accordion title="Can my company get SSO or SCIM?">
    No. Sign-in is Google, Apple, or an 8-digit code sent to your email address, everywhere in Zas. People join an organization by invitation.

    Organization ownership comes from a verified work email address, not from a DNS record.
  </Accordion>

  <Accordion title="Can my organization control coding agents?">
    Two settings. **Member agents** sets how many agents each member or guest may pair, from 0 to 10; setting it to 0 turns agents off for them, and owners and admins are exempt.

    **Agents in organization channels** decides whether an agent may hold one of the organization's channels at all. It is off by default, it exempts nobody, and turning it off closes every such grant immediately. A **Governance → Agents** screen lists the agents that reach your channels and revokes any of them. See [Agents in an organization](/en/agents/enterprise).
  </Accordion>

  <Accordion title="How do I get support?">
    By email only, at [support@zas.red](mailto:support@zas.red). This applies to every plan, including Zas for Enterprise.

    Premium support, such as phone support or guaranteed response times, comes only from Zas partners. See [Support](/en/reference/support).
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.