Editorial & Review Policy
iTechVora aims to make consumer technology easier to understand through clear explanations, reliable sources and transparent evaluation. This policy sets the standards for our articles, reviews and recommendations.
These standards apply across smartphones, laptops, TVs, cameras, audio, monitors, tablets, wearables and accessories. They describe our editorial requirements; they are not a claim that every product mentioned has been independently tested.
Editorial responsibility and independence
iTechVora is led by Anil Kumar. Editorial decisions should serve readers: what a product does, who it suits, where it falls short and which claims remain uncertain. Brands, retailers and advertisers must not determine our conclusions, suppress relevant criticism or purchase a favourable score.
We may ask a manufacturer or other source to clarify a technical fact. That does not give the source approval over the article or its verdict. Authors must disclose relevant commercial relationships or personal interests that could affect a reader’s assessment of their work.
Sources, verification and uncertainty
Factual claims should be supported by appropriate evidence. Depending on the subject, this can include official product documentation, support pages, release notes, direct statements, original observations or clearly attributed reporting. Important sources should be linked so readers can examine them.
Manufacturer specifications and performance claims must be identified as such when they have not been independently verified. Rumours, leaks, estimates and unconfirmed availability should be clearly distinguished from confirmed information. We must not invent quotations, sources, benchmarks or product experience.
Exact model names, configurations, regions and software versions matter. Where information conflicts or cannot be confirmed, an article should explain the uncertainty rather than present an assumption as fact.
Reviews, previews and specification explainers
- Hands-on review: the author has used the product and explains the basis and limits of the evaluation.
- First impressions or preview: access or testing is limited. The article must make that limitation clear and avoid conclusions that require longer use.
- Specification or research-based explainer: the article draws on documented information and attributed sources. It must not imply personal testing.
- Buying guide or editorial comparison: recommendations should explain their selection criteria and identify whether they rely on hands-on experience, research or both.
Our review requirements
A hands-on review should identify the exact product tested, relevant software or firmware, how the product was obtained, the approximate testing period and the conditions that materially affect the findings. Loan units, supplied samples and paid travel or access must be disclosed when relevant.
Testing should fit the category and the claims made. For example:
- Phones, tablets and wearables: everyday usability, display, compatibility, software support and battery behaviour under stated conditions.
- Laptops and monitors: display, performance for the intended workload, connectivity, ergonomics and, where applicable, heat, noise and battery life.
- TVs, cameras and audio: relevant picture, capture or listening conditions, settings, connectivity and practical limitations.
- Accessories: compatibility, build, usability and the specific functions evaluated. Safety certifications must not be claimed without verification.
Measurements should identify their method, settings and context. Subjective impressions should be presented as impressions. Short-term testing cannot establish long-term reliability, and a review must not suggest otherwise. If equipment or access is unavailable, we should narrow the claims rather than imply that a test occurred.
Scores and recommendations
Not every article needs a score. Where a review includes a numerical score, it should be supported by a genuine evaluation and an explanation of the main strengths, limitations and intended audience. Scores are editorial judgements, not laboratory certifications or guarantees.
We do not automatically treat a higher number in a specification table as better. A useful recommendation considers compatibility, price, support, usability and the reader’s needs. Comparisons should use appropriate product types and explain material differences in configurations and testing conditions.
Prices, availability and product links
Our default currency is US dollars (USD). Prices, stock, offers and software features can vary by date, seller and region. Readers should confirm the exact model, final price, delivery costs, taxes and return terms with the retailer before purchasing.
A retailer link is not a guarantee of availability or service. Where we use an affiliate link that may earn a commission, that relationship should be disclosed clearly in the relevant content. Commercial benefit must not determine whether a product is recommended.
Sponsorships, samples and advertising
Any sponsored or paid content must be clearly labelled. Receiving a product, loan unit or invitation does not guarantee coverage, a positive review or a particular rating. Commercial arrangements must not be concealed as independent editorial opinion.
These rules govern any such arrangements; they do not imply that every article or link is sponsored or affiliated.
Originality, images and AI-assisted work
Articles must offer original value and use text, photographs, graphics and other material that we have the right to publish. Attribution is required where appropriate and does not replace permission when permission is needed.
If AI tools assist research, drafting or production, the responsible author or editor remains accountable for accuracy, originality, rights and source verification. AI output must not be used as evidence of a product test, personal experience or a quotation. Material uses that affect how readers interpret an article or image should be disclosed. Illustrations must not be presented as photographs documenting a test that did not occur.
Corrections and updates
Readers can report a possible error through our Contact page or at itechvora@gmail.com. Please include the article URL, the disputed statement and supporting evidence.
Confirmed substantive errors should be corrected with a note explaining the meaningful change. Updates that materially change a recommendation, specification or conclusion should be identified. Minor spelling, punctuation or formatting fixes may be made without a separate note. Dates should reflect genuine publication or revision, not be changed simply to make old coverage appear new.
Contributors and accountability
Contributors are expected to follow these standards and disclose relevant relationships, source limitations and material AI assistance. Read our Write for Us guidelines for submission requirements.
For more about the publication, visit About iTechVora. Our Disclaimer explains the general limits of the information on this website.
Last updated: September 22, 2026.