Should I Text Back? is designed to be useful without asking who you are. This policy explains what happens when you use the tool and what would change if advertising or analytics is enabled later.
What we collect
We do not require an account, collect your name or email, or store the text messages and relationship details you type into the decision helper. The verdict is calculated for the moment you ask. The current verdict endpoint is stateless and does not save your form input.
Local storage
Your browser may store an anonymous usage count, your five most recent verdict summaries (verdict, relationship label, elapsed time, and checked-at time), a light or dark theme choice, an optional community-submission draft, and your privacy preferences. The privacy record stores only necessary, analytics, and advertising choices with a version and decision time under should_i_text_back_consent_v1. You can clear this data at any time through your browser settings or reopen Privacy choices in the footer.
Region-aware privacy prompt
No verified CDN currently supplies a trusted country signal, so the app ignores country headers sent by browsers or other clients and uses the more protective unknown-region prompt by default. If a verified edge is configured later, only the header that edge strips and rewrites will be trusted. This is a practical interface rule, not a legal determination of your location or rights.
AdSense verification loader
We load Google’s AdSense script for site verification for publisher ID ca-pub-9041250000937538. No AdSense ad units, placements, or Auto ads are currently enabled, and Google Analytics remains inactive because no real GA4 Measurement ID is configured. Prepared analytics code will load only after a real ID is supplied and the saved analytics preference allows it. The verification loader is placed in the shared document head and is not currently gated by the custom preference choices.
Google and its service providers may process technical information and may use cookies, web beacons, IP addresses, or similar identifiers as described in Google’s policies. Learn more at How Google uses data when you use our partners’ sites or apps.
Certified consent platforms
The current custom privacy controls are a consent foundation, not a Google-certified CMP and do not implement IAB TCF. Before AdSense serves ads in the EEA, UK, or Switzerland, the site must be connected to a Google-certified platform supporting the required framework version. Consent and policy requirements will be reviewed again before any ad unit is activated.
Third-party links
Our links and embedded content may take you to other websites. Their privacy practices are controlled by their own policies. We do not control how those sites handle data.
Questions
For questions about this policy, use the contact channel provided by the site owner. This page is plain-language information, not legal advice. See our advertising and editorial disclosure for the short version.