America.gov's mandated Login.gov backend already runs a 20-year tracking cookie

GoKawiil's interpretation of the reporting above, not reported fact.

The gap between America.gov's public privacy promises and the tracking code embedded in the authentication system it must use suggests the portal's privacy posture could depend entirely on backend components outside its own stated policies. Because the executive order mandates GSA integrate Login.gov as the authentication layer for a growing list of federal agencies and services, any tracking mechanism there could scale across the entire federal digital footprint rather than staying confined to one site. The order's assurance of 'privacy-preserving' integration and its limits on cross-agency data access may not address identifiers persisting at the shared authentication layer itself.

• Trump's executive order makes America.gov the single digital entry point for federal services and mandates Login.gov as its authentication backbone.
• Login.gov's public source code reportedly includes a National Design Studio feature generating a long-lived, 20-year browser identifier used in analytics.
• America.gov's current privacy materials disclaim advertising cookies and third-party trackers, but that promise doesn't clearly extend to the Login.gov layer it will depend on.