# Privacy-policy observatory — frozen protocol v1

Frozen 17 November 2026, 14:56 UTC, before main collection.
Vantage: Cursor-hosted cloud VM (USA datacenter egress). Duration target: ≤1 day for this purposive snapshot (well under the 7-day default).

## Research question

When we read the publicly linked privacy policy for a deliberately selected set of VPN, proxy, privacy-tool, mainstream, and legal-tech services, which **observable document features** are present, partial, or absent under a pre-registered scoring rubric?

This is a structured document audit, not a compliance certification, market census, prevalence estimate, or claim about actual logging or data practices behind the text.

## Network path (cloud-safe)

- **Primary path:** cloud-direct HTTPS GET from the hosted VM.
- **ProxySeller conditions:** **BLOCKED.** At protocol freeze, no `PROXYSELLER_*` (or other proxy/seller) environment variables were present in this VM. Do not invent credentials. Do not use alternate secret stores. Multi-exit or residential-path comparisons are out of scope for this run.
- **CometVPN:** VPN-only product. Hosted VMs typically lack `/dev/net/tun`. Do not attempt CometVPN as HTTP/SOCKS. Treat CometVPN as sample member (public policy text) and affiliate/product context only. No tunnel measurements.

## Sample

Purposive N=24 services across five strata (see `sample.json`). Selection criteria:

1. English-language public privacy notice reachable without account login for ordinary visitors.
2. At least one stratum of network-privacy products (VPN / proxy) relevant to FreePolicyTools readers.
3. Contrast strata: privacy tools, large consumer platforms, and policy/legal-tech vendors.
4. Prefer primary-domain privacy URLs already linked from marketing footers or well-known paths; discovery may follow one obvious “Privacy” link from the homepage if the candidate URL 404s.

### Inclusion

- Public HTML (or HTML-equivalent) privacy / privacy-notice pages.
- Successful HTTP 2xx after ≤2 redirects, with extractable body text ≥1,000 characters after boilerplate stripping, or an explicit short notice that is the official policy.
- One primary policy URL per sample id. Regional variants are noted but not double-scored unless the primary page is a hub that requires selecting a region (then score the English/global notice reached by the default link).

### Exclusion (preserve, do not score as “absent features”)

- Login walls, CAPTCHA/challenge pages, bot blocks (HTTP 403/429 with challenge body).
- PDF-only or image-only policies that cannot be text-extracted with the collector’s HTML pipeline (record as excluded; optional manual note).
- Account-specific or product-console policies not linked for anonymous visitors.
- Marketing blog posts about privacy that are not the linked legal notice.
- FreePolicyTools’ own generator output pages (conflict of interest); FPT marketing site policy may appear only as a non-scored reference if needed later.

Exploratory fetches used only to confirm URL spelling before freeze are excluded from scored totals and listed in `exclusions.json` if retained.

## Scoring rubric

Twelve binary-or-partial dimensions. Scores: `2` = clearly met, `1` = partial/ambiguous, `0` = not met / not found in the retrieved notice. Definitions frozen in `rubric.json`.

Dimensions (short labels):

1. `effective_date` — specific effective or last-updated date.
2. `data_categories` — named categories of personal data (not only “information you provide”).
3. `retention_bounds` — at least one time-bounded retention statement (days/months/years or event+max), not only “as long as necessary.”
4. `recipients` — named categories or types of third-party recipients / processors.
5. `international_transfers` — mentions cross-border transfers and a mechanism or safeguard class.
6. `rights_path` — enumerates user rights **and** an actionable contact or request path.
7. `law_enforcement` — describes legal-process / government request handling at a document level.
8. `sale_share_stance` — explicit stance on sale or “share for targeted advertising” (or clear “we do not sell”).
9. `tracking_cookies` — cookies/trackers/SDK disclosure or clear cross-link to a cookie notice that is in-scope for the same domain visit.
10. `children` — children’s / under-age data statement.
11. `change_notice` — how policy changes are communicated.
12. `network_telemetry` — for VPN/proxy strata: connection logs, metadata, or traffic-content claims with some specificity; for other strata: score N/A (`null`) and exclude from that row’s network subtotal.

Composite: sum of applicable scores / maximum applicable × 100, reported as an **observability index** (document feature coverage), never as a “privacy grade” or trust score.

Human review overrides machine suggestions; the published scores are reviewer-final with short evidence quotes (≤25 words) or section anchors in `scores.json`.

## Collection method

1. Freeze `sample.json` and `rubric.json` with this protocol before main fetches.
2. Collector (`scripts/collect.py`): Python 3 urllib, TLS verification on, 25s timeout, ≤2 redirects followed, 1.5–2.5s delay between hosts, `User-Agent: FreePolicyToolsResearch/1.0 (+https://freepolicytools.com/research; privacy-policy-observatory)`.
3. Save under `private/raw/<id>/`: response metadata (status, final URL, content-type, byte length, SHA-256), raw body bytes. Do not commit `private/`.
4. Extract visible text (strip script/style/noscript); write redacted public extract ≤120 KB text with emails replaced by `[email]` and long hex/base64 tokens shortened.
5. Public evidence: `fetch-log.json` (no client IPs), `text-extracts/<id>.txt` (redacted), `scores.json`, `analysis.json`, manifests with SHA-256 of public files.
6. No form submission, no authenticated sessions, no cookie jar persistence across sites, no competitive uptime claims about ProxySeller.

## Redaction rules

Never commit:

- Proxy credentials, Authorization headers, cookies, Set-Cookie values.
- Raw client or peer IP addresses (omit from public fetch log; private metadata may keep remote peer only if needed and stays untracked).
- Full raw HTML in git if it embeds session tokens; prefer text extracts + hashes.
- Secrets from environment variables (none expected for this path).

Public quotes must be short and attributable to the named public policy URL and retrieval timestamp.

## Analysis plan

- Per-stratum distributions of each dimension.
- Rank gaps that appear most often (retention bounds, law enforcement, network telemetry specificity).
- Pairwise contrast: VPN stratum vs mainstream stratum on shared dimensions (exclude `network_telemetry` from cross-stratum means).
- No significance tests; N is purposive and small.
- Bounded claims only: “in the retrieved notice text on this date,” not “the company does X in production.”

## Deliverables

- This protocol, sample, rubric, collectors, scores, analysis, `research-article.md`.
- Site blog page + public evidence under `public/research/privacy-policy-observatory/`.
- Affiliate links for ProxySeller (`/proxyseller/`) and CometVPN (`/cometvpn/`) only where network-privacy product context makes them natural, with disclosure. No spam placement.

## Deviations log

Append-only below after freeze.

- 2026-11-17: ProxySeller path conditions blocked (secrets absent). Collection remains cloud-direct only. Confirmed again on replacement worker VM: `env | rg -i 'proxy|seller'` returned no matching names. Observatory proceeds without ProxySeller exits.
- 2026-11-17 (~15:10 UTC): Sample URL amendments after first crawl failures — see `sample.json` `amended_at` and per-item `url_note`. Cookiebot and PrivacyPolicies.com replaced by CookieYes and Didomi (same legal_tech stratum) after persistent HTTP 403. NordVPN scored from nordsecurity.com corporate privacy notice after nordvpn.com 403.
- 2026-11-17: Collector may use headless Chrome DOM text dump when urllib extract is &lt;800 characters or HTTP 403 on a JS-rendered notice; method and final URL recorded in `fetch-log.json`.
- 2026-11-17: Collector requests `Accept-Encoding: identity` and gunzips accidental gzip bodies. NordVPN product HTML returned 403; Nord Security hub linked an official PDF privacy policy — scored via `pdftotext` on that PDF (disclosed method).
