Home / Editorial standards

Editorial standards

Every post on this blog is published by VaultCord. There is no independent editorial team, and we are not going to invent one by putting fictional names on articles. What we can tell you is what gets checked before a post goes out, and what we refuse to publish.

Posts carry the “VaultCord Team” byline because that is accurate: they are written and edited in-house. You should read anything here about VaultCord as coming from the people who make it, with the bias that implies. When another tool is the better choice for the job in the headline, the post says so.

We do not attach invented author names, fictional credentials, or made-up years of experience. If a post ever carries a person’s name, it is a real person who worked on that post.

What we check

• Claims about VaultCord match the product. If a post says a setting exists, that setting exists, under that name, on the plan the post names. A post that describes a feature we have not shipped is a bug, not a marketing choice.
• Competitor pricing is dated. Other companies change plans without telling us. Where we quote a price or a limit, we say the day we checked it, we link their page, and you should confirm it there before you pay.
• Third-party tools have to be real. We only name a bot we can open. Where we cannot check a detail, we say so and link the page we looked at.
• Internal links have to resolve. A link to another post is checked against posts that are actually published.
• The read time is counted from the words on the page, at 220 words a minute, and never shown as less than one minute.
• The date is the day the post was published or the day a real correction went in. We do not change it to look newer.

What we will not publish

• Reviews or testimonials we made up. No invented quote from “a server owner,” and no star rating we awarded ourselves.
• Statistics we did not measure. No “70% of servers we protect.”
• Tools that do not exist.
• A verdict that cannot lose. If VaultCord is the wrong tool for the job, the verdict names who should pick something else.
• File paths, repository names, or function names in a post written for server owners. Those belong in the writing notes, not on the page.

Corrections

If something here is wrong, tell us and we will fix it. The fastest route is the chat on help.vaultcord.com. Corrections are made in the article. Where a correction changes the meaning, we say so in the Editorial disclosure on that post, with the date.

That applies to other products too. If you work on a bot we described and we got a limit or a price wrong, we would rather hear it from you than leave it wrong.