{
  "acceptance": "The delivered headers match the written storage policy and unauthorized requests cannot retrieve the report. The acceptance record names the tested route and proxy path; it does not generalize one result to all private pages.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "no-cache permits storage with revalidation; no-store is the directive for avoiding storage."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "no-store tells private and shared caches not to store the response."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "private permits storage only in a private cache."
    }
  ],
  "description": "Distinguish no-cache, no-store and private before changing the caching policy of an authenticated analytics page.",
  "diagram": [
    "no-cache: storage plus validation",
    "no-store: prohibit response storage",
    "private: private-cache storage only",
    "Access control: test independently"
  ],
  "draft_hash": "83e7c4ccd2661488adda94fa7d06e7fa558b06941b8599c8e91d6e0f1d7d861f",
  "evidence": {
    "observed_at": "2026-11-03T21:45:34.240059+00:00",
    "period": {
      "end": "2026-11-03T21:45:34.240059+00:00",
      "start": "2026-11-03T21:45:34.240059+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "comparison",
  "figure_notes": [
    "Storage is allowed; reuse requires revalidation.",
    "Caches should not store the response.",
    "Shared-cache storage is excluded by this directive.",
    "Cache directives do not implement authentication."
  ],
  "figure_title": "Choose cache rules for private analytics reports",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "cache-control-private-analytics-reports",
  "interpretation": "The names of cache directives can be misleading. MDN states that no-cache permits storage but requires validation before reuse. no-store instructs caches not to store the response, while private restricts storage to a private cache. These are different policies. Define whether the report may be stored at all, whether shared storage is acceptable, and how freshness should be checked before selecting directives. Authentication and authorization still need their own working controls.",
  "keyword_volume": "Not obtained",
  "limits": "Cache configuration alone cannot prove that previously stored copies have been removed. No legal compliance conclusion or data exposure finding is made from headers alone.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/cache-control-private-analytics-reports/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "An authenticated analytics report uses a cache directive whose behavior does not match its intended confidentiality and freshness requirements.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T11:55:09.117718+00:00",
  "reader": "Site owners and analysts investigating an authenticated analytics report uses a cache directive whose behavior does not match its intended confidentiality and freshness requirements.",
  "related": [
    "privacy-safe-analytics-paths"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/privacy-safe-analytics-paths/",
      "title": "Keep private URLs out of public analytics"
    }
  ],
  "research_document_ids": [
    "c138b6f556212d4911656b670d0c5c45"
  ],
  "slug": "cache-control-private-analytics-reports",
  "source_signature": "c1070f0d04858e1027478ed37b0017f74551c128fa6727317d23cd3dfabfda6b",
  "sources": [
    {
      "hash": "ccca5d8e28af3dcbc565e764b554acdf42093dbaaef6b49d9ddd886cfaeedc2e",
      "locator": "Response Directives / b32; Response Directives / b40; Response Directives / b41",
      "observed_at": "2026-11-03T21:45:34.240059+00:00",
      "title": "Cache-Control header",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cache-Control"
    }
  ],
  "sources_required": [],
  "steps": [
    "Inventory the report route, response headers and any CDN or reverse-proxy caching rule. Inspect an authenticated response without copying report contents or session credentials into public evidence.",
    "Write separate requirements for access, storage and freshness. A report being private does not make every cache safe, and a cache header does not implement authentication.",
    "Apply the narrow cache policy appropriate to the approved requirements. Check both the application response and the response actually delivered through the proxy.",
    "Use isolated authorized accounts to test access boundaries and inspect cache behavior. Stop if you cannot safely isolate test data. Retain header evidence and access results, not confidential report screenshots."
  ],
  "title": "Choose cache rules for private analytics reports",
  "worked_example": "Hypothetical example: an internal report uses no-cache because its owner believes that phrase means nothing will be saved. The documented behavior does not match that expectation. The first correction is to state the requirement precisely: whether the response must avoid storage, or whether browser storage with revalidation is acceptable. This is a technical policy review, not evidence that a particular report has leaked."
}