Independent by design
DevLifeCheck is not a manufacturer, carrier, regulator, repair provider, or security-certification body. Affiliate links never change a verdict.
ABOUT DEVLIFECHECK
DevLifeCheck helps people understand how long an exact device variant is inside a stated operating-system or security-support period, what evidence supports that conclusion, and what remains unknown.
DevLifeCheck is operated and published by Rufuf E Commerce (روفوف للتجارة الإلكترونية), a single-member limited liability company registered in Qatar. Feroz Sheikh remains the editor and reviewer of the device research.
Rufuf company details · Rufuf Instagram · Rufuf Snapchat · Rufuf Facebook

EDITORIAL IDENTITY
Feroz Sheikh is the editor and reviewer behind DevLifeCheck, an independent device-lifecycle research project. He focuses on exact model identity, regional scope, manufacturer support commitments, firmware evidence, recall screening, and repair context. His review process keeps official dates separate from policy-derived calculations and leaves unsupported claims clearly marked as unknown. Before a record is published, he checks the source, model code, jurisdiction, date precision, and wording limitations. Feroz also maintains the public correction process so material evidence changes can be reviewed, documented, and reflected in revision history.
DevLifeCheck is not a manufacturer, carrier, regulator, repair provider, or security-certification body. Affiliate links never change a verdict.
Official dates, policy-derived calculations, regional scope, precision, and checked dates remain visible. Missing evidence stays unknown.
Material corrections enter an editorial queue and appear in revision history after the supporting source and exact model scope are reviewed.
A “supported” label means the record remains inside the cited manufacturer commitment as of the displayed review date. It does not guarantee that every vulnerability is fixed, every carrier build arrives together, or a product is safe for every use. “No exact recall match” reports only the regulator sources and date named on the page.
Questions about a record, correction evidence, licensing, or press citations can be sent to [email protected]. For a structured correction, use the public queue so the affected model and source stay attached.