Takedown log

Recorded review removals, their reasons and sentiments, and how to inspect aggregate takedown-request counts without publishing private messages.

This page lists recorded review removals from Christian Rated. Takedown-request outcomes are counted in aggregate on Transparency; private requests are not individual public entries. The table below is read from recorded moderation actions. Aggregate counts are produced by the reporting job, and relevant review events can be checked in the public vote log.

What the table shows

One row per removal, newest first. The columns:

Column Meaning
Date When the removal was recorded, to the second, in UTC. The same time is in the log.
Resource The listing the review was about, linked.
Review The review’s id, such as r_7k2m. It is the same id as in the log, so the row can be matched to its review.removed event and to the anchor that covers it.
Reason One of the five listed reasons: suspected fake, unrelated to the resource, harassment or obscenity, personal information about a private person, or a review of a person. There is no other reason.
Sentiment Positive, negative or mixed: how the review read at the time it was removed.
By Moderator, or author. A row marked author is a withdrawal by the person who wrote it, listed here so that the log and the page agree.
Organizations The two organizations that acted: the one that proposed the removal and the one that confirmed it. A row marked “override” uses the limited REVA operator route, either because no partner had an assigned moderator or because the configured waiting period had passed when that timed route was enabled; those are counted on their own line on the transparency page.
Appeal None, open, upheld or declined. An upheld appeal restores the review, and the restoration is logged too.

A withdrawn or removed review loses its text. Its row stays, and its event in the log keeps a hash of the text, which reveals nothing about what the text said. That is described on the privacy page.

How to read it

Look at the sentiment column first. If removals were falling mostly on negative reviews, or mostly on reviews of one maker, this is where it would show. The transparency page totals the same rows by reason and sentiment, with reviews of REVA, our own app, on their own line, so that you can compare our product’s removal rate with everyone else’s without doing the arithmetic.

Then look at the reason. “We never remove a review because it is negative” is checkable here: human removals use the listed reasons. Author withdrawals and other recorded actions are distinct from a moderator’s decision to remove a review. Doctrinal arguments do not appear in this table at all, because they are moved to theological notes, not removed. Moves are counted on the transparency page.

Then, if you want, check a row against the log. Each review id appears in a review.removed event with the same reason, sentiment and time, and any confirmed Solana anchor can be checked against that log prefix. Anchoring is optional; the live status on Verify shows whether a confirmed anchor is available. The Verify page explains how.

Takedown requests

Takedown requests from readers and makers enter the staff request inbox. Aggregate request counts are shown on Transparency; private request messages and contact details are not an additional public table. The outcomes are applied or declined. A request is applied only when the review meets one of the five reasons above, or when a listing is withdrawn under the listing policy. A request from a maker to remove a review because it is negative is declined, and the decline is listed.

A legal request, such as a right-to-erasure request, is handled as described on the privacy page and appears here with the outcome and without the person’s name.

What is not here

Declines before publication are counted on the transparency page but not listed by row, because a declined review was never on the open web. Freezes and listing withdrawals are listed on the transparency page with their dates and reasons. Appeals are counted there and shown in the Appeal column here.

Our own app

Removals of reviews about REVA products are reported separately on Transparency, with their sentiment. Authorized participating-company moderators can inspect the review process through their assigned roles. Any separately completed outside oversight is identified on the conflicts page; it is not claimed automatically for every removal. If you think a row below was wrong, use the appeal if it is your review, or report a conflict if it is not.

The log

No removals yet.

Last changed 2026-10-25 · This page as Markdown