Captured fields
Public routes may capture operator name, work email, organization, account intent and minimum continuity context so Foundry can evaluate access intent and communicate the next safe step.
PAGE 06 — PRIVACY
Privacy for Foundry Account and desktop continuation.
The Foundry public surface exists for purchase, account continuation, authorized download and guided review with the smallest possible amount of operator operational data.
DATA CAPTURED ON THE PUBLIC SURFACE
Only the minimum account-path context should be captured on the web surface.
WEB SURFACE LIMITS
Browser-side identity resolution is not the same thing as desktop authorization.
Operational boundary
Foundry continues to separate public identity, remote access policy, machine authorization and local runtime truth.
RETENTION AND USE
Account-path data should be retained only for continuity, support and minimal auditability.
Retention principle
Data should exist only as long as required to evaluate eligibility, sustain continuity communication, answer account support and preserve basic distribution decisions.
OPERATIONAL CONTACT
Submitting an account or recovery request acts as consent for operational follow-up.
Foundry may use that submission to contact the operator about account continuation, controlled distribution and next onboarding steps.