Skip to content

Page

Privacy policy

Privacy policy helps readers navigate Gautier Dorval’s corpus, services, evidence layers and interpretive governance resources.

CollectionPage
TypeInstitutional

Governance artifacts

Governance files brought into scope by this page

This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.

  1. 01Canonical AI entrypoint
  2. 02Public AI manifest
  3. 03Definitions canon
Entrypoint#01

Canonical AI entrypoint

/.well-known/ai-governance.json

Neutral entrypoint that declares the governance map, precedence chain, and the surfaces to read first.

Governs
Access order across surfaces and initial precedence.
Bounds
Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Entrypoint#02

Public AI manifest

/ai-manifest.json

Structured inventory of the surfaces, registries, and modules that extend the canonical entrypoint.

Governs
Access order across surfaces and initial precedence.
Bounds
Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Canon and identity#03

Definitions canon

/canon.md

Canonical surface that fixes identity, roles, negations, and divergence rules.

Governs
Public identity, roles, and attributes that must not drift.
Bounds
Extrapolations, entity collisions, and abusive requalification.

Does not guarantee: A canonical surface reduces ambiguity; it does not guarantee faithful restitution on its own.

Scope

This page describes the limited handling of data on gautierdorval.com. The site is primarily a public editorial corpus. It does not provide public comments, user accounts, or a member area.

Technical browsing data

As with any website, hosting and delivery layers may process technical data required to operate the service, such as IP address, browser type, request date and time, requested page, and certain network information. These elements are used for normal operation, security, and page delivery.

Display preference

The light or dark theme toggle stores a local browser preference named gd-theme. This preference remains on the visitor’s device and is used only to remember the display mode.

The search feature relies on a static index loaded in the browser. Search processing happens client-side against the published corpus.

Contact

When a message is sent to the contact address published on the site, the information provided voluntarily — for example name, email address, and message content — is used only to read, process, and reply to the request.

Audience measurement

The site uses Google Analytics (identifier G-ENNJL9FR8D) to measure page visits. This service collects aggregated browsing data (pages viewed, session duration, approximate geographic origin, device type). This data is used exclusively to understand usage of the published corpus and to inform editorial decisions. No advertising profile is built from this data. Google Analytics is operated by Google LLC, which applies its own privacy policy.

External services

Fonts are served locally from the site domain. Links to third-party platforms may be present in the content. Those services apply their own privacy policies.

What the site does not do

At this time, the site does not use an internal public commenting system, user accounts, public editorial login, an integrated newsletter, or application-level advertising tracking. The only application-level persistence identified in the public front-end for user preference is the local storage of the display theme.

Privacy requests

For any question about this page, or for a request related to information voluntarily sent by email, write to info [at] pagup.com.

Data minimization principle

The site is designed as a public knowledge corpus, not as an account-based application. The editorial layer is available without login, profile creation, payment flow, comment submission, or private workspace. This limits the categories of information intentionally requested from visitors.

The main voluntary data path is email contact. When a message is sent to the published contact address, the information transmitted is used to understand and respond to that message. The site does not require visitors to provide personal information in order to read the corpus.

Search and reading behavior

Internal search is intended to help readers navigate published material. The static search index exposes public content for client-side lookup. It is not designed as a private query system, a behavioral profiling system, or a personal knowledge base.

The site may still generate technical access logs through hosting, security, and delivery infrastructure. Those logs are part of normal web operation. They may be used to preserve availability, diagnose errors, protect against abuse, and understand whether public pages can be delivered correctly.

Analytics limits

Audience measurement is used to understand how the public corpus is read at an aggregate level. The purpose is editorial and operational: identifying pages that are visited, understanding broad navigation patterns, and detecting whether certain sections are underused, confusing, or technically difficult to access.

Analytics should not be read as an interpretive authority layer. Visit data does not decide the canonical status of a concept, the validity of a definition, the authority of a source, or the legitimacy of an AI-generated response. Those questions are governed by the published corpus and by the relevant governance artifacts, not by popularity metrics.

Email and professional exchanges

Messages sent by email may contain names, contact details, organizations, links, examples, screenshots, or descriptions of observed problems. These elements are used only in relation to the request. They should not be sent if they include unnecessary confidential information, sensitive data, regulated records, credentials, or internal documents that have not been cleared for external review.

If a request requires a deeper review, the scope, context, and appropriate handling conditions should be established before detailed materials are exchanged. Public email is not the right channel for unrestricted disclosure of sensitive corpora or operational logs.

The site links to external platforms, publications, repositories, tools, and documentation when they help readers understand the corpus or follow a reference. Leaving the site may expose the visitor to the privacy practices of those third-party environments. Those environments are not controlled by gautierdorval.com.

References to AI systems, search engines, analytics tools, external repositories, or third-party services are provided for editorial or contextual purposes. They do not imply that those systems follow the site’s governance files, privacy choices, response conditions, or source hierarchy.

Updates to this page

This page may be updated when the site structure, contact process, analytics setup, or public corpus changes. A privacy page should be read as a description of current site operation, not as a guarantee that external systems, browsers, caches, search engines, or AI tools will interpret the site in a particular way.