App Review Notes for a crypto exchange: the template that carries your evidence
App Review Notes are the free-text field in App Store Connect that reviewers read before opening any attachment. For a crypto exchange, effective notes follow a fixed structure: who operates the app → where it is available → the legal basis → the demo account → the attached documents, each mapped to the guideline that was cited. Good notes turn a legal pack into an approvable submission.
Why Review Notes decide the outcome
Reviewers process large queues and are not lawyers. If your notes force them to reconstruct your compliance story from raw attachments, the practical result is another form rejection. The notes must do the reviewer's work for them: state the conclusion, map the evidence, remove every open question.
The template, annotated
1 · Operator. This app is offered by ████████ Ltd., the operator of the ██████ exchange. The developer account is held by the operating entity. (Registry extract attached.)
2 · Availability. The app is distributed only in the XX storefronts listed in Country_Availability_Statement.pdf. All other storefronts are deselected.
3 · Legal basis. Licensing, registration and exemption analysis for each region of availability is set out in Legal_Opinion.pdf (summary on p.1; region table in section 3). This responds directly to Guideline 3.1.5.
4 · Demo account. Credentials: ████████ / ████████. KYC pre-approved; all features accessible from the review region; test funds loaded.
5 · Previous rejection. This submission responds to the ██/██ rejection under 3.1.5 by adding the documents above. No other functionality changed.
The five mistakes that get notes ignored
- Apologizing or arguing. "We believe this rejection was unfair…" belongs in an appeal, never in notes. Notes state facts and map documents.
- Wall of text. Over ~1 page unstructured, reviewers skim and miss the one line that mattered. Numbered blocks, one topic each.
- Documents without a map. Attaching five PDFs without saying which answers which guideline forces the reviewer to guess. Reviewers don't guess in your favor.
- A demo account that fails. Expired credentials or geo-blocked access is an instant rejection regardless of your legal pack. Test it from a foreign IP before submitting.
- Inconsistency. An entity name in the notes that differs from the opinion or the app metadata reopens the identity question you were trying to close.
Want the full annotated template (with the region table format and attachment naming convention)? We send it free on Telegram — or we rewrite your notes for you as part of the submission pack.
Get the full template →Pre-submission checklist
Frequently asked questions
Where do I put App Review Notes in App Store Connect?
In the App Review Information section of your version submission — the Notes free-text field, plus the attachment slots and the demo account fields next to it.
How long should Review Notes be for a crypto exchange app?
About one structured page. Long enough to map every document and close every 3.1.5 question, short enough that a reviewer reads all of it. Push detail into attachments.
Do Review Notes replace the legal opinion letter?
No. Notes are the argument; the opinion is the evidence. Notes without documents read as unsupported claims, and documents without notes usually go unread.
Can you write the Review Notes for us?
Yes — a Review Notes rewrite is part of every CexPass submission pack, built from your legal opinion and availability statement so the whole file reads as one consistent story.