Humanitarian Aid App Store Metadata and Privacy Policy Validator
Creates a Python validation script to inspect store metadata, localized strings, and permission privacy compliance for NGO apps.
Use this template when preparing mobile applications for international aid and relief operations. It produces an executable Python CLI script that audits localized store descriptions and manifest permissions against strict privacy and data protection mandates.
Role: Principal Humanitarian Mobile Compliance Engineer.
Context
- NGO Program Name: {{ngo_program_name}}
- Required Locales: {{target_locales}}
- Distribution Platforms: {{store_platforms}}
- Data Sensitivity Classification: {{data_sensitivity_tier}}
- Privacy Policy Link: {{consent_policy_url}}
- Whitelisted Permissions: {{allowed_device_permissions}}
Task
Author a standalone Python validation script that audits App Store and Google Play metadata directories, verifies localized privacy disclosures for {{target_locales}}, and checks native manifest permissions against {{allowed_device_permissions}} for {{ngo_program_name}}.
Method
- Define configuration data structures incorporating {{data_sensitivity_tier}} rules and accepted values.
- Write metadata parsing logic to traverse localized store assets (description, keywords, privacy URLs) for all entries in {{target_locales}}.
- Implement regex and HTTP verification checks ensuring {{consent_policy_url}} resolves and contains required non-profit data protection clauses.
- Build native manifest parsers (
AndroidManifest.xmlandInfo.plist) to scan all requested hardware and runtime permissions. - Compare extracted permissions against {{allowed_device_permissions}}, flagging any unapproved location, contact, or telemetry access.
- Generate structured compliance scoring tailored to {{store_platforms}} requirements.
- Add CLI arguments (
argparse), structured exit codes (0 for pass, 1 for fail), and automated markdown report emission. - Embed clear remediation suggestions in the terminal output for any failing check.
Constraints
- MUST be written in standard Python 3.10+ using only standard library modules to ensure zero-dependency CI execution.
- MUST NOT permit builds to pass if undeclared permissions outside {{allowed_device_permissions}} are detected.
- The script must validate URL reachability using non-blocking connection timeouts.
- Error outputs must highlight exact file paths and line mismatches.
Output format
- Script Overview and Dependencies
- Complete Executable Python Script (
validate_store_compliance.py) - Sample Configuration File (
store_compliance.json) - Integration Instructions for Pre-commit and CI Pipelines
Self-review
- Ensure all variables (including {{ngo_program_name}} and {{consent_policy_url}}) are properly bound within the script logic.
- Verify standard library compliance (no unlisted pip packages required).
- Check that both iOS Info.plist and Android AndroidManifest.xml validation paths are fully implemented.
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.