Start with mechanisms, not headlines
Rental devices are exposed to a recognizable set of problems: overdue accounts and lost contact, unlawful disposal of the device, abnormal account activity, and attempts to bypass management controls. These are the mechanisms worth discussing. What should not be inferred from them is a number. Naming a risk is not the same as quantifying it. A precise description of a failure mode is useful; an invented total is not.
Evidence standard for case figures
Whenever a case is cited with a participant count, a device count or a monetary amount, three items must accompany it: the original source, meaning a public-security authority, a court or a reputable news outlet; the publication date; and the stage of the case. If the source or the case stage cannot be verified, the specific figure is not disclosed. The stage matters because a case under investigation is not the same as a concluded one. This is a rule about verifiability, not a judgment that the underlying event did or did not happen. It protects the reader from numbers that look precise but cannot be checked.
How to assess a delivery or pricing model
- Evaluate the technical maintenance behind the model, and whether it is documented.
- Look at the update mechanism and how quickly issues are actually handled.
- Check the response process and where contractual responsibility sits when something fails.
These are verifiable dimensions that can be compared across providers. A price point or a delivery method should never be labelled unsafe as a category. Where evidence is missing, the correct statement is that the claim has not been verified, not that the model is dangerous. Requiring this discipline does not weaken the discussion of risk; it makes the discussion usable.
