Privacy
Last updated September 2026
Short version: we don't know who you are, and we can't find out.
There's no account and no login. We never ask for your name, your birthday, your address, or your phone number. We don't save what you type. Nobody at your county, your school, or your placement can look up what you asked us.
What we never collect
These aren't things we promise not to look at. They're things the software has no way to store.
- Your name, or any name
- What you typed — the words you send are used to find your answer and are then gone
- Your email address or phone number
- Your IP address or anything that identifies your phone
- Your location
- Any account, because there are no accounts
What we do count
We keep a count of how the service is used, so counties can see what young people actually need and where the gaps are. A record looks like this, and it cannot hold anything else:
- The kind of thing that was asked about — housing, food, ID — from a fixed list of categories
- The county, if a county was known from the link or QR code used
- Which QR code or printed link the visit came from
- Which resources were shown, and whether one was tapped
- Whether we had no verified resource for what was needed
- Whether a safety message was shown, and which kind
- The date and time, to the second
Why we count the gaps
When you tell us we didn't have what you needed, that goes into a report counties and the state use to decide what to fund. It is the most useful thing this service produces, and it carries nothing about you — only that somebody, somewhere in a county, needed a thing that did not exist.
Answers you see
Some wording is put together by an AI system. It can only describe resources we have already checked, and it is not allowed to write a phone number, web address, or street address at all — those are added by the app from our own records. Anything that breaks that rule is thrown away before you see it.
We check resources by calling them. Every one shows when it was last checked.
For reviewers and procurement
No personal data is collected, processed, or stored, so there is no data subject to access, correction, or deletion requests, and no breach could expose personal information because none exists to expose.
The service holds no protected health information and no education records, placing it outside the scope of HIPAA and FERPA. There is no user authentication, so there are no credentials to compromise.
Analytics records are structurally incapable of holding free text: every field is a fixed-vocabulary value, a boolean, an identifier from our own catalogue, or a timestamp. This is asserted by an automated test that inspects every event the system emits.
Message content is never written to a log, a database, an analytics record, or an error report. It exists only for the duration of the single request that produced the answer.
Requests are not associated with an IP address or device fingerprint. Timestamps are recorded to the second rather than the millisecond, so events cannot be correlated into a session by timing.
Changes
If this ever changes in a way that means we collect something about you, this page changes first, and it will say so plainly at the top.