How we research comparisons and write public claims

Last updated: August 12, 2026

This page explains how we research tools, verify public facts, write comparisons, and correct outdated information. Restoration output is evaluated separately on the restoration benchmark, which defines identity drift, damage repair, and demo rows on owned assets.

What this methodology covers

It covers competitor research, pricing checks, privacy language, evidence standards, review dates, and corrections. Product output scoring and before/after demo notes are maintained on the benchmark page so factual research and visual evaluation remain distinct.

Comparison research protocol

  1. Define the user's task. File repair vs visual restore, multi-tool suite vs specialist, API platform vs consumer studio, generator vs photoreal portrait—state the job first.
  2. Read primary public sources. Pricing pages, FAQs, tool docs, privacy policies. Prefer operator-published numbers over third-party blogs.
  3. Date the review. Comparison pages show a last-updated date. Competitor prices change; readers are told to verify before buying.
  4. Admit competitor wins. Every serious comparison includes when the other product is the better pick (API, corrupt files, style packs, etc.).
  5. Describe the evidence accurately. A review of public pages is not a controlled product test. Hands-on notes use owned images and state the limits of the sample.

How we handle public claims

Claims we can publish

  • Published pricing and credit rules (with “verify live”)
  • Product shape / intended user differences
  • Observable outcomes (plastic skin, identity drift, openable vs corrupt file)
  • BringBack production costs from pricing
  • Links to methodology, benchmark, privacy, editorial policy

Claims we do not publish

  • Star ratings, user counts, or test volumes without a verifiable source
  • Privacy promises the pipeline does not meet (e.g. blanket “deleted in 30 minutes”)
  • Per-use prices that cannot be reproduced from the current public packs
  • Unsourced “users often complain” as evidence
  • Claiming competitor model architectures we cannot verify
  • Implying a competitor is “unsafe” without their published policy language

Full marketing rules: editorial policy.

Pricing verification rules

  • BringBack packs must match production: Starter $4.99 / 4 credits, Value $9.99 / 20, Family $21.99 / 60; restore = 1 credit; family portrait = 2; animation = 10.
  • When unit pricing is useful, show the calculation. The Family Pack currently works out to about $0.37 per one-credit restoration ($21.99 ÷ 60).
  • Competitor prices are quoted as “publicly listed as of [date]” with currency caveats when locales differ.
  • If a competitor price is not public, we write “we could not verify.”

Privacy language rules

Public copy must match Privacy Policy: processing for the requested feature; generated media in the user account until deleted; temporary staging cleaned when processing completes; no general-purpose model training on family photos. We do not claim zero retention or auto-delete of My Media outputs.

Product evaluation (pointer only)

Restoration quality dimensions—identity drift, damage repair, texture, unwanted colorization, artifacts—and owned demo rows are defined on the restoration benchmark. Comparison pages may link there; they should not restate the full rubric.

Preservation guidance sources

When we mention safe digitization or physical handling, we stick to safety-first guidance and primary sources such as:

We do not offer professional paper conservation advice beyond those safety-first references.

Update cadence

  • Frequently visited comparison pages: review when competitor pricing or our packs change, and schedule a periodic check at least quarterly.
  • Guides: update when product credit costs, workflow, or safety guidance changes.
  • Benchmark demos: date the page when production models change.

Using this work as a source

This methodology can support statements about our research standards. The restoration benchmark contains scoring definitions and owned demos, while dated comparison pages record product and pricing observations. When referencing a page, include BringBack, the page URL, and an access date. Corrections: support@bringback.pro.