Editorial standards
Business owners use our articles and guides to make real decisions about their computers, data and compliance. This page explains who writes them, how we check the facts, how we fix mistakes, and what our content is and is not.
Who writes and reviews Preferred Data articles?
Articles are published under the company name, Preferred Data Corporation. They draw on the same work we do every day for our clients: managed IT, cybersecurity, compliance, cloud and custom software.
Preferred Data Corporation has served businesses from High Point, North Carolina since 1987. You can read more about the company on our about page.
The byline on each post names the company rather than an individual. If we add named authors in the future, each will have a short bio with their role and relevant experience.
How do we source and check facts?
Every statistic, deadline, dollar figure and legal requirement should link to the source it came from, right where we state it, so you can check it yourself. We prefer primary sources: the government agency, the standards body or the vendor that published the information. If we cannot verify a fact, we leave it out rather than guess.
| Kind of fact | Source we look for first |
|---|---|
| A security flaw or patch | The vendor’s own security advisory, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) when it lists the flaw as actively exploited |
| A law, rule or deadline | The agency or legislature that issued it, such as the Federal Register or the North Carolina General Statutes |
| A statistic or survey result | The original report from the organization that collected the data, not an article that repeats it |
| A price or licensing change | The vendor’s published price list, licensing terms or announcement |
- Links go next to the claim they support, written as the name of the source, not a bare web address or a numbered footnote.
- When sources disagree, we say so and tell you which one we relied on.
- We do not invent examples, client stories, quotes or results. If a post describes our own work, it describes work we actually do.
- New posts must meet this standard before they publish. Some older posts were written before it; we bring them up to it as we update them.
How do we handle corrections and updates?
If something we published is wrong or out of date, we fix it. When a change could affect a decision you made based on the post, we add a dated update note at the top that says what changed, instead of quietly rewriting it.
- To report an error, use our contact page or call (336) 886-3282. Include the page address and what you believe is wrong; a link to a source helps.
- We check the report against the source. If we got it wrong, we correct the page.
- Security posts are updated when the facts change, for example when a patch is replaced or a deadline moves.
- When two posts end up covering the same story, we keep the more complete one and send visitors from the other to it, so you do not find two versions that disagree.
How often do we review our guides?
Our guides, checklists and reports show the date their facts were last checked, so you can see how current they are. We re-check them when the rules, prices or products they describe change.
A news post about a specific security flaw or announcement describes what was known as of the date shown on the post. When we refresh a post with newer facts, the date shown changes to the refresh date, and corrections to older claims are added as dated update notes.
Is our content legal, tax or insurance advice?
No. Our articles and guides are general information to help you understand a topic and ask better questions. They are not legal, tax, accounting or insurance advice, and they cannot account for your specific situation.
Where a post discusses a legal obligation, such as a data breach notice rule or a federal contract requirement, check with your attorney before you act. For insurance questions, talk to your broker or carrier.
How do we handle the products and services we sell?
Preferred Data Corporation sells IT, security and software services, and some posts mention products we install or support. When a post points to something we offer, it links to that service page, so the business relationship is clear.
Product and company names mentioned in our content are trademarks of their owners. Mentioning a product does not mean its maker reviewed or endorsed our article.
Frequently asked questions
How do I report a mistake in an article?
Use our contact page or call (336) 886-3282. Tell us the page address and what you believe is wrong, and include a link to a source if you have one.
Why do your posts list the company as the author?
Our articles are published and reviewed by Preferred Data Corporation as a company, so the byline names the company. You can read about who we are on our about page.
Can I rely on a blog post to meet a compliance requirement?
Use our posts to understand what a requirement is and what questions to ask, not as proof of compliance. Rules change and every business is different, so confirm legal obligations with your attorney and the agency that sets the rule.
What happens when a newer post covers the same topic as an older one?
We keep the more complete and better-sourced post and send visitors from the other one to it. That way you find one current version instead of two that may disagree.
Questions about something you read here?
Talk to our team about your own network, security or compliance question, or tell us about an error so we can fix it.