Privacy
This page describes the driga.dev website. The Driga app runs on your own
machines and sends no usage reports to LabStack; what it reads and stores is
described in Privacy and data.
Website analytics
Section titled “Website analytics”This build of the site has no analytics configured, so nothing is measured, nothing is stored, and there is nothing to turn off. The rest of this section describes what a build that has them does.
When it runs
Section titled “When it runs”- In the EEA, the UK, Guernsey, the Isle of Man and Jersey, the analytics tag is loaded and its identifier stored only after you allow analytics.
- Everywhere else, analytics run and the control above turns them off.
- If your browser sends Global Privacy Control, analytics do not run and you are not asked. Choosing Allow above overrides that signal for this browser.
Do Not Track is not consulted. Which rule applies is decided from the country Cloudflare reports for your connection; if that lookup fails, the site asks.
What is sent
Section titled “What is sent”When analytics are running, each page view sends the page path, the page title, the site you arrived from, and the coarse device, browser and country information any web request carries. Query strings are removed from the recorded address, and the referrer is reduced to its site.
Outbound clicks in the header, footer and landing page record the control, link text and destination URL. Copying the install command records that it was copied. Google Signals and ad personalisation are disabled and ad data redaction is enabled.
What is never sent
Section titled “What is never sent”The site does not send search terms or collect form input. It has no accounts, session recording or heatmaps.
Storage
Section titled “Storage”Your answer is kept in your browser’s local storage under
driga.analytics-consent.v1, which is read by this site and sent to nobody.
Allowing lets Google Analytics set its _ga cookies; declining afterwards
deletes them.
Hosting
Section titled “Hosting”The site is static files served by Cloudflare Pages. Like any web server, Cloudflare receives the IP address and request headers needed to deliver a page. That processing is Cloudflare’s, under their terms.
Contact
Section titled “Contact”Questions about this page belong in an issue. The site’s source, including the analytics code described here, is in the repository.