Nonprofit Mobile Donation Exemption and Store Policy Brief
Structure a formal app store exemption brief for tax-exempt charitable donations and fundraising flows.
Use this template when launching or updating a nonprofit mobile app that accepts charitable donations. It helps developers establish compliance with Apple Guideline 3.2.2(iv) and Google Play financial transaction rules.
Role: Mobile Policy and Nonprofit Compliance Architect.
Context
- Nonprofit legal entity: {{nonprofit_entity}}
- Fundraising mechanism: {{fundraising_mechanism}}
- Target app stores: {{target_app_stores}}
- Financial compliance status: {{tax_exempt_status}}
- Core app utility: {{app_utility}}
- Third-party payment gateway: {{payment_gateway}}
Task
Generate a store policy compliance brief justifying in-app donation exemptions under Apple App Store Review Guideline 3.2.2(iv) and Google Play Payments Policy for {{nonprofit_entity}}.
Method
- Analyze {{target_app_stores}} guidelines governing charitable contributions, fundraising, and in-app purchase exemptions.
- Validate {{tax_exempt_status}} documentation requirements for nonprofit developer account verification.
- Dissect {{fundraising_mechanism}} to ensure donation flows bypass standard digital goods IAP pipelines via {{payment_gateway}}.
- Separate {{app_utility}} features from pure donation collection to maintain required standalone mobile utility.
- Draft the formal exemption request narrative intended for the App Review Board and Google Play Policy Operations.
- Specify user experience guardrails to ensure safari/web-view donation handoffs adhere strictly to platform merchant policies.
- Define verification proof packs including official public registry links and payment processing statements.
Constraints
- MUST reference specific platform guidelines including Apple Guideline 3.2.2(iv) and Google Play Financial Services terms.
- MUST NOT suggest using native in-app purchases for tax-deductible direct charitable contributions.
- Keep compliance rationale auditable, objective, and defensible.
- Limit technical architecture mentions solely to payment gateway routing and user interface handoffs.
Output format
Deliver a store compliance brief in 4 labeled sections:
- Nonprofit Developer Profile & Exemption Scope (max 150 words)
- Payment Architecture & Fee-Exemption Justification (annotated flow explanation)
- App Review Submission Narrative (verbatim submission text, max 300 words)
- Compliance Checklist & Audit Evidence (bulleted checklist of 6-8 required artifacts)
Self-review
- Is the legal exemption justification sound under current Apple and Google terms?
- Does the payment flow clearly isolate donations from digital goods purchases?
- Is the submission narrative ready to paste directly into review correspondence?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.