Verify recipe inputs stay on this device
LocalCupGrams converts cups ↔ grams and can scale pasted recipe lines entirely in the browser. This page is the check you can run yourself: which network calls are normal, and which calls would mean your inputs left the tab. The converter is on the home page. The short policy is the privacy policy. The usage rules are the terms. Publisher context is on about.
What you are proving
You are proving that converting and scaling do not upload ingredient choices, amounts, or pasted recipe text. You are not proving that nothing on your computer can see the tab. A browser extension, malware, or a recorder you installed can still read a page. This site does not receive those inputs, and it does not claim to block other software on the device. Values never leave this device through this page.
Also remember: density results are cooking guidance from published charts, not lab metrology, nutrition labels, or medical advice. See why volume ≠ weight.
If Network shows a POST or PUT of your amounts or paste, stop using that session and write to contact@localcupgrams.pages.dev with the page URL and what you saw — without attaching the real recipe. That would not match how this tool is built.
Steps in DevTools
- Open the converter. Use a throwaway test amount or a tiny pasted recipe the first time — not a private family recipe — until you trust the flow.
- Open DevTools → Network. In Chrome that panel is documented as the Network panel. In Firefox it is the Network Monitor. Enable “Preserve log” so a reload does not wipe the list.
- Reload the page once and let the first requests finish. You should see same-origin GETs for the document,
/assets/styles.css,/assets/tool.js,/assets/densities.json, and the favicon. - Change ingredient, amount, and unit. Switch Volume → grams and Grams → volume. Watch for new rows. There should be no POST, PUT, or beacon whose body is your amount or ingredient pick.
- Open the Recipe scale tab. Paste a few sample lines, set factor 1.5, and scale. Again: no upload of the pasted text. Scaling is plain arithmetic in
tool.js. - Optional: clear the scaler and close the tab. In-tab inputs and results drop with the page’s memory. We have no account library to reopen.
Expected requests
- Page assets. HTML, CSS,
tool.js,densities.json, and the icon — all GET, all from this site — when the page loads. The JSON is a static density table, not your recipe. - Analytics beacon, maybe. The privacy policy describes Cloudflare Web Analytics. If that product is enabled for the zone, a request to
cloudflareinsights.comcan show up. It is a page-view beacon. It is not an upload of ingredients or pasted lines. The HTML we ship does not include an advertising script.
Requests that should not appear
- A POST, PUT, or PATCH that carries ingredient picks, amounts, or recipe paste.
- A call to a third-party “recipe API”, nutrition analyzer, or cloud converter after you type or paste.
- A script load from an ad host. Response headers for this site set a strict
script-srcto'self'. That policy does not list an ad network.
Why the math can stay in the tab
The converter multiplies your amount by a grams-per-cup value from the local density table. The scaler parses leading numbers on each pasted line and multiplies by your factor. Neither path needs a server round-trip with your inputs. Results are plain numbers in the DOM — not a downloadable cloud job, and not a nutrition label export. When you close the tab, those values go with the page’s memory.
This tool is for kitchen cups/tbsp/tsp ↔ grams (and ml for water-like liquids). It is not a garden fill, mulch, paint, or flooring planner.
Publisher, contact, and policy pages
These pages stay on the existing URLs. They are how you learn who publishes the tool and how to reach us:
- About — who publishes the pages.dev experiment and what the converter is for.
- Contact — a working mailbox for wording and bugs, with clear “do not paste private recipes.”
- Privacy — no recipe upload, hosting logs, optional Web Analytics, children note.
- Terms — acceptable use, density honesty, honest limits.
- This trust page — a verifiable Network check for browser-local conversion.
This experiment does not run advertising scripts today. Response headers set script-src 'self'. If that ever changes, privacy and about would need an honest update first.
Where to go next
- Convert cups ↔ grams
- Cups to grams for flour
- Tablespoons to grams for butter
- Scale a recipe 1.5×
- Why volume ≠ weight
- About · Privacy · Terms · Contact
Questions about this wording, email contact@localcupgrams.pages.dev. Do not paste a private family recipe into that email. We do not need it, and we do not want it in a mailbox.
Sources
- Chrome DevTools — Network panel: developer.chrome.com/docs/devtools/network
- Firefox — Network Monitor: firefox-source-docs.mozilla.org/…/network_monitor
- King Arthur Baking — Ingredient Weight Chart: kingarthurbaking.com/learn/ingredient-weight-chart
- USDA FoodData Central: fdc.nal.usda.gov
- MDN —
<details>element: developer.mozilla.org/…/details - MDN — Content Security Policy: developer.mozilla.org/…/CSP
- Cloudflare Web Analytics: developers.cloudflare.com/web-analytics/about
- Cloudflare Pages: developers.cloudflare.com/pages
FAQ
How do I prove LocalCupGrams does not upload my recipe?
Open DevTools → Network, change ingredients or paste a few test lines, then convert or scale. You should see same-origin page assets and densities.json. You should not see a POST or PUT of your inputs.
Is the densities.json request an upload of my ingredients?
No. It is a GET of a static table from this site when the page loads. The response is published cup-weight averages. Your picks and paste are not in that request.
What does Scale recipe send to the server?
Nothing required. Scaling multiplies leading quantities in the tab with tool.js. The paste never leaves as a form upload.
Which network requests are a problem?
A problem is any request that sends ingredient picks, amounts, or pasted recipe text, or calls a third-party converter/nutrition API after you type. Static assets and an optional Cloudflare Web Analytics beacon are not input uploads.
Are the gram numbers lab-certified?
No. They are cooking guidance aligned with King Arthur Baking– and USDA FoodData Central–style published charts. Packing and humidity change real weight — use a kitchen scale when precision matters.
Where do I report a Network result that looks wrong?
Email contact@localcupgrams.pages.dev with the page URL and what you saw in DevTools. Do not paste a private recipe. Start from this trust page and the privacy wording so we can compare claims to behavior. Also see contact.