URL fragment vs. query
Example: Before trusting a pricing tool's "your numbers stay in the URL" promise, a cafe owner checks whether the food costs sit after the ? where the server logs them, or after the # where the server never sees them at all.
#-vs-?
In a URL, the part after ? is the query (sent to the server with every request). The part after # is the fragment (per HTTP spec, browsers never send it to the server). Tools that share scenarios via the fragment keep your inputs out of server logs entirely.
Why it matters
When a tool says “your numbers stay in the URL,” check whether they live in the query (which means the server logs them) or the fragment (which means the server never sees them). It’s the difference between a privacy claim and a privacy reality.
This is the mechanism behind claim 6 on the data promise.
Frequently asked
What is URL fragment vs. query?
URL fragment vs. query is in a URL, the part after ? is the query (sent to the server with every request). The part after # is the fragment (per HTTP spec, browsers never send it to the server). Tools that share scenarios via the fragment keep your inputs out of server logs entirely.
Why does URL fragment vs. query matter for a restaurant?
When a tool says “your numbers stay in the URL,” check whether they live in the query (which means the server logs them) or the fragment (which means the server never sees them). It’s the difference between a privacy claim and a privacy reality.
Browse all
149 terms.
Plain-English definitions for every term in your audit, organized by category.