Viewer Safety LabInstagram Account Viewer Testing
RankingsViewer ReviewsMonthly ReportsHow We TestSafety GuidesAboutCheck a Viewer

Corrections Policy

Tests describe a moment in time, and websites change. When a result is inaccurate or out of date, we want to fix it: quickly, transparently, and on the record.

Last updated: June 2026

Our commitment

Accuracy is the whole point of the Index. If we get something wrong, or if a service has genuinely changed, we correct it from evidence, log the change publicly, and update the affected score. Corrections are never quietly edited away.

What qualifies as a correction

  • A factual error in a review: a mis-stated tracker count, an incorrect login finding, a wrong tested date.
  • A material change by the service since it was last tested: it removed a login prompt, dropped trackers, or added a redirect.
  • A misattribution: the wrong domain, logo, or operator linked to a review.

Disagreeing with the methodology itself is not a correction; that's feedback, and it's welcome through the submission form. A correction is about a specific, verifiable fact.

Request a correction

Anyone (a visitor, a researcher, or a service operator) can request a correction. Point us at the result, tell us what's inaccurate, and include evidence we can verify.

To request a correction, email the lab with: the review or page URL, what is inaccurate, and any evidence (screenshots, links, dates). Anyone may file one: readers, researchers, or the service operator. Every request is reviewed against fresh test evidence.

Email a correction request

Our review process

  1. AcknowledgedEvery request is logged on receipt. If you left an email, we confirm we have it.
  2. VerifiedWe re-check the claim against evidence and, where relevant, re-run the test on the live service.
  3. ResolvedIf substantiated, we update the review and score, usually within one test cycle; urgent safety issues are handled sooner.
  4. LoggedThe change is recorded in the public corrections log below, with the date and reason.
Safety issues jump the queue. A report that a service has started requesting Instagram credentials is treated as urgent and retested ahead of the normal cycle.

The corrections log

Resolved corrections are published here so the record of what changed, and why, stays visible.

Published corrections and score changes, with date, service, change, and reason
DateServiceChangeReason
Jul 13, 2026StoriesIGDomain status: storiesig.net marked deadLive check found the domain unreachable; WHOIS now lists Instagram, LLC. Review pinned to storiesig.info.
Jul 11, 2026AnonyIGGridinsoft trust card: 88 to 95Reputation recheck during the July update; card and FAQ synced to the new reading.
Jul 11, 2026AnonyIGAvailability note addedA June report of a US legal block did not reproduce in our July 11 checks from US and EU vantage points.
Jul 11, 2026InviziogramFeature list correctedComments, tagged posts, and Smart History are labeled coming soon by the vendor; a June third-party review had listed them as live.

Every entry reflects a documented change to a published review; the affected page is updated in the same pass.

Retests & scores

  • A substantiated correction triggers a retest, and the score is recalculated from the new evidence using the standard methodology.
  • Updated reviews note that they were corrected and when.
  • Previous scores remain visible in the monthly reports, so a correction never erases history.

For how funding and independence relate to all of this, see the Editorial Policy.