FAQ

Operational answers for the Veilo public interface.

Does Veilo relay payloads?

No. Veilo serves the interface, docs, legal pages, and optional hosted endpoints. Transfer payload work happens in the browser, a future local bridge, or a user-owned remote node.

Does Web Mode support classic BitTorrent?

No. Web Mode uses WebTorrent and WebRTC-compatible swarms. Classic TCP/UDP BitTorrent requires Local Bridge or Remote Node.

Does Veilo store my transfer library?

The transfer library is stored in your browser using IndexedDB with localStorage fallback. There is no server sync in v1.

Can Veilo preview a remote URL or torrent for me?

No. The PHP backend does not fetch user-provided URLs, magnets, torrents, local network addresses, or remote node URLs.

Does Veilo guarantee anonymity?

No. Route selection changes exposure, but peers, trackers, node operators, bridge implementations, and network operators may observe activity depending on the route.

Who handles compliance?

Compliance requests go to compliance@veilo.quest. General contact goes to contact@veilo.quest. FAQ mail goes to faq@veilo.quest.