METHODOLOGY
Every claim needs evidence
DevLifeCheck separates facts, calculations and estimates so a confident-looking interface never hides uncertainty.
Evidence hierarchy
Review workflow
- DiscoverFind a manufacturer, regulator or other permitted source.
- ParseCapture the exact claim, region, model family and effective date.
- MatchResolve variants and avoid transferring a claim to an unsupported model.
- VerifyThe named editor checks the source, scope and calculation before publication.
- PublishThe record receives a confidence label and review date.
- MonitorPolicy changes and stale evidence return to the review queue.
How a support date is calculated
When a manufacturer publishes an exact end date for a model, the record uses it as Grade A evidence. More often the manufacturer publishes a duration, such as “seven years of security updates from launch”. The record then states the documented start point and adds the duration.
Example: Google states that Pixel 8 receives OS and security updates for seven years from its first availability in the US Google Store in October 2023. The record therefore shows October 2030 as a Grade B, policy-derived horizon at month precision. It is not presented as the day of the final patch.
Minimum commitments, such as legally required update periods in the UK or EU, are labelled “at least” and kept separate from final dates. OS-upgrade promises are never converted into security-support dates.
How to read a device record
Device pages show only the facts recorded for that model. The explanations below apply to every record, so they are kept here once instead of being repeated on each page.
- Model and region: a record is not a universal “global variant.” Apply each support date, firmware release or repair fact only to the identifiers and regions named in its cited source. Listing an identifier does not establish shared lifecycle coverage, and a materially different variant needs its own reviewed evidence.
- Support dates: a support window is not a guarantee that every vulnerability is fixed or that every regional or carrier build arrives together. A support date is not a safety certificate or proof of the last patch. An unknown date does not establish that support has ended; check the installed software on the device.
- Shared dates: when two records share a release or support horizon, they remain separate records. A shared policy date is not evidence that firmware, recalls or repair records are interchangeable.
- Firmware: lifecycle evidence and firmware-source checks use separate dates. A documented build for one model and channel is not a worldwide latest-version claim, and a lifecycle-policy page never authorises copying or inferring a firmware version.
- Recall screening: DevLifeCheck monitors CPSC, EU Safety Gate, UK OPSS and Health Canada. A monitored feed is not itself a “no recall” finding. A dated non-match covers only the named feeds on that date and is not worldwide safety clearance.
- Repairability and battery: each repairability card shows only the facts published by its cited source. iFixit scores, manufacturer playback estimates and EU-label measurements use different tests and are not compared with each other. EPREL data is attached only to an exact approved registration, never borrowed from a related model.
- “Not documented”: means DevLifeCheck has no approved value for that field. It does not mean the value does not exist.
- Evidence grade: the grade is DevLifeCheck's classification of the source behind a date; it is not a safety rating.
- Provenance and hashes: where a record lists claim-to-evidence provenance, hashes identify the stored normalised capture of the source. They are not a substitute for reading the official source.
- Badges and citations: the embeddable status badge always links back to the canonical record so scope, evidence and uncertainty remain visible. See the badge builder and dataset and attribution guidance.
- Related records and shopping links: links to related records help comparison; shared dates, families or brands do not imply identical support policies or purchase recommendations. Paid links never change a date, grade or comparison.
Which records are promoted in search
Every published record stays readable. A device record is offered to search engines (indexed and listed in the sitemap) only when it carries a first-party source and device-specific facts beyond a single support date copied from one manufacturer table, such as a release date, an OS policy, documented firmware, repairability data, several sources or model variants. Records that only repeat one table row are kept out of search results; their brand hub or support list is the page to find.
Status labels
- Supported — the recorded security-support date is more than twelve months away.
- Ending soon — the recorded date falls within the next twelve months.
- Support ended — the recorded date has passed. The device still works, but new flaws may stay unfixed.
- Status unknown — no defensible end date is public; the record shows the manufacturer’s policy or update frequency instead.
Sources we use
- Manufacturers: support and update-policy pages, security bulletins, firmware release notes and product specifications.
- Regulators: U.S. CPSC, EU Safety Gate, UK Office for Product Safety and Standards, and Health Canada recall notices.
- Registries: the EU EPREL database for repairability, battery and durability labels, matched to exact registrations only.
- Independent assessments: iFixit repairability scores, shown as their own scheme and never blended with official labels.
Every source is listed in the public source registry with its owner, jurisdiction and last check date.
Review cadence and corrections
Sources are re-checked on their own schedule: recall feeds daily, and manufacturer policy and firmware pages monthly or quarterly. A changed or stale source sends the affected records back to the review queue. Anyone can submit a correction with an official source; confirmed changes are published with a revision entry, so earlier values remain visible.
Automation and AI use
DevLifeCheck is a structured database. Device, brand, comparison and report pages are generated from shared templates filled with each record's fields, and scheduled jobs fetch public sources to flag changes for review. Comparisons, calendars and lists are computed from the same records rather than written separately.
AI tools help draft template wording, guide text, Spanish and Hindi translations and site code. They are never used as a source: a support date or other fact is published only when it traces to a linked source for that exact model and region, and anything that cannot be traced stays marked as unknown. Section added .
Independence
DevLifeCheck is independent of manufacturers and retailers. Affiliate relationships, where present, never change a date, grade or verdict, and no manufacturer can pay to change a record.
Wording rules
We do not say a device “is secure.” We say it is within a stated security-support period. We do not say “no recalls exist.” We say no matching notices were found in the sources checked on a specific date.