JMB Google Play readiness
A release-readiness checklist for JMB's Trusted Web Activity app package and Google Play listing.
Play policy and account readiness
Google Play Console access
Use an organization-owned Google Play Console developer account with verified business details and a recovery contact.
App identity
Reserve the permanent package name co.za.jirehmb.app and public listing name JMB before creating the first production release.
Store declarations
Complete the Data safety form, content rating questionnaire, target audience declaration, app access instructions, and ads declaration using verified product facts.
Privacy and data protection
Public privacy policy
Publish a clear, publicly accessible privacy policy that explains account, identity-verification, payment, device, and support data handling.
In-app privacy access
Link to the privacy policy from the app experience and provide a clear way for members to request account or data deletion where applicable.
Data safety accuracy
Declare only data actually collected or shared by JMB and its approved providers, including authentication, FICA verification, payments, analytics, and support services.
Financial-services and member-benefit disclosures
Verified legal identity
Publish Jireh Mutual Benefits' official company identity, contact details, and any applicable regulatory or licensing information before release.
Benefit terms
Make funeral cover, vouchers, rewards, founding-member eligibility, and any share-related statements subject to approved written terms, underwriting, and eligibility rules.
Payments and trials
Clearly disclose the monthly contribution, one-month trial conditions, renewal timing, cancellation process, and Ozow payment handling before a member starts checkout.
No unverified promises
Avoid presenting benefits, returns, allocations, or financial outcomes as guaranteed unless they are contractually approved and independently supportable.
Trusted Web Activity release checklist
Lock the Android identity
Use the permanent application ID co.za.jirehmb.app and the public app name JMB consistently across the Android project, signing configuration, Digital Asset Links, and Play Console record.
Build the signed Android App Bundle
Create a release AAB from the Trusted Web Activity project, keep the upload key protected, enroll in Play App Signing, and record the signing certificate SHA-256 fingerprint supplied by Play.
Publish Digital Asset Links
Serve https://jirehmb.co.za/.well-known/assetlinks.json over HTTPS with the Android package name and Play signing certificate SHA-256 fingerprint, then validate the relationship before testing the app.
Verify the trusted web experience
Confirm the production site is HTTPS-only, opens without browser chrome after verification, handles deep links safely, and provides a clear fallback if verification is unavailable.
Create the Play Console release
Create the JMB app record, upload the signed AAB to internal testing first, add release notes and tester access, resolve pre-launch findings, then promote through closed testing and production when ready.
Release quality and security
Secure member access
Test sign-in, sign-out, session recovery, FICA gating, and protected member areas on Android devices before submission.
Payment lifecycle testing
Validate Ozow callback signatures, duplicate callbacks, failed payments, cancellations, trial expiry, and renewal transitions in a controlled environment.
Trusted Web Activity verification
Publish and verify Digital Asset Links for jirehmb.co.za so the Android package can securely open the verified web experience.
Support and incident path
Provide a monitored support email or contact route for account, payment, privacy, and member-access issues.