docs: tighten public privacy guidance

Author: MSTU0

CLI_FLAGS.md

@@ -240,8 +240,8 @@ To keep SOCKS5 proxying but avoid QUIC/HTTP/3, add the standard `--disable-quic`
 
 <a id="pac-request-policy-ent-tier3"></a>
 <a id="pac-like-request-callback-ent-tier3"></a>
-### PAC-Like Request Callback (ENT Tier3)
-ENT Tier3 profiles can use trusted PAC scripts for request callback workflows while preserving standard PAC routing. Configure PAC through the standard `--proxy-pac-url` flag and keep the PAC source explicit.
+### PAC Request Policy (ENT Tier3)
+ENT Tier3 profiles can use trusted PAC scripts for request-aware policy while preserving standard PAC routing. Configure PAC through the standard `--proxy-pac-url` flag and keep the PAC source explicit.
 
 <a id="flag-proxy-pac-url"></a>
 
@@ -255,22 +255,9 @@ ENT Tier3 profiles can use trusted PAC scripts for request callback workflows wh
 --proxy-pac-url=http://127.0.0.1:8080/proxy.pac
 ```
 
-Standard `FindProxyForURL(url, host)` behavior remains available for normal routing. Approved profiles and trusted PAC sources can also define BotBrowser's request callback:
+Standard `FindProxyForURL(url, host)` behavior remains available for normal routing.
 
-```javascript
-function BotBrowserFindProxyForRequest(url, host, method, headersB64, bodyB64, bodyState) {
-  return "CONTINUE";
-}
-```
-
-Supported callback results:
-
-- Continue or stop: `CONTINUE`, `BLOCK`
-- Capture: `CAPTURE`, `CAPTURE_TAG <tag>`, `CAPTURE_FILE <path>`
-- Synthetic response: `RESPONSE <raw_http_response_b64>`, `RESPONSE_FILE <path>`
-- Standard PAC route: `DIRECT`, `PROXY`, `HTTPS`, `SOCKS`, `SOCKS4`, `SOCKS5`
-
-PAC and callback routes can include credentials, for example `SOCKS5 user:pass@proxy.example.com:1080`. Capture records are written only when `CAPTURE` and `CAPTURE_FILE <path>` are returned together. Synthetic responses are limited to approved `file:` and `data:` PAC sources and fail closed when response input is invalid. See [PAC Request Policy](docs/guides/network/PAC_REQUEST_POLICY.md).
+The enterprise policy can apply approved request-aware routing and handling while standard PAC behavior remains available. Controlled response policy is limited to approved `file:` and `data:` PAC sources. See [PAC Request Policy](docs/guides/network/PAC_REQUEST_POLICY.md) for source requirements and deployment guidance.
 
 Use this when request-aware policy should stay in PAC routing instead of CDP-level request interception, especially for workflows that need help preserving HTTP/2 connection and stream continuity while directing selected requests to different routes.
 

docs/guides/deployment/PERFORMANCE_OPTIMIZATION.md

@@ -65,27 +65,18 @@ BotBrowser performance is influenced by several factors:
 
 BotBrowser ships two builds. **Standard Build** is the default public release and stays the right choice for long-running, interactive workflows. **Trimmed Build** is an ENT Tier3 distribution tuned for short-session, high-concurrency automation. Both share the same fingerprint protection model, profile format, CLI flag surface, and CDP commands; you do not change automation code when you switch.
 
-The Linux x64 benchmark (400 official samples, `1..20 contexts × 10 repeats × 2 builds`) shows Trimmed Build versus Standard Build:
-
-| Dimension | Trimmed delta | What it drives |
-|---|---:|---|
-| Wall time | **-61.85%** mean, **-67.79%** p95 | Total throughput per shift |
-| Per-context creation | **-85.32%** mean, **-87.51%** p95 | How fast a fleet can rotate contexts |
-| Per-context first nav | **-38.71%** mean | Time to first useful work in each context |
-| CPU peak | **-67.81%** mean | How many concurrent contexts a host can sustain |
-| PSS peak | **-31.25%** mean | Shared memory headroom under bursty load |
-| Success rate | unchanged at 100% | Stability and cleanup are not regressed |
+BotBrowser release testing compares Trimmed Build with Standard Build on context startup, first navigation, CPU load, and shared memory use. Trimmed Build reduces resource pressure for short-session workloads while retaining the same profile and automation interfaces.
 
 Choose Trimmed Build when at least one of the following is true:
 
-- **Context spin-up dominates wall time.** Short-session privacy testing, single-page consistency checks, and high-rotation per-context fleets. The `-85%` creation delta is the headline.
+- **Context spin-up dominates wall time.** Short-session privacy testing, single-page consistency checks, and high-rotation per-context fleets.
 - **CPU peak per context is the bottleneck.** Hosts already at high CPU utilization recover headroom directly.
-- **Shared memory (PSS/USS) is the binding constraint.** Memory-pressured hosts see `-31%` to `-38%` peak headroom returned.
+- **Shared memory is the binding constraint.** Memory-pressured hosts can recover headroom by using fewer browser processes.
 - **Workloads rotate through many identities per hour.** Each context lives seconds to minutes before the next identity takes over.
 
 Stay on Standard Build when sessions are long-running and interactive, when the workload exercises the full browser feature surface, or when the host has plenty of CPU and memory headroom and per-context spin-up is not the bottleneck.
 
-Trimmed Build is not on the public [Releases](https://github.com/botswin/BotBrowser/releases) page; it ships through the enterprise distribution channel. Product overview, engineering design, and FAQ: [TRIMMED_BUILD.md](../../../TRIMMED_BUILD.md). Full benchmark table and per-context matrix: [BENCHMARK.md#trimmed-build](../../../BENCHMARK.md#trimmed-build). Access: [Enterprise](https://botbrowser.io/enterprise/) or [Pricing](https://botbrowser.io/pricing/).
+Trimmed Build ships through the enterprise distribution channel. Product overview and compatibility notes: [TRIMMED_BUILD.md](../../../TRIMMED_BUILD.md). Access: [Enterprise](https://botbrowser.io/enterprise/) or [Pricing](https://botbrowser.io/pricing/).
 
 ---
 
@@ -149,7 +140,7 @@ chromium-browser \
     --user-data-dir="$(mktemp -d)"
 ```
 
-`1:30` means video frames visually update near 1 FPS while media reporting uses 30 FPS. Pixel output follows the actual cadence, so choose a higher actual value when the workload samples video pixels frame by frame. For Per-Context Fingerprint, pass the flag in `botbrowserFlags` before creating pages in the context. See the [Video FPS benchmark](../../../BENCHMARK.md#video-fps-control).
+`1:30` means video frames visually update near 1 FPS while media reporting uses 30 FPS. Pixel output follows the actual cadence, so choose a higher actual value when the workload samples video pixels frame by frame. For Per-Context Fingerprint, pass the flag in `botbrowserFlags` before creating pages in the context.
 
 ### Reuse browser instances with multiple contexts
 

docs/guides/fingerprint/CANVAS.md

@@ -67,7 +67,7 @@ When a profile is loaded, BotBrowser uses its built-in font libraries and render
 
 ### Canvas Color Spaces
 
-Chrome 150 keeps Canvas 2D protection active for standard and wide-gamut canvas color spaces, including `display-p3`. Color-space selection follows the page request while profile-backed replay and deterministic protection remain consistent with the session.
+BotBrowser 150.0.7871.46 keeps Canvas 2D protection active for standard and wide-gamut canvas color spaces, including `display-p3`. Color-space selection follows the page request while profile-backed protection remains consistent with the session.
 
 ---
 
@@ -83,11 +83,7 @@ BotBrowser applies deterministic noise to all Canvas 2D output at the rendering
 
 ## Effect Verification
 
-To verify protection is active:
-
-1. Launch BotBrowser with a profile and visit a fingerprint testing site such as [BrowserLeaks](https://browserleaks.com/) or [CreepJS](https://abrahamjuliot.github.io/creepjs/).
-2. Confirm that the reported Canvas hash and image data match the profile configuration, not the host machine.
-3. To verify reproducibility, launch two sessions with the same `--bot-noise-seed` and confirm that the Canvas fingerprint output is identical.
+For a defensive consistency check, compare separate sessions that use the same BotBrowser build, profile, color-space policy, and noise seed. Repeat the authorized visual workflow on each supported host platform and review unexpected output differences before deployment.
 
 ---
 

docs/guides/fingerprint/FONT.md

@@ -91,7 +91,7 @@ BotBrowser addresses cross-platform font consistency through built-in font libra
 
 ### FontFace and Fallback Behavior
 
-Chrome 150 improves profile-backed font handling for `FontFace` local sources, request-by-name loading, and multilingual fallback. Windows-target profiles also keep their font renderer preferences with the active BrowserContext, including per-context sessions running on another host platform.
+BotBrowser 150.0.7871.46 improves profile-backed font handling for local font sources, request-by-name loading, and multilingual fallback. Windows-target profiles also keep their font renderer preferences with the active BrowserContext, including per-context sessions running on another host platform.
 
 Keep `--bot-config-fonts=profile` when the profile font inventory and fallback policy should remain authoritative. Use `expand` only when the workflow intentionally allows host fallback beyond the profile bundle.
 
@@ -101,11 +101,7 @@ Keep `--bot-config-fonts=profile` when the profile font inventory and fallback p
 
 ## Effect Verification
 
-To verify protection is active:
-
-1. Launch BotBrowser with a profile and visit a fingerprint testing site such as [BrowserLeaks](https://browserleaks.com/) or [CreepJS](https://abrahamjuliot.github.io/creepjs/).
-2. Confirm that the reported font list and text metrics match the profile configuration, not the host machine.
-3. To verify reproducibility, launch two sessions with the same `--bot-noise-seed` and confirm that the font measurement output is identical.
+For a defensive consistency check, compare separate sessions that use the same BotBrowser build, profile, locale, and noise seed. Repeat the authorized workflow on each supported host platform and record any visible layout differences.
 
 ---
 
@@ -117,7 +113,7 @@ To verify protection is active:
 |---------|----------|
 | Font list shows host system fonts | Ensure `--bot-config-fonts=profile` is set. The `real` mode disables font protection. |
 | CJK text renders with missing glyphs | Verify the profile includes appropriate CJK fonts. Windows and macOS profiles include CJK support by default. |
-| A local FontFace name resolves differently across hosts | Use `--bot-config-fonts=profile` and a Chrome 150 profile package so local and request-by-name font handling follows the profile inventory. |
+| A local font name resolves differently across hosts | Use `--bot-config-fonts=profile` and a matching BotBrowser 150.0.7871.46 profile package so local and request-by-name font handling follows the profile inventory. |
 | Font metrics differ between headless and headful mode | Both modes should produce identical metrics with a profile loaded. Check that the same profile and flags are used. |
 | ClientRects values vary between sessions | Use `--bot-noise-seed` for reproducible measurements. Without a fixed seed, noise varies per session. |
 

docs/guides/fingerprint/PERMISSIONS.md

@@ -33,7 +33,7 @@ Permission state follows the loaded profile together with the browser's normal s
 
 Browser permission results are visible through web APIs, page capability checks, workers, and browser UI decisions. BotBrowser keeps these paths aligned with the selected browser and platform profile family.
 
-Chrome 150 improves profile-backed permission mapping for launch profiles and per-context profiles. Permission queries and browser-side checks follow the active BrowserContext.
+BotBrowser 150.0.7871.46 improves profile-backed permission mapping for launch profiles and per-context profiles. Permission queries and browser-side checks follow the active BrowserContext.
 
 For Per-Context Fingerprint, set the profile before creating the first page:
 

docs/guides/fingerprint/STORAGE_QUOTA.md

@@ -42,13 +42,12 @@ The default policy is `profile`: BotBrowser uses the active profile for storage
 --bot-js-heap-size-limit=real
 --bot-storage-quota=real
 
-# Set explicit byte values
---bot-js-heap-size-limit=4294967296
---bot-storage-quota=10737418240
 ```
 
 `--bot-js-heap-size-limit` is applied to newly started sessions or contexts. Start a new browser session or create a fresh context when changing this value. `--bot-storage-quota` can be used at launch and in per-context flag workflows.
 
+Approved enterprise profiles can also use explicit values supplied through managed deployment policy. Keep storage quota, JavaScript heap, and device memory settings aligned with the selected profile family. Contact enterprise support for profile-specific configuration.
+
 ---
 
 <a id="what-botbrowser-controls"></a>
@@ -98,11 +97,7 @@ await page.goto("https://example.com");
 await browser.close();
 ```
 
-To verify storage and memory protection is active:
-
-1. Launch BotBrowser with a profile and visit a fingerprint testing site such as [BrowserLeaks](https://browserleaks.com/) or [CreepJS](https://abrahamjuliot.github.io/creepjs/).
-2. Confirm that the reported storage quota and device memory values match the profile configuration, not the host machine.
-3. Launch a second session with the same profile and confirm identical values are reported.
+For a defensive consistency check, launch separate sessions with the same build, profile, proxy policy, and runtime settings. Compare the user-visible behavior recorded by your authorized test workflow. Repeat on each supported host platform before deployment.
 
 ---