Where the security score comes from
Eight channels, each asking one question of the published record and reading a named set of fields to answer it. They multiply rather than add — the factor beside a channel is what is left after the pressure it found, and open a channel to see every field it read, as it is stored. How the model works
Security fields
67 55 of them feed a channel
Established
32 33 left unknown, 2 not applicable
Completeness
50% the share the model could weigh
Citations
52 across 18 documents
Every value carries what it rests on, and the model weighs the four levels differently. Weight, then how many citations on this record sit at that level:
B weighs 0.85 · 49 hereC weighs 0.70 · 1 hereD weighs 0.35 · 2 here
The weights are methodology.json’s own; a claim seen in the artefact itself counts for more than the same claim reported second-hand. The date at the end of a row is the day that value was last read.
A channel does not price every field it reads. The ones it did are marked along their edge and carry what they added; everything else was read and cost nothing. Only a channel that composes field by field can mark a field at all — the rest price themselves by the parameters printed above their rows.
Still open on this record.
No independent audit. No no-logs audit, pentest, or third-party security review of any kind is referenced anywhere on GOOSE VPN's own site, so the entire verification block (V01-V15) is unknown. Everything about retention rests on the provider's own word, at whatever credence a privacy policy and a support article carry on their own.
The no-log claim carries its own exception. The privacy policy describes no caching of VPN session data, but GOOSE VPN's own FAQ says that if "a public body suspects a GOOSE VPN user from criminal activities" it "can keep a log on this specific user" — a targeted logging capability that sits beside a page on the same site calling the policy "100%" no-log. The two statements do not agree.
Ownership and jurisdiction facts are thin. No ultimate beneficial owner, no group affiliation beyond "independent," and no launch year could be established from the provider's own pages or a Wayback Machine check; a Dutch Chamber of Commerce lookup that could resolve incorporation date and ownership was not accessible in this session.
On the record as a whole.
GOOSE VPN (GOOSE B.V., Rijswijk/Rotterdam, Netherlands) is a small, independently run Dutch VPN. Pricing is EUR-only; USD figures here are converted at the rate Mullvad's own pricing page publishes (€1 = $1.16 on 2026-09-13), same convention used elsewhere in this catalogue for EUR-only providers.
The protocol list (PPTP, L2TP, OpenVPN, IKEv2) is the whole offer across every platform page checked; no WireGuard. An older support article quotes a €12.99/mo unlimited plan that disagrees with the live pricing page's €9.99/mo one-month plan — the live pricing page was treated as authoritative.
JurisdictionCan someone compel what exists, without the provider getting a say?5 fields read · 3 left unknown · 76.0 points of pressure×0.240
Where the company sits 0.6, where its owner sits 0.03, the exits it offers 0.35, the gag-order regime 0.05.
Computed
×0.032 of a clean record completeness 50%
Where the drop comes from: Jurisdiction. It is the channel this record's risk is concentrated in — on its own it takes a clean record to ×0.240, and its bar above is filled to that.
Exposure is recorded as low and the integrity status as unexamined.
Against the rest of the register, this record sits furthest above on Integrity — ×0.783 where the register averages ×0.658 — and furthest below on Jurisdiction, ×0.240 against ×0.680.
Every row above is one field of the published record, and every one of them can be challenged: every row carries Report, or raise something about the record as a whole. A correction with a source behind it is made the same day, and if it moves the score it moves the rank.
