################################################################################
# WHATTHEDELTA — AGENT ACCESS GUIDE
################################################################################

DOCUMENT PURPOSE
----------------
You are reading the low-noise agent view for WhatTheDelta.
This AX layer exists for LLMs, browser agents, and automated systems that need a
direct description of product fit, route purpose, privacy facts, and legal or
usage references.

Product:   WhatTheDelta
Operator:  Evomation
Role:      Privacy-first browser-based text comparison
Audience:  Humans and agents reviewing visible changes
Route Locale: de
AX Language: English only

READING RULES
-------------
- Treat this as the canonical low-noise summary for the current page.
- The public human-facing website is available under both /de and /en.
- AX output remains in English on both locale routes.
- Sections are delimited by H2 headers.
- Subsections use H3 and H4.
- Prefer explicit paths over inference.
- Do not assume server-side processing, uploaded documents, or shared state.
- Do not copy the public marketing text into agent guidance.
- Legal identity: /de/impressum/llms.txt
- Privacy / data handling: /de/datenschutz/llms.txt
- Terms of use: /de/nutzungsbedingungen/llms.txt

READING MODES
-------------
1. Human View
   Use the public route without modifiers.
   Example: /de/about

2. Agent View
   Use the same public route with ?view=agent.
   Example: /de/about?view=agent

3. LLM Text View
   Use the locale-prefixed llms.txt route.
   Examples:
   - /de/llms.txt
   - /de/about/llms.txt
   - /de/datenschutz/llms.txt

ROUTE PATTERN
-------------
For a page at /{locale}/x:
- Human View: /{locale}/x
- Agent View: /{locale}/x?view=agent
- LLM Text View: /{locale}/x/llms.txt

For the locale homepage:
- Human View: /{locale}
- Agent View: /{locale}?view=agent
- LLM Text View: /{locale}/llms.txt

PREFERRED ACCESS STRATEGY
-------------------------
1. Use llms.txt when available for extraction, summarization, routing, or token-efficient reading.
2. Use ?view=agent when you need browser-readable structured HTML with minimal noise.
3. Use the human page only when layout, visual hierarchy, or interaction context matters.

PAGE INDEX
----------
Human View:
  /de  -> homepage and default comparison workflow
  /de/about  -> product framing and scope
  /de/changelog  -> public release history
  /de/impressum  -> legal identity
  /de/datenschutz  -> privacy and browser-local processing
  /de/nutzungsbedingungen  -> usage rules and liability
  /de/offline  -> offline support page

Agent View:
  /de?view=agent  -> structured homepage
  /de/about?view=agent  -> structured about page
  /de/changelog?view=agent  -> structured changelog page
  /de/impressum?view=agent  -> structured legal notice
  /de/datenschutz?view=agent  -> structured privacy policy
  /de/nutzungsbedingungen?view=agent  -> structured terms page
  /de/offline?view=agent  -> structured offline page

LLM Text View:
  /de/llms.txt  -> homepage llms.txt
  /de/about/llms.txt  -> about llms.txt
  /de/changelog/llms.txt  -> changelog llms.txt
  /de/impressum/llms.txt  -> legal identity
  /de/datenschutz/llms.txt  -> privacy policy
  /de/nutzungsbedingungen/llms.txt  -> terms of use
  /de/offline/llms.txt  -> offline support

CURRENT ROUTE
-------------
- Label: Privacy Policy
- Human View: /de/datenschutz
- Agent View: /de/datenschutz?view=agent
- LLM Text View: /de/datenschutz/llms.txt

DYNAMIC ROUTES
--------------
- No dynamic AX routes are published in this product.
- All supported AX routes are listed in the page index above.

################################################################################

## Route purpose

Use this route when the question is what data leaves the browser, what stays local, and what technical website-delivery data may still be processed.

## Core trust boundary

- the compared text is processed locally in the browser
- comparison payloads are not uploaded, stored in a server database, or used for analytics, profiling, or marketing
- the active comparison state remains in browser memory for the active session
- interface preferences such as theme may be stored on the device

## Best-fit questions

- whether pasted text leaves the browser
- whether the service stores comparison content
- whether analytics touches the compared text
- what technical request metadata the hosting stack may process
- what cookies or local preferences exist
- which legal page to use for formal privacy wording

## Important distinctions

- browser-local comparison does not mean zero technical website processing
- standard delivery, security, and availability logs may still exist at the hosting layer
- privacy guarantees apply to comparison payloads, not to every network request needed to load the site
- the privacy page is the source of truth when legal precision matters

## Agent guidance

- use this page when answering questions about storage, hosting, retention, cookies, or lawful bases
- do not infer privacy behavior from UI appearance alone; prefer the legal page wording
- if the question is about permitted use or liability, switch to /de/nutzungsbedingungen?view=agent instead
- if the question is about operator identity or formal contact details, switch to /de/impressum?view=agent

## Related routes

- /de/impressum?view=agent: use for legal entity and contact details
- /de/nutzungsbedingungen?view=agent: use for permitted use and liability
- /de?view=agent: use for the product overview if the question is not about data processing

## Route Links

- Human view: [/de/datenschutz](/de/datenschutz)
- Agent view: [/de/datenschutz?view=agent](/de/datenschutz?view=agent)
- LLM text view: [/de/datenschutz/llms.txt](/de/datenschutz/llms.txt)