Corrections Policy
How CamoCrypt handles errors: we correct them publicly, log substantive changes with dates, and tell you how to report a mistake.
Why we have a corrections policy
CamoCrypt publishes security and education content that people may act on to protect real money. An error in that context is not a cosmetic problem — it can lead someone to a wrong command, a false sense of safety, or a procedure that exposes their funds. Because the stakes are real, we treat corrections as a core part of the publication, not an afterthought. We correct mistakes in the open and we keep a record.
What counts as a correction
We distinguish between two kinds of change:
- Substantive corrections are changes that alter the meaning, accuracy, or safety of a piece. Examples include a wrong command or flag, an incorrect technical claim, a mischaracterised attack or defence, a broken or misleading instruction, or any factual error a reader could have relied on. These are logged.
- Minor edits are changes that do not affect meaning — fixing a typo, a broken link, a formatting glitch, or clarifying wording without changing the substance. These are made silently and are not logged.
When in doubt, we treat a change as substantive and log it. We would rather over-disclose a correction than hide one that mattered.
How we correct
When we make a substantive correction, we do the following:
- We fix the error in the article itself.
- We add a dated note to the correction log below, describing what was wrong and what changed.
- Where the error was significant, we add a brief note on the affected article so readers of that page see that it was corrected and when.
We do not quietly rewrite an article to erase a meaningful mistake as if it never happened. If the original was wrong in a way that could have affected a reader, that fact belongs on the record.
The correction log
The log below lists substantive corrections as they occur, newest first, each with a date and a description. At the time of publication there are no logged corrections. This is not a claim of perfection — it simply means the log is new. As corrections happen, they will appear here.
| Date | Article | What changed |
|---|---|---|
| — | — | No corrections have been logged yet. Entries will be added here as they occur. |
Re-reviews are separate from corrections
Not every change to an article is a correction. As described in our editorial policy, security content is re-reviewed on a six-month cycle to keep it current. Routine updates made during a scheduled review — reflecting a wallet’s new defaults or an evolved attack technique — are maintenance, not corrections, unless they fix something that was actually wrong when published. The correction log is reserved for errors, so that it stays a meaningful record of when we got something wrong.
How to report an error
If you believe something on CamoCrypt is inaccurate, unsafe, or out of date, please tell us. Corrections from readers are genuinely valuable and we act on them. To report an error, use our contact page and include, if you can:
- The page or article, ideally with its URL.
- The specific claim, command, or instruction you think is wrong.
- Why you believe it is wrong, and a source we can check if you have one.
We read every report. If you have found a genuine error, we will correct it and, where it was substantive, log it here. We cannot always reply individually, but a good correction report improves the publication for everyone who reads the page after you.
One note on scope: this channel is for factual and safety corrections to our content. It is not a support desk, and — as our disclaimer explains — we cannot help recover lost or stolen funds and will never contact you offering to.