Effective date: August 12, 2026
eDigitalReviews uses research, product documentation, direct evaluation, technical evidence, and reliable external information to create technology reviews, buying guides, product comparisons, tutorials, and software analysis.
This Sources and Citations Policy explains how we select information, evaluate sources, identify firsthand testing, handle manufacturer claims, cite important facts, and correct information when better evidence becomes available.
A source should do more than make an article appear authoritative. It should help readers understand where information came from and why a factual statement, technical conclusion, or recommendation can be trusted.
Our Research Standard
We aim to use sources that are relevant, reliable, current, and appropriate for the claim being made.
The source required for a product price may not be appropriate for a performance claim. A manufacturer’s specification page may be authoritative for a listed port or supported format, but it does not independently prove that the product performs better than a competitor.
Before publication, we may verify:
- Product specifications.
- Compatibility information.
- Software features.
- Warranty and support conditions.
- Product availability.
- Pricing and subscription costs.
- Technical standards.
- Performance claims.
- Product launch details.
- Company statements.
- Security and privacy information.
- Product documentation.
- Regional differences.
The depth of research depends on the subject, the complexity of the claim, its importance to the article, and the potential effect on a reader’s decision.
Types of Sources
We may use several types of sources during editorial research.
Official Manufacturer Information
Manufacturer websites, product pages, manuals, support documents, firmware notes, technical data sheets, and official announcements can help confirm product specifications, supported features, compatibility, accessories, warranty details, and software requirements.
Official information is useful but may contain marketing language or information that applies only to a particular model, region, configuration, or release. We assess the context rather than treating every promotional statement as an independently proven fact.
Direct Product Evaluation
Hands-on testing, product use, measurements, photographs, screenshots, software access, and direct observation may provide evidence that cannot be obtained from a specification sheet.
We distinguish direct evaluation from research-based information. We do not claim to have tested a product physically when we only reviewed documentation, watched a demonstration, studied public information, or received comments from another person.
Testing results may depend on the equipment, software, settings, environment, configuration, and duration of the evaluation. We include relevant context when it affects interpretation.
Technical Documentation
Technical manuals, support articles, developer documentation, standards information, installation instructions, and release notes may be used to explain how a product or service operates.
Technical documents can clarify compatibility, limitations, settings, file formats, system requirements, and update behavior. We review the date and version of documentation when the information may change over time.
Retailer and Marketplace Information
Retailer listings may help confirm current pricing, inventory, regional configurations, included accessories, delivery conditions, and available purchasing options.
Retailer information may change frequently and may contain inaccurate or incomplete product details. We do not rely on one retailer listing for a significant technical claim when a more authoritative source is available.
Expert and Company Statements
We may use statements from company representatives, engineers, developers, photographers, creators, researchers, or other informed individuals.
We aim to identify the speaker and preserve the meaning of the statement. A company statement may explain its position or product design but does not automatically establish that a performance claim is objectively true.
Reader Feedback and User Experience
Reader comments, product submissions, support messages, and user experiences can identify practical issues, compatibility details, regional differences, or changes that deserve investigation.
Reader feedback is not automatically verified. We may use it to identify a question, request additional evidence, or investigate a possible correction. We do not present an individual experience as universal evidence without appropriate support.
Matching Sources to Claims
We aim to match each claim with an appropriate source.
For example:
- A manufacturer manual may support a product’s supported connection types.
- A software support document may support system requirements.
- A retailer listing may support a current price at a particular time.
- Direct testing may support an observation about setup or usability.
- A published technical standard may explain a format or protocol.
- An official company announcement may confirm a launch or product change.
- Independent measurement may support a performance comparison.
The strength of a conclusion should not exceed the strength of the evidence. If a source confirms that a product includes a feature, that does not automatically prove the feature is useful, reliable, or better than a competitor.
Citations in Articles
We may cite sources directly in an article when a reader would benefit from knowing where important information came from.
Citations may be used for:
- Technical specifications.
- Official product announcements.
- Pricing and subscription conditions.
- Compatibility requirements.
- Warranty information.
- Software changes.
- Industry statistics.
- Research findings.
- Security or privacy claims.
- Regulatory or standards information.
- Statements attributed to a company or individual.
A citation should be relevant to the statement it supports. We avoid attaching one citation to a paragraph containing several unrelated claims when the source does not support all of them.
Citations should not be used to give unsupported opinions the appearance of verification. Editorial conclusions should be explained through reasoning, testing, comparison, and relevant evidence.
Current Information
Some information becomes outdated quickly. Prices, inventory, software features, firmware, support policies, subscription fees, warranty terms, and product availability may change after an article is published.
When an article includes time-sensitive information, we aim to provide enough context for readers to understand that the information may change.
Readers should confirm current pricing, product configuration, availability, warranty coverage, return terms, and subscription conditions before purchasing or signing up for a service.
An old source may remain appropriate for historical context but may not support a current claim. We review dates carefully when using a source to describe present conditions.
Conflicting Sources
Sources may disagree about a specification, feature, performance result, or product configuration. When this occurs, we may compare the sources, review updated documentation, contact the relevant company, examine the product directly, or qualify the wording.
Possible reasons for conflicting information include:
- Different regional models.
- Pre-release documentation.
- Retailer listing errors.
- Firmware or software updates.
- Optional accessories.
- Product revisions.
- Different testing conditions.
- Manufacturer terminology.
- Discontinued configurations.
We do not hide meaningful uncertainty. When a detail cannot be confirmed with reasonable confidence, we may identify the limitation, use qualified language, or leave the claim out.
Manufacturer and Brand Materials
Manufacturers may provide specifications, press information, product images, technical documents, review samples, demonstrations, or responses to questions.
These materials may inform our research but do not automatically determine the editorial conclusion. Marketing statements should be identified as company claims when that distinction matters.
A company may report that a product is faster, more durable, more accurate, more secure, or more efficient than a competitor. We may include the claim, but we should not present it as independently verified unless the available evidence supports that conclusion.
Pricing and Affiliate Information
Price information may be gathered from manufacturers, retailers, marketplaces, affiliate platforms, or direct observation.
Because prices can change, a citation or source may support the price at a particular time without guaranteeing that the same price remains available. We aim to avoid presenting temporary discounts as permanent pricing.
Affiliate links may provide referral information or commission reporting. Affiliate status does not make a source more reliable and does not determine whether a product receives a recommendation.
Images, Screenshots, and Visual Evidence
Images and screenshots may help demonstrate a product’s design, software interface, feature, configuration, or testing environment.
Visual evidence should be identified accurately. We do not present manufacturer imagery as original hands-on photography, and we do not present an edited or generated image as a real product photograph or testing result.
Screenshots should reflect the relevant software version, account type, device, or configuration when those details affect interpretation.
Charts and comparison tables should be checked for consistent units, product models, dates, and source information.
Artificial Intelligence and Research Tools
Artificial intelligence tools may assist with organizing notes, identifying research questions, checking structure, or improving sentence clarity.
AI-generated information is not considered verified evidence by itself. We do not use fabricated citations, invented sources, false quotations, generated test results, or unsupported AI claims in published content.
A human writer or editor must verify important information and review the final article. If a source cannot be located, checked, or understood, it should not be used as support for a factual claim.
Corrections and Source Updates
If a source is discovered to be inaccurate, outdated, misinterpreted, removed, or incorrectly attributed, we may revise the affected article.
A correction may involve:
- Replacing the source.
- Revising the supported claim.
- Adding context.
- Removing unsupported information.
- Updating a table.
- Changing a recommendation.
- Adding a clarification.
- Updating the article date after a substantial revision.
Readers may report possible source or citation errors through the website’s contact form. A useful report should identify the article, the statement, the concern, and supporting information.
Our aim is to use sources that support the information presented, explain the basis of important claims, distinguish evidence from opinion, and give readers a clearer understanding of how technology conclusions are reached.