Verification before publication

Data correction policy

Potential errors are leads for editorial verification. A report never changes a published broker fact automatically.

What belongs in a data report

  • A wrong or changed fee.
  • A broken or superseded official source.
  • Changed country or account eligibility.
  • A missing material condition.
  • Incorrect account, investment, or platform availability.
  • A reproducible calculation discrepancy.

Never submit sensitive or personal information

Do not send brokerage account numbers, passwords, government IDs, tax documents, names, email addresses, exact holdings, screenshots containing personal data, investment-loss details, broker-support complaints, or legal allegations unrelated to a modeled product fact.

How review and publication work

  1. The claimed fact is checked against the most specific official jurisdiction and product source.
  2. Conflicts, dates, conditions, and calculation rules are reproduced before editing product data.
  3. A confirmed error is changed through repository review and receives a public record labeled Correction, with before and after text when concise.
  4. Unconfirmed reports do not alter the comparison.

There is no guaranteed response time.

Current submission status

A monitored correction email is available. Send a concise description and the relevant official public source to hello@findyourbestbroker.com. Do not include any of the personal or sensitive information listed above.

There is no public web form because the application has no configured D1 binding, form-specific abuse controls, or retention automation. Email reports are verification leads and never change published data automatically. Use the official source ledger to inspect the current record.

Retention if reporting is introduced

The proposed policy is to retain anonymous reports for 12 months after resolution, then delete them or aggregate non-identifying issue metadata. This is a proposal, not a claim that automated deletion currently runs. A future form must publish the implemented retention schedule before launch and will not request contact email by default.

Raw descriptions and source URLs will never be rendered publicly or sent to analytics. Application logs must record only a generic outcome and controlled category, never the report body.

View corrections and material changes · Return to the full methodology