# Protocol: cloud Chromium browser fingerprint surfaces

Frozen before measured collection, 17 November 2026, UTC.
Duration cap: ≤7 days.

**Amendment A1 (same day, post Runtime Secrets injection):** activate
`proxy-us-http` and `proxy-us-socks` after env discovery confirms the
component secret names below. Cloud-direct main run remains the baseline;
proxy legs are comparison conditions, not replacements.

## Decision and scope

Sibling FreePolicyTools studies measured application proxy routing, proxy
authentication transport, VPN website warnings, and browser-path leakage.
Those studies ask whether a configured tunnel or proxy engages for network
traffic.

This study asks a different question: on a Cursor-hosted USA cloud VM, in a
fresh Playwright Chromium, which browser fingerprint surfaces remain stable
across fresh contexts, and how those surfaces relate to independently observed
document IP echoes.

Primary surfaces are researcher-operated: a local fixture page that collects
canvas, WebGL, audio, navigator, screen, timezone, font-metric and WebRTC
candidate-class signals. Vendor “fingerprint uniqueness score” pages are not
the primary sample.

## Frozen route conditions

Main matrix (two passes minimum; three preferred):

1. `cloud-direct` — Playwright Chromium, no browser proxy, no VPN tunnel claim.
2. `proxy-us-http` — ProxySeller residential/USA HTTP as Chromium proxy **only if**
   Runtime Secrets inject discoverable `PROXYSELLER_*` / proxy env names.
3. `proxy-us-socks` — same credentials as Chromium SOCKS5 **only if** secrets present.

Supplementary, not pooled into stability totals unless activated:

- `proxy-dead` — invalid local proxy port; fixture served with loopback bypass;
  record whether fingerprint collection still completes and how public fetches fail.
  **Amendment A1 status:** not activated (disclosed in the research article; not a
  silent skip of a main-matrix cell).

CometVPN is VPN-only affiliate/product context. Hosted VMs may expose
`/dev/net/tun`, but this protocol does **not** claim a CometVPN tunnel
measurement unless a working VPN path is proven in an amendment. Do not use
CometVPN as HTTP/SOCKS.

## Env discovery (required before proxy legs)

1. Presence-only checks for proxy/seller tokens (never print values).
2. Explicit candidate presence map for common `PROXYSELLER_*` names.
3. Record names present (never values) in `evidence/env-discovery.json`.

### Discovered Runtime Secret names (A1)

Presence confirmed for component assembly (values never recorded):

- `PROXYSELLER_HOST`
- `PROXYSELLER_HTTP_PORT`
- `PROXYSELLER_SOCKS_PORT`
- `PROXYSELLER_USER`
- `PROXYSELLER_PASS`

Collector assembles Playwright proxy as:

- HTTP: `http://$PROXYSELLER_HOST:$PROXYSELLER_HTTP_PORT` + Playwright username/password fields
- SOCKS5: Chromium does not accept SOCKS5 username/password. The collector uses
  `proxy-chain` to expose a local unauthenticated HTTP forwarder that authenticates
  to upstream SOCKS5 (`socks5://$PROXYSELLER_HOST:$PROXYSELLER_SOCKS_PORT`). Design
  records `proxyViaLocalAnonymizer: true` for that path. Upstream remains ProxySeller
  residential SOCKS; the local forwarder is a Chromium constraint workaround, not a
  second commercial hop.
- Always bypass `127.0.0.1,localhost,<-loopback>` for any residual local traffic
- Fixture delivery for all conditions: Playwright `page.setContent(fixtureHtml)` so
  residential proxies that deny loopback targets (`503 Target host denied`) cannot
  block the researcher page. Document echoes still traverse the configured proxy.
- Document echo fetches use a 12s AbortSignal; media/audio/WebRTC stages have outer
  timeouts so a single hung API cannot stall the visit beyond the collector wait

If no proxy env names are present, collect `cloud-direct` only.
Do not invent credentials.

Screenshots: after each successful visit, capture a full-page PNG of the fixture UI
(hashes / renderer / timezone only). Public package may include those PNGs; raw
echo bodies and salts remain private.

## Collection rules

- Isolated Chromium via Playwright; no personal profile; one browser context per visit.
- Locale `en-US`, timezone `UTC`, viewport `1360×900`, JavaScript on, ordinary TLS.
- Headless Chromium allowed on cloud VMs; record browser version and headless flag.
- Local fixture served on `127.0.0.1`. Public echoes (document fetches from the
  page): `api.ipify.org`, `api64.ipify.org`, `ipinfo.io/json`,
  `cloudflare.com/cdn-cgi/trace`.
- WebRTC: `RTCPeerConnection` with `iceServers` `stun:stun.cloudflare.com:3478`
  only. Record host/srflx/relay **counts and private-range class**, not raw IPs.
- Fingerprint surfaces: navigator subset, screen, timezone, canvas 2D hash,
  WebGL vendor/renderer + canvas hash, OfflineAudioContext hash when available,
  limited canvas font-metric set, media-device counts, storage availability.
- Composite hashes are SHA-256 over canonical JSON of selected surfaces.
- Never complete CAPTCHAs, log into third-party sites, or submit forms.
- Failed guards exclude that condition until reviewed; they are not successes.

## Public evidence

Raw addresses, credentials, HMAC keys and original screenshots stay in `private/`.
Public records keep only:

- salted opaque labels for document IP echoes (not raw IPs)
- country/org labels from ipinfo when present
- fingerprint surface hashes and non-identifying structured fields
- whether WebRTC candidates were host/srflx/relay and private-range class
- Playwright / Chromium versions, viewport, locale, timezone, headless flag
- env **names** discovered (never values)

## Interpretation limits

Stable hashes across fresh contexts show that these surfaces did not vary in
this Chromium on this VM. They are not a population uniqueness estimate, not
proof of named-person identification, and not a claim that a VPN or proxy
“fails to anonymize.” An IP change (when measured) that leaves fingerprint
hashes unchanged demonstrates separation of network identity from browser
rendering identity on this fixture — nothing more.

Proxy findings are endpoint- and account-configuration specific. CometVPN is
not a measured tunnel in the frozen cloud-direct phase.

## Funding / affiliates

FreePolicyTools is a ProxySeller and CometVPN affiliate. Affiliate CTAs may
appear in the published article. Affiliates do not change methods, results, or
limitations. No competitive ProxySeller uptime benchmarking.
