Privacy
OpenPWA is a static site: every page is built ahead of time and served from Cloudflare Pages. It has no accounts, no comments, no forms and no advertising. Cloudflare does change some pages on the way to your browser: it adds the Web Analytics beacon described below to the site’s HTML pages, and on pages that show the editorial email address it adds a small decoding script, described under Email address obfuscation.
What runs in your browser
Section titled “What runs in your browser”- No cookies. The site’s pages set none. The one exception is a test cookie in the device-test lab, set only when you press its button; see The demo app and the device-test lab.
- One analytics script: Cloudflare Web Analytics. The site is hosted on Cloudflare Pages with
Web Analytics turned on, so
Cloudflare adds its beacon script, loaded from
static.cloudflareinsights.com, to the site’s HTML pages. Details are in the next section. - One script that Cloudflare adds from openpwa.net:
email-decode.min.js. It runs only on pages that show the editorial email address. Details are under Email address obfuscation. - No other third-party scripts. No page loads advertising, social-media or other tracking code, and the site’s fonts are served from openpwa.net itself.
- Theme setting in
localStorage. The theme switch of Starlight, the documentation framework the site is built with, keeps its setting under the keystarlight-theme:light,dark, or an empty value for automatic, which is written on your first visit before you choose anything (ThemeSelect). - Sidebar state in
sessionStorage. Starlight also remembers which sidebar groups are open and how far the sidebar is scrolled, under the keysl-sidebar-state, for the current tab only (SidebarPersistState). Neither value is sent anywhere, and clearing site data removes both. - Search runs in your browser. The search box is Pagefind. When you first use it, it downloads its index and result snippets from openpwa.net as static files and matches your words locally: the words you type are not part of any request, although which index files are downloaded depends on them.
Cloudflare Web Analytics
Section titled “Cloudflare Web Analytics”The beacon measures page views and page-load performance in the browser, using the Performance API
for timing metrics and Core Web Vitals, and sends the result to openpwa.net/cdn-cgi/rum: for a site
proxied through Cloudflare, as this one is, the beacon reports to the site’s own domain rather than
to a Cloudflare domain
(data origin and collection).
Cloudflare’s documentation states what the editors see and what the script does not do:
- What the editors see. Visits and page views, page load time and Core Web Vitals, broken down by country, host, path, referring site, device type, browser, operating system and how the page was loaded (metrics, dimensions). The dashboard shows these as totals, not as a record of any one reader.
- No query strings. Web Analytics does not log the part of a URL after
?(FAQ). - No cookies, no local storage, no fingerprinting. Cloudflare says Web Analytics uses no
client-side state such as cookies or
localStorageto collect usage metrics, does not fingerprint individuals by IP address, User-Agent string or any other data, and does not track individual users across the sites that use it (product page, data collection). - Retention. Cloudflare keeps unsampled beacon data for 7 days and then aggregates it down to about 10 %; the dashboard shows the previous six months (FAQ).
The interactive demo app under /demo/ and the device-test harness of the Device Lab (the
test pages and apps themselves) are served with Cache-Control: no-transform, which stops Cloudflare
from adding the beacon to them, so those pages load no analytics at all
(FAQ). The Device Lab’s documentation pages
elsewhere under /lab/ are ordinary pages of the site and carry the same Web Analytics beacon
as every other page.
Email address obfuscation
Section titled “Email address obfuscation”Cloudflare’s Email Address Obfuscation
is switched on for openpwa.net, which is Cloudflare’s default. On every page that contains an
email address, such as Report a problem and every entry that ends with a
“Report a problem” link, Cloudflare rewrites the address in the HTML so that address
harvesters cannot read it, and adds the script email-decode.min.js, served from openpwa.net under
/cdn-cgi/scripts/, which restores the address in your browser. Cloudflare’s documentation
describes it as a small decode script that does not block page rendering.
The demo app and the device-test lab
Section titled “The demo app and the device-test lab”Two corners of the site are small installable test apps rather than pages, and they keep data in your browser because that is what they test. Nothing they store is sent to openpwa.net.
- /demo/ keeps its language choice in
localStorageand installs a service worker that caches the demo’s own files. Its push demo asks for notification permission; if you allow it, your browser creates a push subscription with its own push service, and the page shows it to you without sending it anywhere. - The device-test harness of the Device Lab is the set of test pages and apps used to
check behaviour on real devices. It is marked
noindexfor search engines and loads no analytics, as described above. The Device Lab’s documentation pages link to it from their run steps; the rest of the site links to those documentation pages, not to the harness. Its storage test, when you press its button, writes a marker tolocalStorage, IndexedDB and a cookie namedopenpwa_lab_marker, limited to the lab’s own path and kept for a year unless you clear it with the button next to it. Its notification tests record notification clicks in IndexedDB, and its push test can create a push subscription in the same way as the demo.
What the host sees
Section titled “What the host sees”The site is served by Cloudflare’s content delivery network. Like any web server, it receives the request line, your IP address and the headers your browser sends, and may keep standard access logs for operational purposes. OpenPWA does not add anything to those logs and does not use them to identify readers.
Mail to the editorial address is received through Cloudflare
Email Routing: the domain’s mail servers
(its MX records) are Cloudflare’s
route1, route2 and route3.mx.cloudflare.net, and Email Routing forwards the message to the
editors’ mailbox. Your address and your message are not published on the site, and reports are not credited
by name. See Report a problem.
Changes
Section titled “Changes”This page changes only when the site’s behaviour changes; such a change is recorded in the site changelog.