How We Test and Write Docubox Guides

Guides are drafted with an AI writing assistant and published under the Docubox Team byline. The rules the assistant follows are kept in our code repository next to the site’s code, and the team is responsible for every published page.

A person reviewed and approved each of the first five guides before it was published. Later guides are published once they pass the checks below.

• Statements about what a Docubox tool does are checked against the tool’s source code and settings, not written from memory. If a guide says a tool keeps or removes something, that was checked against the code that does it, and each claim is recorded with the file and line that backs it so it can be reviewed.
• Numbers about Docubox, such as file limits, daily allowances and prices, are filled in from the same settings the app enforces instead of being typed by hand, so they change when the settings do. See pricing for the current plans.
• When a guide says something about another company’s product, it links to where that information comes from.
• Nothing in a guide comes from files people upload.
• We do not invent statistics, test results, quotes or testimonials.

• A title and summary built around one search phrase, with no other guide or tool page written for the same phrase.
• Guide text of at least 900 words, plus three to eight questions and answers shown on the page.
• At least two links to Docubox pages that exist, including a link to a tool page.
• No prices or file sizes typed by hand, unless the same sentence links to an outside source.
• For comparison guides, links to at least two different outside sources.
• No near-copies: compared five words at a time, a guide shares less than a fifth of its wording with any tool page or other guide.
• A steady pace: at most two new guides a day and fourteen in any seven days.

Each Docubox tool has automated tests that run sample files through the same conversion code the site uses, and after every change to the conversion code, every tool is run on the live site with test files. Guides do not report test results of their own: they describe what the code does.

When you use a tool, your files are processed on our servers. Uploads and unsaved results expire 24 hours after you start. A result you save to My documents is kept as a copy until you delete it; the upload itself still expires. Downloading neither deletes a file nor adds time. Read the file retention policy and how we protect files.

If something in a guide is wrong or out of date, email support@docubox.io. We correct confirmed errors and update the date at the top of the guide.