How reports and held builds work

Guest and Free builds: a report reviewed as likely real or unclear holds the build, so its link takes no installs, and the owner gets an email with the reason category and text, never who reported. A guest build shows the hold on its manage page. A likely junk report does not hold the build and goes to the staff queue only.

Pro and Team builds: each likely real or unclear report sends the owner a warning email with the reason, at most one an hour per build, and the build keeps working. Once 5 different people have such reports open, the build is held and the owner is emailed. Likely junk reports do not count. If the automated review is not available, a report counts as unclear.

Channels skip a held build, and the owner cannot lift a hold. When staff clear a build, older reports never count again and new ones count from zero. The release email says the link works again.

A file our staff removed for abuse cannot be uploaded again: the same file is refused. Guest Android uploads that ask for a set of permissions typical of covert surveillance, such as reading SMS and the call log together with an accessibility service, are held for a person to review before anyone can install them. Builds with the app ID of big companies that do not ship test builds here, or known malware app IDs, are refused at upload.

Every upload, on every plan, is also checked for known malware right after the link is issued, and a match is held for a person in the same way. See the malware check for what it covers. Testers should still install builds only from people they trust.