Privacy
Learn what the site's analytics and future email tools may collect, what they never collect, and the privacy release conditions.
Data minimization
The measurement design records aggregate page and mission-action events using opaque content, source, destination and release IDs. It must not send names, email addresses, phone numbers, street addresses, ZIP codes, message text, form values, child or case data, placement information, diagnoses, precise location or sensitive audience labels.
Location and audience limits
Analytics may use a provider’s coarse inferred region as a directional aggregate. The site never labels an identifiable person as a foster youth, parent, provider, voter or other sensitive role. Release links may describe an asset or channel, never a visitor’s status.
Email and confirmation pages
No update-list connection is active in this code branch. Any future form must use double opt-in. Confirmation tokens and query strings must be removed before any page-hit or analytics code runs, or analytics must remain disabled on the callback page.
Hosting and essential security
The site is delivered through Cloudflare-backed hosting. The hosting and security layer may process request metadata such as IP address, user agent and request headers, and may set an essential security cookie such as __cf_bm to distinguish malicious or automated traffic. Georgia Doesn't Care does not use that security cookie to build advertising profiles or identify a visitor's relationship to foster care.
The site also loads its typefaces from Google Fonts. A visitor's browser may therefore send Google the IP address and request metadata needed to deliver those font files. No Google analytics or advertising code is enabled.
Release condition
Questions about these boundaries can be sent through the contact page. Publication and attribution rules are defined in the editorial policy.