Editorial standards

These are the rules the Rifinit blog is written and checked against. They exist so a reader — and a reviewer — can tell what a guide is based on, who stands behind it, and how to get something fixed. If a page does not meet them, that is a bug; report it and we will correct the page or the claim.

Who writes here

The guides are published under the byline Alex Roshid, which is a pen name for the Rifinit engineering team. The people who write and review the articles are the people who build and maintain the PDF engine, the browser editor, the conversion tools and the OCR pipeline. There is no separate content agency and no ghostwritten product page.

How a guide is produced

  • Written from the product, not from a keyword list. Each article starts from a real workflow or a question support has actually received.
  • Checked against the shipped build. A claim about what a tool does is verified in the running application before it is published, including the edge cases the article warns about.
  • Numbers come from runs, not estimates. Where an article gives a file size, a page count, a resolution or a timing, it comes from processing a real document; the sample is described on the page.
  • Limits are stated. If a conversion, an OCR pass or an editor change cannot do something, the guide says so instead of promising a magic result.

Use of AI

We use AI-assisted drafting and editing tools, as most small technical teams do. That is not the standard by itself: the standard is that a person who works on the engine reviews every article, corrects it, checks its claims against the build and takes responsibility for what it says before it is published. We do not publish unedited model output, and a page that reads as generic is treated as a defect to rewrite, not as content to keep.

Corrections

If a page is wrong, unclear, out of date or missing a limitation that matters, email [email protected] with the URL. Substantive corrections update the page and its review date; a correction that changes what a tool does is also reflected in the product documentation. We would rather be corrected than keep a confident mistake online.

Independence and advertising

The blog does not accept paid placements, sponsored posts or paid rankings. Advertising on the site is labelled and kept separate from the editorial; no advertiser sees an article before it is published and none can change a verdict about a tool. Comparisons describe the workflows we have actually tested, including where a different tool is the better choice.

Review dates

Every guide carries a review date. Tool pages, the documentation and the guides are revisited when the engine or the interface changes, and a page that can no longer be verified is corrected or withdrawn rather than left to age quietly.

What this policy is not

It is not a claim that every article is perfect, and it is not legal advice. It is a description of the process we follow and a way to hold us to it. For the product itself, see the security page, privacy policy and terms.

Standards and sources: PDF parsing and writing follow the open PDF specification, documented in the Library of Congress format registry; the interface follows WCAG 2.2 (W3C). Rifinit is independent of both organisations.

By the Rifinit team. Published under the Alex Roshid byline. We build, test and document these PDF tools in-house: every guide is written by the same engineers who work on the converters, the editor and the OCR pipeline. Meet the team. Read how we write and review, our privacy policy and terms. Last reviewed .

Follow Rifinit Facebook LinkedIn Pinterest Reddit