A pending termination citing both Section 3.2(f) and Guideline 5.6.2 is broader than an ordinary request for an identity document. Apple may be investigating whether the legal entity, account holder, application owner, service operator and information presented to customers are consistent and verifiable.
Since you submitted the appeal within the stated deadline, preserve proof of submission: the confirmation screen or email, exact timestamp, Apple ID, Team ID and the complete text of your appeal. Six days without a decision does not necessarily mean that the appeal was not received.
I would not submit duplicate appeals or change any account details while the investigation is pending. Instead, contact Developer Support under case 102979575702 and ask them to confirm that the appeal was received and provide a secure channel for your supporting documents. Do not post identity, tax, banking or company records publicly.
Prepare one indexed evidence package covering the following:
-
The exact legal name, address and registration number of RAYAAUSTIN LLC.
-
Evidence that the Account Holder is authorized to represent and legally bind the company.
-
Consistency between the company’s D‑U‑N‑S record, IRS records, bank account and App Store Connect information.
-
Consistency between the App Store developer name, support website, privacy policy, domain registration and customer-support email.
-
Ownership of the LightXtreme name, icon, source code, backend and VPN infrastructure.
-
Every employee, contractor or development agency that had access to the source code, certificates or App Store Connect account.
-
Any previous developer account, transferred application, purchased codebase, white-label component, related company or shared technical infrastructure.
-
The identity of the company that actually operates the VPN servers, processes subscriptions and handles user data.
For every item, state the name currently shown, the person or company that controls it, the supporting document and any discrepancy you discovered. This provides the same clarity as a table without requiring one.
Because this is a VPN application, include a separate section confirming that the account is enrolled as an organization, the app uses NEVPNManager, users receive a clear data-use disclosure before purchasing or using the VPN, and the privacy policy identifies the actual VPN operator and describes all data flows. Also confirm that VPN-derived user data is not sold, used or disclosed to third parties and identify any territorial VPN licences that may be required.
Do not state only that all documents match. Compare every field carefully. A trading name instead of the LLC name, an individually owned domain, a different company named in the privacy policy, a contractor-controlled backend or a reused VPN codebase may all be relevant.
I would send Apple this focused follow-up:
“We submitted our termination appeal on [date and time] regarding Team ID [ID] and Apple ID [ID]. Please confirm that it was received and remains under review.
We understand that the cited provisions may concern consistency between our legal entity, Account Holder, application ownership, customer-facing identity and VPN service operations.
We have prepared an indexed verification package covering company registration, Account Holder authority, D‑U‑N‑S, tax and banking records, domain and privacy-policy ownership, source-code provenance, contractors, backend and VPN infrastructure, and all potentially related developer accounts. Because these records contain sensitive information, please provide the secure channel through which the team handling the appeal wants them submitted.
If possible, please also identify the category of the outstanding concern: legal-entity information, Account Holder authority, application or source-code ownership, related-account association, customer-facing identity, or VPN service operation. This will allow us to address the issue precisely.”
If you discover a genuine inconsistency, disclose it directly, explain how it occurred and provide a dated correction plan. If no inconsistency exists, present the documents as a factual rebuttal rather than making a generic promise to improve.
Do not create another developer account, transfer the application, replace the Bundle ID or ask another company to resubmit it. Those actions could reinforce the identity or account-association concern.
