Frequently asked questions

Yes. AscAuto never asks for — and can never see — your Apple ID password. You connect with an official App Store Connect API key (.p8), the same mechanism CI systems like Fastlane use. The key is stored AES-256-GCM encrypted, needs only the App Manager role, and you can revoke it from App Store Connect at any moment, instantly cutting off all access.

Only safe metadata fixes — things like screenshots, descriptions, keywords, or age-rating answers — and only when the AI's confidence is above the threshold you set. Everything else (reviewer replies, code changes, anything ambiguous) lands in your approval queue and waits for your explicit one-click approval. Nothing risky ever ships on its own.

AscAuto classifies the rejection as a code issue, writes a diagnosis with the exact guideline and a proposed change, and — if you've connected a GitHub token — opens a pull request against your repo (1 credit). You review and merge the PR yourself; AscAuto then handles the resubmission. It never pushes to your branches directly.

Best coverage today: • Metadata issues (2.3.x) — screenshots, descriptions, misleading claims: often fully automatic. • Information requests (2.1) — drafts a reviewer reply for your approval. • Common code-level guidelines (e.g. 5.1.x privacy, 4.x design) — diagnosis plus a proposed PR. Rejections it can't confidently classify are still queued with a diagnosis, so you start from an explanation instead of a wall of Apple boilerplate.

Every account gets a private inbound address like user_8k3f@ascauto.org. Forward Apple's rejection email to it manually, or set a one-time filter in Gmail / Apple Mail that auto-forwards anything from Apple's review address. AscAuto verifies the sender, matches the email to your monitored app, and starts the diagnosis within seconds.

Anytime, two ways: delete the key inside AscAuto (we erase the encrypted material immediately), or revoke it in App Store Connect → Users and Access → Integrations — that kills access on Apple's side instantly, no cooperation from us needed.

During the private beta, monitoring and metadata auto-fixes are free. Code-fix PRs use credits (beta accounts start with a bundle included). Public pricing will be announced before general availability — join the waitlist and you'll keep beta terms for your first year.