App support
One channel, read by the people who wrote the app. There is no ticket queue and no bot in front of it.
Put app in the subject so it is routed straight to the right person.
What to include
A report we can reproduce is worth ten descriptions of it:
- The URL involved, if the problem concerns a specific inspection or a monitored page.
- What you expected and what happened instead.
- The app version and your iOS version, both shown at the bottom of Settings.
- For a score you disagree with: which check, and what you believe the correct verdict is. Every check names what it tested and what it found, so this is usually a short sentence.
Do not send passwords, API keys or anything from a private page. We never need them, and a support message is not a safe place for them.
Subscriptions — what only Apple can do
Subscriptions are sold and billed by Apple, so several things are genuinely outside our reach:
- Cancelling. iOS Settings → your Apple Account → Subscriptions → Outrings. We cannot cancel one for you, and neither can the app.
- Refunds. Requested from Apple, granted or refused by Apple.
- Changing plan. Done in the app or in the App Store; Apple prorates it.
- Restoring a purchase after reinstalling or on a new phone: Settings → Restore purchases in the app. It uses your Apple Account, so it works without any account with us.
If a subscription is active but the app does not see it, that is ours to fix — write to us.
Answered before you ask
A URL will not come off my list
A monitored URL holds its slot for 30 days, and can only be removed in its first hour. You can mute it at any time, which stops all alerts while the slot runs out. Why the rule exists.
I got no notification, but the score changed
Check the alert mode in Settings — "problems only" stays silent for improvements. Also check that the URL is not muted, and that notifications are allowed for Outrings in iOS Settings. iOS decides the final timing of delivery; we can ask, not insist.
A check says "blocked"
The site refused our request, usually a firewall or a rate limiter. Blocked checks are reported and excluded from the score, rather than counted as failures, because a refusal says nothing about the site itself. More on that.
The app and the website show different scores
They should not: both call the same engine with the same ruleset. If they differ, compare the ruleset version printed under each report, and whether either run has blocked checks — a site that refuses one request and answers the next produces exactly this. If neither explains it, tell us both URLs and both timestamps.
Something else is wrong with a report
The engine is ours and the rules are published. If a check is wrong, we would rather know: every check is documented, and a specific disagreement is an easy thing to act on.