Editorial policy · public methodology

Claims should be easy to check.

HighRoad publishes first-party product pages and clearly labelled editorial comparisons. This page explains where our facts come from, how we handle competitors and research, and what happens when something changes.

Published 15 July 2026Publisher: COBI Management SRLReport an error

Who writes and owns this content

The site is published by HighRoad Software, a brand of COBI Management SRL in Belgium. Product and editorial pages are written and maintained by the HighRoad Software editorial team in direct contact with the code and release materials for the products described.

That access makes HighRoad a primary source for its own software. It does not make HighRoad an independent reviewer of competitors. Every comparison is labelled as publisher-authored analysis, and competitor trademarks remain the property of their owners.

No invented bylines. We do not attach a fictional expert, clinician or reviewer to a page. Where qualified legal or clinical review has not occurred, we say so.

Our source hierarchy

1 · Product truth

Current source repository

For HighRoad features, platforms, processing paths and release status, the app repository and signed release material take precedence over older marketing copy.

2 · Competitors

First-party documentation

We prefer the competitor’s current product, support, privacy and plan pages. We do not use affiliate round-ups as evidence for a competitor fact.

3 · Science

Paper, registry or institutional source

We link to the DOI, PubMed record, journal page or an accountable public institution. Secondary commentary may add context, but it does not replace the underlying source.

4 · Commercial claims

Live public offer

A repository plan is not a Store offer. Public price, trial, entitlement and availability claims require a live regional listing or checkout.

How we write comparisons

A useful comparison starts with a decision, not a winner. We identify the job someone is trying to do, compare the dimensions that materially change that job, and name cases where the other product is a better fit. A larger catalogue, established cross-platform service or collaborative cloud workflow can be the right answer even when a HighRoad product offers a more private local path.

Comparison tables use descriptive criteria rather than manufactured scores. We avoid exact prices and catalogue counts unless a current official source makes them verifiable, and we date the review so readers know when the external facts were checked.

  • Included: workflow, platform, processing location, account requirements, source handling, meaningful limitations and current availability.
  • Excluded: paid placement, affiliate commissions, hidden weighting, fabricated user reviews and unsupported “best” claims.
  • Disclosure: the comparison is written by the publisher of the HighRoad product and is not an endorsement by the other company.

How health and research evidence is labelled

A citation can support a technique without validating a particular app implementation. PulseWave therefore uses three evidence labels throughout its research library:

Direct

The named technique was studied

The paper evaluates the same named breathing method or a materially matching cadence. This still does not mean PulseWave itself was clinically tested.

Adjacent

The broader mechanism or family was studied

Research supports slow-paced breathing, HRV biofeedback or diaphragmatic breathing, but not necessarily the precise count or label used in the app.

Practice

A practical rhythm, without direct validation

The cadence is an editorial breathing exercise. It must not be presented as clinically proven or as treating a condition.

Health boundary. HighRoad has not represented that its editorial team provides clinical review. PulseWave is a general-wellness product, not a medical device, crisis service or substitute for professional care.

How generative AI fits into the writing process

Software tools may help inspect repositories, find inconsistencies, test links or draft a structure. They are not treated as sources. A claim must remain traceable to a repository, current first-party document or identifiable publication, and the final copy is edited for the actual product rather than published as generic search text.

We do not create a separate page for every keyword variation. A page should answer a distinct human decision, disclose limitations and add information that is not already available in a product card.

Dates, corrections and material changes

Each comparison and research page shows a reviewed date. We recheck external facts when updating the page, when a product launches, or when a reported error affects the decision. Repository facts are also checked before release-language changes.

To report a factual error, email support@highroadsoftware.com with the page, disputed statement and a source. We correct verified errors in the visible copy and update the modified date. A correction that changes the conclusion should be called out on the page rather than silently buried.

What this policy cannot provide

Transparent first-party documentation improves accountability; it does not create independent authority by itself. Genuine third-party coverage, customer experience, professional review and community discussion must come from people and organisations outside HighRoad. We do not manufacture those signals, trade links or present sponsored mentions as editorial validation.

Reference standards used for this policy