Every page on Sharedrop renders inside a locked-down, isolated sandbox, so it can't touch your account, your cookies, or your files. What differs between pages is two things: whether the page runs JavaScript, and whether it can reach the network. There are three modes.
Document mode. Scripts and event handlers are removed when the file is uploaded, and blocked again when the page is viewed. Static is the safest mode and the right choice for anything that doesn't need to run code: reports, exports, documents. Because scripts are removed at upload, a static page can't be “switched on” later; to add interactivity, re-upload the source as an interactive page.
JavaScript runs inside the sandbox, so tabs, filters, charts, and other local interactions work. Arbitrary external scripts, fonts, images, and network calls (fetch/XHR, tracking beacons) are blocked by a strict Content-Security-Policy, and the page's own assets (its JavaScript, CSS, images, fonts, and data files) are served from Sharedrop as part of its bundle, so a rich interactive report can be completely self-contained with no third-party requests.
One honest limit: because real JavaScript runs, this isn't a hard “no external request ever”guarantee. The page can't fetch, beacon, or load remote resources, but, like any web page, a script can still navigate you to another site(the same as following a link). It still can't read your Sharedrop session, your cookies, or this page's access token. For content you don't trust at all, use a static document; to let a page deliberately talk to other sites, turn on external network below.
This is the default for interactive pages. To keep a report local-only, inline small assets or upload the whole folder (its index.html plus its assets) so everything ships with the page instead of loading from a CDN.
Some interactive pages genuinely need third-party resources. An owner can turn on external networkfor a page they created or whose source they trust. When it's on, the page may load remote scripts, assets, and fonts, and call external APIs.
That power comes with risk: an external-network page can phone home, beacon activity about whoever views it, or change its behaviour later if the remote code it loads changes. Because of that, external network is off by default, enabling it shows a clear warning first, and public or shared pages with it enabled carry a visible “External network” indicator in the viewer so people can see the page reaches outside Sharedrop.
None of these modes loosen the sandbox. Across all of them, a page can't read your Sharedrop session or cookies, can't access your files, and can't navigate your browser, open pop-ups, or submit forms as you. Network access is the only thing the modes change, and for interactive pages, it's off until you deliberately turn it on.