Generated data
A generator creates synthetic values for tests, fixtures, demos and mockups. A plausible format does not make the value a real person, company, account or card.
Privacy · accuracy · clear limits
How OnSubmit tools process and verify data
OnSubmit is a catalog of free browser tools. This page explains where processing happens, what each type of result proves, how changes are checked and when an official source is still required.
Browser-first processingExplicit result scopeOfficial-source boundaries
Core definitions
Generated, validated, converted and calculated are not the same
Each verb describes a different level of assurance. OnSubmit keeps those meanings separate.
Local validation
A validator checks rules available in the browser, such as length, allowed characters, checksum or control key. It does not prove that a record exists in an official registry.
Conversion
A converter changes representation or file format. It preserves or transforms the supplied input but cannot confirm that the original data is accurate.
Calculation
A calculator applies the displayed formula and assumptions. Financial, payroll, tax and property outputs are estimates unless an authoritative workflow confirms them.
Result scope
What an OnSubmit result confirms and what it does not
This distinction is especially important for banking, company, tax and financial tools.
| Result type | What it can confirm | What it cannot confirm |
|---|---|---|
| Generator | Syntax, structure and implemented checksum rules | Real-world existence, ownership or official allocation |
| Validator | Local format, length, checksum or control key | Registry status, identity, account status or legal validity |
| Converter | Transformation produced from the supplied input | Accuracy or authenticity of the source data |
| Calculator | Result of the displayed formula and assumptions | Personal advice, contractual amount or authority decision |
| File tool | Output created locally by the browser | Compatibility with every reader, device or downstream system |
Review process
How a tool change is checked
Verification scales with the risk of the feature. Formula and structured-data changes receive focused test cases in addition to build and browser checks.
- Define the expected format, formula, unit and boundaries before changing the interface.
- Keep reusable calculation or generation logic separate from the visual component when the feature warrants it.
- Test representative, boundary and invalid inputs for formulas and structured generators.
- Run type checks and a production build, then test the actual user flow in a browser.
- State the result scope, common mistakes and official-source boundary on the page.
Trust and limits
Privacy, sources and corrections
Useful tools should explain both their behavior and their limits.
Tool inputs stay in the browser
Current catalog tools process text and files on the device and do not send tool inputs to the OnSubmit API. The contact form is a separate server request.
Official checks remain official
VIES, INSEE, banking institutions, tax authorities and other registries remain the source of truth for existence, status and legal or administrative use.
Sources are linked where they matter
Reference guides cite primary or official material when a format or formula depends on it. A missing or outdated rule can be reported through the contact form.
FAQ
Questions about OnSubmit reliability
Are files and text entered into OnSubmit tools uploaded?
No. Current catalog tools process their inputs in the browser and do not send those inputs to the OnSubmit API. The contact form is separate and sends only the message you submit.
What is the difference between a valid format and a real value?
A valid format satisfies local rules such as length, allowed characters or checksum. A real value is also assigned, active or recorded by the relevant bank, company registry or authority.
Can generated IBAN, SIRET, identity or card data be used officially?
No. Generated values are synthetic test data for QA, fixtures, demos and mockups. They must not be used for payments, contracts, registrations or identity checks.
Do OnSubmit validators query official databases?
Unless a page explicitly says otherwise, validators perform local structural checks. For example, VIES is still required for official EU VAT status and INSEE or another public source for French company records.
How accurate are the financial calculators?
They apply the formula, rates and assumptions shown on the page. Rounding, fees, insurance, tax rules and contractual conditions can change the final amount, so results are estimates rather than advice.
How are tool changes tested?
Changes are checked with a production build and browser testing. Formula and structured-data features also receive focused automated cases when their risk warrants it.
How can I report an incorrect result or outdated rule?
Use the OnSubmit contact form and include the tool URL, input, observed output and expected result without sending personal, banking or confidential production data.