Processed locally. Tested with documented evidence.

Three layers of verification

Local link processing was examined on three separate levels:

1. a technical network restriction provided by the Content Security Policy;
2. a recorded browser Network test using unique test values;
3. a successful link calculation without an active network connection after the app had fully loaded.

No single layer is a complete proof on its own. Together, they document how the SafeShare App behaved during the described test run.

1. Network restriction

For the tested production version, the SafeShare App was delivered with a Content Security Policy containing this directive:

connect-src 'none'

This directive restricts script-initiated connections covered by connect-src. These include connections made through fetch, XMLHttpRequest, WebSocket, and EventSource.

It does not mean that the entire website is unable to make any network requests. The initial document and its CSS, JavaScript, images, and other static resources still have to be loaded. Those requests are not generally controlled by connect-src.

The policy is therefore a technical restriction on specific connection paths. It is not a claim that the website itself can load without a network connection.

2. Browser Network test

The documented run used a test link containing three unique values:

• safeshare-live-test
• test123
• example.com/path

The browser recorded 11 requests while SafeShare processed the link.

The recorded result was:

• 11 requests in total;
• safesharepro.com was the only request host;
• no external hosts;
• 0 occurrences of safeshare-live-test in actual request components;
• 0 occurrences of test123 in actual request components;
• 0 occurrences of example.com/path in actual request components.

During the documented test run, none of the unique values from the submitted test link was found in a request.

The 11 requests consisted of the SafeShare document and the static resources required to load it. “Processed locally” therefore does not mean that the website itself requires no initial page or resource requests.

This result applies only to the recorded run and does not support a general claim about other circumstances or future versions.

3. Offline-after-loading test

For a second functional test, the SafeShare App was first allowed to load completely. Windows airplane mode was then enabled.

Without reloading the page, this link was entered:

https://example.com/path?utm_source=offline-test&fbclid=offline123&ok=1

The observed result was:

https://example.com/path?ok=1

utm_source and fbclid were removed. ok=1 remained.

For the tested browser state, the link calculation continued to work without an active network connection after the app had fully loaded.

This does not show that SafeShare is a fully installable offline web app. It also does not show that the website can be opened offline without first being loaded. The test covered only the calculation inside an already loaded app.

Verified version

The code revision identifies the app version that was tested. The later documentation commit adds the technical report and measurement artifacts without changing the tested app code.

Technical evidence

The full technical report contains:

• the scope and limits of the test;
• the CSP check;
• the Fragment Launcher check;
• the browser Network test;
• the offline-after-loading test;
• reproduction instructions;
• the paths and SHA-256 values of the published artifacts.

The repository also contains:

• a sanitized HAR copy of the 11-request run;
• one screenshot showing the 11 recorded requests;
• three Network-filter screenshots showing 0 / 11 requests.

The raw HAR is not part of the repository. The offline test is documented in the report but still has no published screenshot artifact.

What the evidence shows – and what it does not

The documented version shows that:

• the app was delivered with a restriction on connections covered by connect-src;
• none of the three unique test values appeared in an actual request component during the recorded run;
• the link calculation continued to work without an active network connection after the app had fully loaded.

The test is not a certification, a guarantee of complete network isolation, or a general claim that every possible use of the website complies with all privacy requirements.

Reproduce the test

The technical report documents the individual test steps. It includes the test URL, observed results, Network-filter values, and the stated limits of the test.

The SafeShare App can be used separately to clean individual links locally in the browser.