Delivery is public by default: a pull zone exists to serve things. Everything below narrows that.
Signed URLs
A signed URL carries an expiry and a signature derived from the zone's signing key. The edge checks both before serving, so a link that leaks stops working on its own schedule rather than staying valid forever.
Mint them from the panel or through POST /api/v1/signed-urls. A signed URL can additionally
restrict the country it may be used from, with an allow list or a block list.
Rotating a zone's signing key invalidates every URL already signed with it. The panel says so before rotating, because this is not a reversible action for links already in circulation.
Referrer, country and IP rules
A pull zone's security policy can require a referrer from a named set of hosts, restrict which countries may fetch from it, and allow or block IP ranges. These are enforced at the edge, so an unauthorised request never reaches storage and never costs an origin fetch.
What none of this is
None of it authenticates a person. It restricts where a request may come from, not who is making it. Anything that must know the user belongs behind the control plane's own authentication.