Editorial policy

Last updated 25 September 2026·Published by DALAMIS s.r.o.

This page describes how orviden.online is written and paid for. It exists so that you can judge our incentives before you judge our conclusions.

1. Who writes this site

Editorial responsibility for orviden.online rests with Sandra Ward, director of publication and responsible editor for DALAMIS s.r.o.. Every article carries a named byline and a publication date, and the byline is a real person who can be reached at info@orviden.online.

We do not publish anonymous content, and we do not publish content under invented author personas, invented job titles or invented credentials. If an article is ever contributed by someone other than the editor, that person will be named and the relationship disclosed.

2. How we establish facts

Our subject — consumer security software — is one where marketing copy circulates faster than checkable information, and where a great deal of what is published online is simply the vendor's own wording rephrased. We work to a small number of rules to avoid adding to that.

• Primary sources first. Product features, plan contents, device allowances and guarantee terms are read from the seller's or manufacturer's own published page, and we record the date we read it.
• Performance claims come from independent laboratories, or not at all. We cite AV-TEST, AV-Comparatives and SE Labs, which publish their methodologies. We name the laboratory, the test, the period and the result. We do not cite a vendor's summary of a test in place of the test.
• We never invent a number. If we have not measured something and cannot cite someone who did, we do not give a figure for it. We would rather write "we did not test this" than publish a plausible-sounding statistic.
• We hedge what is genuinely uncertain, and we say which parts are uncertain, rather than smoothing everything into the same confident tone.
• We date and re-check. Pages show when they were published and when the product information was last checked. Specifications change; an undated page about software is close to worthless.
• The seller's information prevails. Where our description of a product differs from the seller's own current page, the seller's page is right and ours needs fixing. Every product page says so.

3. How this site is funded

orviden.online is funded entirely by affiliate commission. When a reader follows a partner link and buys, the seller pays DALAMIS s.r.o. a percentage of the sale. The reader's price is not increased; the commission comes out of the seller's margin.

We take no payment for reviews, no payment for a favourable rating, no payment for placement and no payment to remove criticism. We do not accept sponsored posts, paid guest articles or link insertions. We run no display advertising, which is also why there are no advertising trackers on the site.

Because that funding model creates an obvious incentive, we disclose it in four places on every commercial page, rather than in a single line of small print: a bar across the top of every page, a disclosure box immediately beneath the headline and before any promotional content, a visible "partner link" label on every commercial button including those in sidebars, and a note under each button repeating that we earn a commission and that it costs you nothing extra. Every commercial link carries rel="sponsored nofollow noopener" in the page source.

4. Advertiser independence

Sellers and affiliate networks have no say in our editorial content. They do not see articles before publication, they cannot request changes, and no commercial relationship is conditional on the tone of what we write.

Three practical consequences follow, and you can check all of them in our articles:

• We publish what a product does not include, in the same detail as what it does — our main review's largest correction was precisely of this kind.
• We tell readers when they should not buy, including when a free alternative is adequate. Our review of a paid product names a free competitor and describes it fairly.
• We do not claim a product is "the best" unless a published test supports it. Usually one does not, and we say that instead.

If we ever cannot write honestly about a product while remaining in its affiliate programme, we leave the programme rather than adjust the article.

5. What we refuse to do

These are not aspirations. They are prohibitions, and breaking one is grounds for withdrawing a page.

• No fabricated testimonials. We do not invent readers, customers or their experiences, and we do not present editorial content as a "reader story" or a "reader-submitted" account. Every page on this site is editorial, written by the named author.
• No invented ratings or scores. We do not publish star ratings, "9.4/10" badges, or scoring tables of our own invention. Scores we quote belong to an independent laboratory and are attributed to it.
• No artificial urgency. No countdown timers, no "offer expires in 10 minutes", no false stock scarcity, no "only 3 licences left". Prices and promotions are the seller's business and are shown on the seller's site.
• No guaranteed-result claims. No security product can promise that you will not be infected, and we will not imply otherwise. Where a vendor offers a guarantee, we describe it as the vendor's commercial guarantee and point you to its conditions.
• No fear-based fabrication. Security writing lends itself to invented threat statistics. We do not use them. Threats are described qualitatively unless we can attribute a figure.
• No fake independence. We do not describe ourselves as a neutral comparison service while being paid by one side of the comparison. We are an affiliate publisher and we say so at the top of every page.
• No impersonation. We do not imitate a vendor's branding, do not use vendor logos or product screenshots, and do not publish anything that could be mistaken for an official page. All diagrams here are our own drawings.
• No hidden data collection. No trackers, no pixels, no fingerprinting — see the cookie policy.

6. Illustrations

Every diagram and illustration on this site is an original SVG drawing created for it. We use no product screenshots, no vendor artwork and no stock photography, both because reusing a vendor's imagery on an advertising-funded page raises trademark and copyright problems, and because a drawing can explain a mechanism that a screenshot merely shows. Each has descriptive alt text, an embedded title and description for assistive technology, and a caption identifying it as our own work.

7. Corrections procedure

We correct errors openly. The procedure is:

1. Report it. Write to info@orviden.online with the page address and what you believe is wrong. A source helps but is not required; "this contradicts the vendor's page" is enough to trigger a check.
2. We check it, normally within five working days, against the primary source.
3. We fix it. A factual error is corrected as soon as it is confirmed, not at the next scheduled update.
4. We record it. Substantive corrections — anything that could have changed a reader's decision — are listed in a corrections note on the page itself, saying what was wrong and what it now says. We do not silently rewrite history. The main article's corrections note is an example of this in practice.
5. We update the date. The "last updated" or "last checked" date on the page changes with the correction.
6. We answer you. Whoever reported the error is told what we did, including when we concluded the original text was right.

Minor typographic fixes are made without a note. Anything affecting meaning gets one.

8. Updates and withdrawal

Product pages are re-checked against the vendor's own information periodically and whenever a reader tells us something has changed. If a page becomes so out of date that it would mislead and we cannot bring it up to date, we withdraw it rather than leave it standing — and we keep its address working so that existing links do not break.

9. Scope

This policy applies to every page on orviden.online. Related documents: the legal notice (who we are), the privacy policy (what we do not collect), and the terms of use.