Privacy

This page describes what the Databricks Field Guide collects and why. It is short because the site does little: it is a manual, there is nothing to sign up for, and nothing here is sold or shared onward.

What is measured

We measure which chapters get read, in what order, and roughly where the reader is. That is the whole purpose: a manual is only worth maintaining if we can tell which parts of it are doing work, and which chapters people give up on.

Specifically, each page view records:

• the chapter, and the part of the manual it belongs to
• the page you came from, if you followed a link
• country, region and city, derived from your network address
• the organisation that operates your network, as your internet provider publishes it — which on a corporate network is usually the employer
• the organisation a visit is attributed to, worked out by Factors from your network address

The last is company-level, not personal. They tell us that someone at a given organisation read a chapter. They do not tell us who, and we make no attempt to find out.

The cookie

One first-party cookie, set by PostHog, our analytics processor. It stores a random identifier and nothing else. Its only job is to recognise that two visits a fortnight apart came from the same browser, which is what separates twenty readers from one reader who came back twenty times.

There is no consent banner, and that is a deliberate position rather than an oversight. The cookie carries no advertising identity, follows you to no other site, and the data it produces is neither sold nor shared. That is the shape regulators describe as audience measurement rather than tracking. We would rather disclose it here, in language you can read, than interrupt a manual with a dialogue box.

Turning it off

Set Do Not Track in your browser. We check the signal before the analytics library is loaded, not merely before events are sent — so with it on, nothing loads, no cookie is set, and no request is made. Blocking /ingest or clearing site data has the same effect.

Who processes it

• PostHog — analytics. Events reach it through this domain rather than directly, which is a blocklist and content-security measure rather than a way to obscure the destination.
• Cloudflare — hosting. Serves every page and supplies the country and network above.
• Factors — works out which organisation a visit came from. It is the one third party whose script runs in your browser, and it sets storage of its own. Blocking third-party scripts stops it, and Do Not Track stops it before it loads.

Getting in touch

For anything about this page, or to ask what we hold, write to privacy@techfabric.com. TechFabric's full privacy policy, which governs techfabric.com and everything you send us there, is at techfabric.com/privacy-policy.