Operational Manual.

ZYQO Send supports two main tiers: Guest nodes allow up to "500MB per transfer", while ZYQO Passport holders unlock a "3.0GB payload" limit. This capacity is specifically tuned for the "students" circuit to handle heavy academic datasets and media projects.

Transit links are temporary by design. Guest links remain active for "24 hours". Passport-authenticated links stay active for "7 days". After this period, our automated "Hard Purge Protocol" is triggered, wiping the data permanently from our Bharat clusters.

Yes. Every transfer is encapsulated in a "TLS 1.3 cryptographic tunnel". Furthermore, Passport users can apply an additional layer of "AES-256 password protection" on their links. This ensures that only the intended recipient with the key can decrypt and access the binary payload.

No. ZYQO follows a "Non-Custodial Data Model". During the ingestion phase, we only process metadata required for architectural routing (file name, extension, and size). We possess no "Master Key" to view or modify your private files stored temporarily in our R2 clusters.

ZYQO Send utilizes localized "Bharat Nodes" on the Cloudflare R2 backbone. Your data remains within the sovereign legal jurisdiction of India. We do not utilize offshore data centers in the US or Europe for Indian transit nodes, ensuring sub-100ms latency.

No. ZYQO Send is a "Zero-Tracking Transit Node". Recipients can download files without creating an account or providing an email address. We prioritize frictionless data movement over harvesting user analytics.

Yes. The "Vault-Send Bridge" is currently in systemic beta. Passport holders can select a file in their Vault and generate a Send-Link instantly, bypassing the need for a fresh upload. This is part of our integrated ecosystem vision for 2027.

Official ZYQO Send links always originate from the `send.zyqo.in` domain and utilize HTTPS (TLS) encryption. Always check the browser padlock icon to ensure you are interacting with our sovereign nodes.