# Billflare collection policy / 收录原则

## How we collect cases

We organize public billing reports and follow-ups. We do not audit private accounts or adjudicate billing disputes.

### Trace the original report.

A case needs a public original source describing an unexpected Cloudflare charge. We group the author’s thread, replies and follow-ups into one incident. Reposts are leads, not additional cases.

### Distinguish charges from estimates.

We preserve the reported number and stated billing period. An estimate is marked ≈; an undisclosed amount stays unknown, not zero. Cloudflare reports using $ default to USD unless the source states otherwise. Monthly costs stay monthly. The case directory sums recorded report amounts, not net losses; refunds do not subtract from the reported charge.

### Identify who reported it.

We check that links, quoted text and incident identity match their sources. Author-reported and provider-reported identify who stated an outcome, not a trust score. We do not verify private invoices or refund settlement. A source that explicitly contradicts an earlier statement is retained as a correction or conflicting account, with both links.

### Keep the reported explanation.

Cause tags organize explanations found in the original reports. We attribute each explanation to its author rather than present it as our technical diagnosis. Corrections stay in the same incident’s timeline.

### Record the specific follow-up.

Each update links to its original source. We distinguish refunds, waivers, credits, adjustments, declined requests and ongoing review, with author or provider attribution. Public replies are recorded separately. An author-reported refund remains visible even when no public provider reply is linked. Partial outcomes retain their stated scope, and a thank-you is recorded as a thank-you.

- [Collection policy](https://billflare.dev/methodology)

## 我们怎样收录案例

整理公开账单报告与后续，不审计私人账单，不裁决账单争议。

### 先找到原始报告。

案例需要公开原始来源，说明当事人遇到的 Cloudflare 意外费用。作者的串文、回复和后续归并为同一事件。转述只作线索，不重复计为案例。

### 分清账单与估算。

保留报告数字和已注明的账期。估算标记为 ≈，未披露金额保持未知，不填零。Cloudflare 报告中的 $ 和“刀”默认按 USD 展示，原帖明确其他币种时除外。月费保持月费。案例目录合计是已记录报告金额之和，不是净损失；退款不扣减原报告费用。

### 说明是谁报告的。

我们检查链接、原文和事件归并是否对应。“作者报告”和“平台报告”说明陈述来源，不是可信度评级。本站不独立审计私人账单或核验退款到账。后续来源明确纠正或反驳早期陈述时，保留更正内容与双方链接。

### 保留原帖中的原因说明。

原因标签整理原帖给出的解释，注明是谁提出的，不作为本站技术诊断。作者后续更正原因时，在同一案例时间线中保留更新。

### 记录具体后续动作。

每条更新链接自己的原始来源。退款、减免、抵扣、调整、拒绝和复核进展分别记录，并标明作者或平台报告。公开回复另列；尚未收录公开回复，不影响展示作者报告的退款。部分结果保留原帖说明的范围，感谢帖只记录感谢。

- [收录原则](https://billflare.dev/zh/methodology)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)