Last updated: 10 October 2026
encapsulated.network explains how VPNs and the technology around them work: protocols, encryption, leaks, features, VPN types, and the laws and intelligence alliances that shape online privacy. This page sets out how articles are researched, written, checked and kept up to date, how AI is used in that process, and how the site is funded. If anything published here falls short of these standards, I want to know (see Corrections and contact).
Who is responsible for the content
The site is run by Najib Dahech, who founded it in March 2026 and is its sole author and editor. I research, write, edit and approve every article, and I am accountable for every claim published here.
My background is in communication. I hold a National Bachelor’s Degree in Communication from IPSI Manouba (Institut de Presse et des Sciences de l’Information) in Tunisia. I am not a cryptographer or a penetration tester. My work is reading the primary documentation (protocol specifications, audit reports, legal texts and research papers) and explaining accurately what it says. More background is on the About page and on LinkedIn.
Independence and funding
encapsulated.network is self-funded and currently earns no revenue.
- The site does not use affiliate links and never will.
- It does not publish sponsored articles, paid placements or paid reviews.
- No VPN provider or other company pays for coverage, sees an article before publication, or has any say in what is published.
Display advertising may be added in future. If it is, ads will be clearly labelled and kept separate from article content, and advertisers will have no input into what is written. If the way the site is funded changes, this page will be updated first, with the date of the change.
No product recommendations
encapsulated.network does not review, score, rank or recommend VPN providers, and does not publish “best VPN” lists. Articles name specific providers only to show how a feature or protocol is implemented in practice, for example how one provider handles post-quantum key exchange or where a setting sits in an app. Naming a provider is not an endorsement. Where a provider makes a claim about itself, such as a no-log policy or an audit result, the article says whether that claim has been independently verified.
How topics are chosen
Each article answers a question readers bring to the subject: what a protocol is, why a leak happens, whether something is legal, how one type of VPN differs from another. Before writing, I check what the site’s existing articles already cover, so each new article answers its own question in depth instead of repeating another page. Coverage follows the subject, not trending topics.
Research and sourcing
Articles are built on primary sources wherever they exist:
- RFCs, protocol specifications and whitepapers
- official documentation, release notes and changelogs from software projects and vendors
- laws, court records, and publications from regulators and government agencies
- published independent audit reports
- peer-reviewed research
News coverage and other publications are used for context and identified as secondary. When two sources agree, I check whether one is simply citing the other before treating them as independent.
Every factual claim is logged when it enters a draft: the source URL, what was actually read (the full text or only a summary), the date it was read, and where in the source the claim appears. Tables, appendices and methodology sections are read, not only summaries, and figures are reported with what they are a share of (for example “24 of 281 apps”, not a bare percentage). Sources are linked in the text so readers can check them. If a source cannot be found or opened, the claim is not published.
Fact-checking
Every article goes through several fact-check passes before publication. Each pass runs separately and has one job, so no single check is relied on to catch everything:
- Existence and accuracy. Does every named law, product, organisation and event exist, and is what the article says about it correct?
- Attribution and quotations. Does each named source say exactly what the article attributes to it? Direct quotations are compared character by character with the original, and translations are marked as translations.
- Numbers, dates and recent developments. Every figure and date is tied to a source, and anything from roughly the last 18 months is re-checked against the live source rather than assumed.
A final review reads the article as a whole and checks that the summary, body, tables and FAQ agree with each other. Any correction made during this process is treated as a new claim and verified against its source in the same way.
These standards apply to every new article. Articles published before they were adopted in September 2026 are being brought up to the same standard as they are revised.
Hands-on testing
Some articles include my own tests, such as DNS and WebRTC leak tests or screenshots of settings inside VPN apps. Where they appear, the article says they come from my own testing. They show how something works on a particular device and app at a particular time. They are not product reviews.
How AI is used
AI tools are part of how this site is produced, and readers should know where. I use them to:
- organise research material I have gathered into an outline
- draft article text from that outline and the sources I have selected
- run the separate fact-check passes described above
- produce first versions of diagrams and featured images
AI tools do not choose topics, are never treated as a source, and do not publish anything. Their output is a draft. Every claim in it is checked against a primary source, every diagram is reviewed and corrected, and I edit and approve every article before it goes live. Because AI tools can state wrong information with confidence, the fact-checking process treats every claim as unconfirmed until a source confirms it.
Updates and dates
VPN technology, provider features and laws change often. Articles are revisited when something they describe changes, such as a protocol release, a new law, a provider removing a feature or a newly published audit. Statements likely to change are dated in the text (for example, “as of October 2026”).
Each article shows the date it was first published. An updated date is shown only when the content has changed substantively, such as corrected facts, new sections or revised conclusions. Adding a link or fixing a typo does not change it.
Corrections and contact
If you find a factual error, a broken source or a claim you think is unsupported, email [email protected] with the article and the passage. Every report is checked against the source. Confirmed errors are corrected, and where a correction changes the meaning of a claim, a short note is added at the end of the article stating what changed and when.