Write Path
Firestore
Client writes with rules
Data HandlingFirebase Data ScopeNo Custom BackendNo User Accounts
Privacy Statement
This web runtime stores contribution and map context data in Firebase services with clear scope boundaries and no custom backend.
Privacy copy must match implementation: Firebase client writes for lead, map brief, and quiz records, analytics instrumentation enabled, and no account system in public V1.
Account Model
None
No sign-in in public V1
Analytics
Enabled
Firebase Analytics events
Data Handling
Firebase-only privacy model with explicit data boundaries.
Public V1 uses Firestore and Analytics without accounts or a custom backend.
Firebase-only runtime • no custom backendData Handling Matrix
Firebase data boundariesHome Contribution
Firestore `leads` + aggregate-safe `communitySubmissions`
Captures name, email, optional phone, occupation, state, derived region, and era in the lead record; aggregate map docs keep only state, region, and era.
Firebase HTTPS client write.
Map Research Brief
Firestore collection (`researchBriefs`) + browser cache
Captures full name, email, era, and selected themes from the explorer brief modal.
Firebase HTTPS client write + local browser state.
Map Filters, Selection & Share Focus
URL query params (`era`, `theme`, `category`, `id`, `state`)
Syncs explorer state, pinned heatmap focus, and share links across reloads.
Client-side state + optional Firestore reads.
Analytics Signals
Firebase Analytics
Tracks lead-first funnel and map interaction events.
Google Analytics for Firebase SDK.
Contribution records are retained in Firestore according to product policy and operational review.
URL filters and pinned heatmap focus remain shareable and can reseed `/map` context without requiring account login.
No custom backend queue or account history is active in this public phase.
Form fields are labeled, grouped, and keyboard reachable to support screen-reader and non-pointer navigation.
Public copy discloses Firebase-only runtime boundaries and avoids implying account-based identity storage.
Community map framing stays aggregate-first and avoids exposing exact personal location.
Availability Notes
Static SPA served from Vite build; hosting must rewrite unknown paths back to `index.html`.
Assets under `/public/stitch` are bundled into the build and served with long cache TTLs.
Availability depends on Firebase Hosting plus configured Firebase project services used by the web client.
Raise a Privacy Question
Need a deeper privacy review? Loop in the product owner and legal counsel. This repo ships only the experience surface; contractual questions belong to the governance docs linked from `docs/ops`.
Public V1 • Firebase-only • No account system
Current Public Summary
Search-Friendly Context
Privacy documentation defines what America250 contributor and quiz data is collected, what is excluded, and which Firebase services process runtime data.
What data is stored in the current preview?
Lead fields, selected archival context, and quiz submissions are stored for runtime operation and measurement in Firebase.
Does US250 store account credentials?
No. The public V1 preview does not include user account sign-in or credential storage.
Is exact personal location published on the map?
No. The map is intentionally aggregate-first and avoids publishing exact personal coordinates.
Related Information
These pages reduce ambiguity around the current preview build and tie the America250 topic cluster back to the archive surface, policies, and trust model.