AppsinityAPPSINITY
Guides and support

Review and report moderation

Moderation on Appsinity is manual and reactive. There is no queue, no reviewer console, no automatic filter and no appeal form for a review; there is a strict data model, a clear policy on fabricated ratings, and email.

Open Appsinity Studio

How a review is stored

RuleBehaviourWhy it matters
One per personUnique on (collection, listing, uid)A second submission edits the first, it does not add
Rating clampRounded, then forced into 1 to 5A 0 is refused; a 9 becomes 5
Text limit2,000 charactersLong complaints are truncated, not rejected
Device and source200 and 120 charactersThe surface a review came from is recorded
Author nameStore display name, then token name, then email, then "Appsinity user"The name shown can outlive a rename
OrderNewest updated first, up to 100 readAn old edited review resurfaces at the top
DisplayA short list on the listingTen rows, not the full read
AverageMean across all stored rowsOne edit can move it
Note: Because an edit rewrites the same row, a five-star review turned one-star keeps its original createdAt and takes a fresh updatedAt. That is the shape of a changed opinion in the data.

What gets removed

The Terms give the platform its latitude: reviews must reflect genuine experience and must not be fabricated, purchased, coordinated or manipulated, and spam, abusive commentary, personal attacks, hate content or obvious rating manipulation may be removed without notice.

ContentRemovable?Typical trigger
Hate or targeted abuseYesA report
Personal information about a developerYesA report
Coordination text ("rate my game, I rate yours")YesPattern plus report
A bought-review clusterYesSame-hour volume
A negative but civil reviewNoDisagreement is not a violation
A one-star with no textNoSparse is not spam
Developer-supplied review textYesIt is still a review on your own listing
Spam in another languageYesIt is still spam
Watch out: There is no developer reply to a review and no way for you to delete one yourself. The only route is a report to support with the listing URL and the reason.

How a safety report travels

  1. A player writes to support. The support chat recognises report-adjacent words; the ticket form is the durable path.
  2. The ticket is stored. One document per ticket with an id, status open, the page URL and the user agent captured at submit time.
  3. A human reads it. There is no triage console; the queue is the collection.
  4. Action is taken on the listing. Restriction, delisting or account enforcement, see Developer policy.
  5. The reporter may or may not hear back. There is no status page and no SLA.
// what the platform records about a report
{
  ticketId: "AS-<base36 time>-<4 random>",
  name, email, type, priority,
  subject, message, pageUrl,
  userAgent, status: "open",
  source: "support-page",
  createdAt
}
// clamps: name 100, email 160, type 80, priority 40,
//        subject 160, message 2500, pageUrl 500
Note: Copyright and trademark reports use the same email route with a stricter evidence packet, see Copyright.

What moderation does not include

  • No profanity filter runs on review text.
  • No machine moderation scores a review before it appears.
  • No verified-purchase flag distinguishes someone who downloaded from someone who did not.
  • No helper-fairness voting by players.
  • No per-review report button on the listing.
  • No appeal path for a developer whose review was removed.
  • No transparency report on removals.
Not available: Appsinity reserves the right to restructure, limit or temporarily suspend review features as abuse mitigation. A review surface that disappears is a policy decision, not an outage.

Your side of the bargain

  • Do not solicit ratings from inside the app in a way that gates a reward on a positive response; that is manufactured engagement.
  • Do not post reviews on your own listings from alternate accounts, which is trivially visible because identity is the storage key.
  • Answer reports about your own listing promptly, with the listing URL and the build path.
  • If a review is factually wrong about a bug you fixed, publish the fix rather than arguing with the text.

Frequently asked questions

Can I delete a review of my game?

No. There is no developer-side deletion and no reply field. Report a violation with the listing URL and the reason and let a human act on it.

Why can one person only review once?

The row is keyed on listing plus account, so a second submission updates it. It removes the cheapest form of rating manipulation.

Does the average include removed reviews?

A deleted row stops contributing, and the recomputation happens the next time analytics is read.

Is there an automated spam filter on reviews?

No. Nothing scores review text before publication; removal is manual and after the fact.

Need help?

Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]