Quality and corrections
Corrections policy
How we report, verify, prioritise and publish corrections.
Quality and corrections
What you should know
The key information is presented below in a short, scannable format.
What to include in a report
A report should identify the exact page, describe the problem, provide the expected and actual result, include only the inputs needed to reproduce the issue and, where relevant, link to a public source. Never send a PESEL, NIP, health, financial or other personal data.
How reports are classified
Reports are classified as calculation-engine errors, content or translation errors, outdated sources or parameters, accessibility problems, or privacy and security concerns. Priority depends on the impact, the number of affected pages and the risk of a user making a wrong decision.
Verification and evidence
A calculation error is reproduced in an isolated test case and checked against the formula and the source applicable to the stated year. Regulated changes are verified against a primary source. A result is not changed solely because an undocumented expectation differs.
How a correction is implemented
A confirmed engine error receives a regression test before the code is changed. After correction, we run type, formatting and unit checks, the static build, link and SEO audits, and representative browser tests. A content or source correction also requires review of the corresponding Polish and English versions.
High-risk errors
If an error could materially distort a legal, tax, financial, employment, education or health result, the page may be temporarily excluded from indexing or withdrawn until verification is complete. Preventing further use of an uncertain result takes priority.
Change transparency
A material correction updates the page review date, engine version or source documentation as appropriate. A correction in one language is checked against its counterpart so that the two versions do not silently diverge.
Personal data in reports
Data included in a report sent to contact@oblicznik.com may be used only to investigate and handle that matter. The website does not provide a contact form. Correspondence is retained for no more than 12 months after the last message, deleted earlier when no longer needed, or kept longer only where required by law or necessary to establish, exercise or defend legal claims.
Last reviewed: 20 September 2026
Verification
Sources and related policies
These references were checked when this page was reviewed.
Useful links
Continue exploring
Read the core pages behind the service or go directly to the tool catalogue.