Transparent by default

How the Review Queue Index is calculated.

A small honest sample is more useful than a precise-looking number with unknown inputs.

01

What we collect

Submission type, Apple platform, Submitted/In Review/Decision timestamps, outcome, and whether the app includes login or IAP. We do not require the app name, bundle ID, Apple ID, or API credentials.

02

Manual vs verified

Manual observations are accepted but labeled. A future optional App Store Connect webhook will verify exact status transitions using per-app secrets and minimal event data.

03

Publication threshold

We do not publish aggregate timing until a window contains at least ten complete timelines. Every index shows its complete and verified sample counts.

04

Robust statistics

The primary figure is the median. P90 describes the long tail. We do not use a simple average as the headline because a single multi-week outlier can distort it.

05

Quality controls

Impossible sequences, future times, duplicate patterns, and extreme values are quarantined for review. Verified and manual samples remain distinguishable.

06

What the index cannot say

It cannot predict an individual decision time, guarantee approval, or reveal Apple's internal prioritization. It is a planning signal, not a service-level agreement.