Carrier Record methodology

What a Carrier Record is

A Carrier Record is a factual regulatory record about one specific legal insurance underwriting entity — what public regulators have reported, by whom, over what period, with what limitations. It is not an opinion or a recommendation from Dinjir.

Brand, group, and legal entity are three different things

A brand (the name on your policy documents or advertising) is not the same thing as the legal entity that underwrites it, and is not the same thing as a group (a holding structure that may own several separate legal entities). One brand can be underwritten by more than one legal entity, and a Carrier Record covers exactly one legal entity — never a brand, and never a blended group total. Where a brand maps to more than one entity, Dinjir states that cardinality explicitly rather than leaving it implied.

Data-state vocabulary

Every fact on a Carrier Record is labeled with one of a small set of honest states:

“Not available” and “not yet publishable” are different claims and are never combined: the first means nobody publishes this; the second means a record exists and Dinjir is not yet permitted or able to show it.

Dinjir publishes facts and computes no ratings

Dinjir does not rate, score, grade, rank, or certify insurance carriers, and does not compute or display a claims-paying rating, a denial rate, an underpayment rate, or a bad-faith rate.

Dinjir does not award a "verified carrier" designation or any trust mark.

Every figure on a Carrier Record is either a fact as published by a public source, or a calculated ratio built transparently from a single source's own figures, with that source and the formula shown.

The money firewall

No carrier, brand, or group can pay to appear, to be excluded, to change a figure, to change the order facts appear in, or to receive different treatment than any other carrier's record. Carrier Records take only the record itself as input — there is no field in Dinjir's carrier data pipeline for a payment, sponsorship, or partnership status, so none can reach what is displayed.

Carrier participation

Carrier Records are built entirely from public regulatory sources. A carrier's non- participation is stated as a plain fact on its own record, not implied. Dinjir plans a process for insurers to submit attributed factual responses; until it exists, no such response appears on any record.

A formal dispute-and-response process for carriers is planned; until it exists, Dinjir displays no enforcement or litigation content.

How correction requests and responses will work (planned, not yet live)

Two separate paths are planned, and only one of them can ever change what a fact displays. A carrier may request a correction of Dinjir's own transcription of a source record — a wrong entity attribution, a mislabeled period, a transcribed number that does not match the source document. Dinjir does not adjudicate the underlying regulatory dispute. A correction request may fix Dinjir's own transcription of a source record; it cannot change what the regulator found. A correction request under review does not change how a fact currently displays, and a rejected request is not evidence of anything.

Separately, a carrier will be able to publish one attributed response next to a fact it addresses. A response cannot alter, hide, reorder, or de-emphasize any fact — it is purely additive, and it always stays open to the carrier, even after a correction request is rejected. Neither path is purchasable: no field anywhere in this planned machinery varies review speed, visibility, or outcome by payment, participation tier, or partner status.

When a regulator later vacates, reverses, or withdraws an action, Dinjir will show that as a dated, neutral status layered on top of the original record — the original text stays visible, unedited; the status change is never read as vindication or as erasure of the original filing.

None of this is live. No real carrier correction or response has been submitted, reviewed, or published. The methodology above describes machinery under development, not a feature available today.

Corrections

Carrier Records follow the same visible-corrections policy as the rest of Dinjir — see the corrections policy for how reported errors are handled.