Privacy notice
Who we are
App Review Wait is operated by Emily Galash. Write to hello@appreviewwait.com. Sponsor questions go to sponsor@appreviewwait.com.
Reading the site
You can read the status page without an account. That does not ask for your name, email, or phone number. The outlier checker does not save what you type.
A visitor who is only reading does not get a cookie from this site. The dark-mode choice and the last status tab you open stay in this browser's local storage. Neither one is a cookie.
Accounts and reports
Signing in sends you one email with a link. Resend delivers that email. The address is kept only until you use the link or it expires, which is 15 minutes. The account stores a hash of the email, not the address itself.
Connecting App Store Connect sends event types and times. It does not send an App Store Connect key. The secret that checks those events is stored encrypted.
A report can include an optional app name, link, and category. You choose whether the name and link are shown. You can remove them from a report you own.
Signed in, you can export your data from the contribute page, and you can delete the account there. Deleting the account removes it, ends the session, and takes your name and link off your reports. The waiting times stay, with no name attached.
Cookies and similar storage
After you sign in, the site sets one cookie, rw_session. It is HttpOnly and SameSite=Lax, and it lasts 30 days. It is how the contribute page knows the session. Signing out or deleting the account clears it. The cookie page has the full list.
Posts from X
The status page shows posts embedded from X. Each embed is loaded with Do Not Track turned on. X may still set its own cookies. View on X is an ordinary link and does not load the embed by itself.
App icons
If a report shows an app icon, your browser loads that image from Apple. Apple can see the IP address of that request. Apple decides what it does with that request.
Who processes data
Cloudflare hosts the site, runs Turnstile on the contribute form, gates the admin page with Cloudflare Access, and routes mail to the contact addresses with Email Routing. Cloudflare Web Analytics, when its token is set, counts visits and does not use a cookie.
Supabase hosts the database in the European Union. It holds accounts, reports, connections, and the other records described here.
Resend sends the sign-in email.
Sentry receives error reports in the United States, from the browser and from the server. Before a report is sent, emails, tokens, query strings, cookies, headers, request bodies, and IP addresses are removed. No user profile is attached.
PostHog, when its key is set, records product analytics in the European Union. It keeps that data in memory for the tab. Autocapture is off and session replay is off. It does not write a cookie or local storage. The script is not on the page while the key is empty.
Why we use it
Publishing the waiting times is a legitimate interest: developers can see how long reviews are taking.
The account, the sign-in email, and the reports you submit are the steps you ask for so a time can be published.
The rw_session cookie is necessary to keep you signed in.
Sentry is a legitimate interest in fixing errors. PostHog and Cloudflare Web Analytics are a legitimate interest in knowing which pages are used, without a cookie. Turnstile is a legitimate interest in blocking abuse of the sign-in form. Cloudflare Access is a legitimate interest in limiting the admin page to the operator.
Showing a public post from X is a legitimate interest in putting that post next to the times. X is a separate controller for its own cookies. Loading an icon from Apple makes Apple a separate controller for that request.
A sponsorship arranged by email is a contract. This site does not take a card payment.
Transfers to the United States
Cloudflare, Resend, and Sentry process data in the United States. Supabase and PostHog process data in the European Union. A transfer to the United States uses Standard Contractual Clauses or the EU-US Data Privacy Framework, whichever that processor offers.
How long we keep it
A published waiting time is separated from the contributor after 24 months. An account that has not been used for 24 months is deleted 30 days after that. A sign-in link expires after 15 minutes. The session cookie lasts 30 days.
An address that asked for alerts and has not confirmed is deleted after 7 days. Posts used for What people are saying are kept for 12 months. Ingest logs are kept for 30 days. Sponsor billing records are kept for 7 years. Backups are deleted after 14 days.
Your rights
You can export or delete your contributor data yourself, as described above. You can ask us to correct it. Write to the contact address below. We aim to answer within one month.
You can complain to a data protection regulator. If you are in the EU or the UK, that is the regulator where you live or work.
The site is for people 16 and over. It is not aimed at children.
Contact
hello@appreviewwait.com