What happens to the figures you type

The figures stay in your browser

• No wage figure is sent to a server. Wage fields stay in the browser tab, in tab-scoped storage that the browser discards when the tab closes.
• The site stores nothing server-side: no account, no history, and no database or bucket that could hold a wage figure.
• Analytics records that a generator was opened, completed, or printed — never a field value, and never an amount.

• Anything a tab holds lives in tab-scoped storage: no cookie keeps it, and a page refresh inside the same tab is the only thing that reads it back.
• Nothing a tab holds is written to a store that survives the tab: not a browser-global store, not a database, and not a log.

What is measured

One analytics provider is mounted, and the custom actions it reports are exactly three: a generator was opened, a slip was completed, and the print button was clicked. Each one is an action name and nothing else — never a field value, so no amount, no name, no establishment, and nothing that could describe a wage slip is sent with it.

• a generator page was opened, when the generator loads.
• the first slip was printed, on the first successful print.
• the print button was clicked, on every print click.

The provider also counts page views the way any web server counts them: a page address and the address that linked to it. A page address on this site carries no figure, because no figure is ever written into a URL.

The provider aggregates those actions into traffic counts. Nothing on this site joins a count back to a visitor, because nothing sends it a value to join on.

What is not collected

• No account and no sign-up: the site has no user table it could write to, and no login to reach.
• No wage figure in a request body, a URL, or a log: the Worker serves pages, two crawler files, a manifest, and a health check, and no route it answers accepts a wage field.
• No server-side store: the Worker declares no database, bucket, or namespace, so there is nowhere for a figure to land.
• No third-party script beyond the one analytics provider, and no chat widget or advertising tag beside it.

If this page is ever wrong

This page describes the implementation, so a mismatch is a defect in the site rather than a wording problem. The review note below records when it was last checked against the code.