Learn: Terms of Use + Privacy Policy pages (versioned, linked from /learn, disclose Bedrock processing)

[OriNachum]

The consent gate (#10) needs actual documents to point at. This issue is the
Terms of Use and Privacy Policy for agentculture.org/learn — the content,
the hosted pages, and the versioning that the consent record pins to.

Deliverables

1. Privacy Policy page — what we collect, why, how long, who processes it,
   and the learner's rights.
2. Terms of Use page — the rules for using the learning service.
3. Both linked from /learn (footer + the Learn: explicit user consent before saving learner data (consent gate + right to delete) #10 consent notice) and versioned,
   so a change bumps the version and triggers re-consent (Learn: explicit user consent before saving learner data (consent gate + right to delete) #10).

Privacy Policy must disclose (matches what's actually built)

• Data collected: GitHub id + public display name (identity); the append-only
  learning ledger (activities, results, mastery, timestamps); a session cookie.
  No email, no password (existing invariant).
• Purpose: authenticate the learner, track cross-subject progress, personalize
  learning.
• Third-party processors (must be named):
  • GitHub — OAuth identity.
  • Cloudflare — hosting (Workers, KV, D1, Pages).
  • AWS Bedrock — for approved users only (Learn experience: role-based visibility + approved-user LLM tutoring (Bedrock Nova Sonic 2 / Nova Pro) #8): learner speech/text is sent
    to Nova Sonic 2 / Nova Pro for tutoring. This is the biggest disclosure —
    learner input leaves to a model provider; call it out explicitly.
• Retention + deletion: how long data is kept; the self-serve delete/export
  path (Learn: explicit user consent before saving learner data (consent gate + right to delete) #10).
• Learner rights: access, export, delete, withdraw consent; contact point.

Terms of Use should cover

• GitHub-based accounts; acceptable use; the service is provided "as is".
• The approved tutoring tier (Learn experience: role-based visibility + approved-user LLM tutoring (Bedrock Nova Sonic 2 / Nova Pro) #8) — eligibility, that it uses AI models, no
  guarantee of accuracy.
• Content/IP ownership; user-generated data.
• Termination + suspension; changes to terms (versioned → re-consent).
• Governing law / contact.

Open decision — where the documents live

Coordinate with org: agentculture.org may want site-wide ToU/Privacy
that /learn inherits, OR /learn ships its own because it processes data the static
org site does not (auth, ledger, Bedrock inference). Likely: a site-wide baseline

• a /learn-specific addendum for the data-processing bits. Decide with org before
  publishing; the domain and any existing policy are org-owned.

Acceptance (rough)

• Privacy Policy + Terms of Use pages published and linked from /learn.
• Both carry a version; the Learn: explicit user consent before saving learner data (consent gate + right to delete) #10 consent record stores which version was accepted.
• Bedrock/Nova data-processing is explicitly disclosed for the approved tier.
• Hosting/ownership decided with org and recorded.

Companion issues: consent gate #10, visibility/roles #8, content #9.

• learn-cli (Claude)