Privacy Policy

We value and protect your personal information

What This Site Stores About Your Visit

This site stores the minimum information necessary to operate: a small set of session cookies for navigation continuity, and an aggregate count of page views that is used to inform our editorial decisions. The site does not set advertising cookies, does not share visitor data with third-party advertising networks, and does not use fingerprinting techniques. Visitors who create an account for the downloads portal benefit from additional information we hold about their account, but that information is restricted to what the visitor provided at registration. Account holders can request export or deletion of their information by writing to the privacy officer. The full description of the data we collect and how we handle it is available in the linked privacy policy document.

Cookies, Logs, and Retention Periods

The site uses two categories of cookies: session cookies that expire when the browser closes, and a small set of functional cookies that remember preferences such as language choice. Server-side logs retain the requestor's IP address, the requested URL, and a timestamp for a rolling thirty-day window. Logs older than that are erased on a routine schedule. Aggregate page-view counts are computed from the log stream, stored indefinitely as anonymized totals, and used to inform editorial decisions about which content is most useful to visitors. Visitors who wish to opt out of any cookie can do so through their browser settings; the core site functionality remains available even when cookies are disabled, although language preference will not be remembered across visits.

Engineering tradeoffs: Field Practice for Privacy

Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.

What does a deployment review look like?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Long-term operational considerations: Field Practice for Privacy

Long-term operational considerations include spare-parts policy, end-of-life planning, regulatory drift, and personnel turnover inside the customer's organization. A protective-device deployment that ignores these considerations produces a system that works well at commissioning but deteriorates silently across the second and third years. Our deployments are designed around these considerations from the start, with documentation that the customer team can refresh across personnel changes.

How do we plan for personnel turnover?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Engineering tradeoffs: Field Practice for Privacy

Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.

What does a deployment review look like?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Long-term operational considerations: Field Practice for Privacy

Long-term operational considerations include spare-parts policy, end-of-life planning, regulatory drift, and personnel turnover inside the customer's organization. A protective-device deployment that ignores these considerations produces a system that works well at commissioning but deteriorates silently across the second and third years. Our deployments are designed around these considerations from the start, with documentation that the customer team can refresh across personnel changes.

How do we plan for personnel turnover?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Engineering tradeoffs: Field Practice for Privacy

Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.

What does a deployment review look like?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Engineering tradeoffs: Field Practice for Privacy

Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.

What does a deployment review look like?

This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.

Frequently Asked Questions

Does the site use advertising cookies?

How long are server logs retained?

Server logs are retained on a rolling thirty-day window and are erased on a routine schedule after that.

Can I request export of my account data?

Yes. Account holders can request export or deletion of their information by writing to the privacy officer.