360° SCD Hub — Response to Board Technical Review

The GitHub repository holds the native app wrapper, which by design changes rarely. The platform itself — content, courses, gamification, community, and the health trackers — lives and is maintained in the WordPress/plugin layer, exactly as presented and accepted at the move-to-maintenance milestone. A repository showing limited change is the expected signature of this architecture, not a sign the platform has been static.

These build-and-deploy instructions were provided to SCFA at the move-to-maintenance handoff in April 2024. Beyond that, the platform ships with BuddyBoss’s own continually-updated documentation — available in WP Admin → BuddyBoss App → Help → Documentation (App Setup, connecting the Apple & Google developer accounts, App Builds, and App Publishing) — which we pointed SCFA to from the outset and which covers the large majority of the steps to maintain the app and produce new builds. The consolidated runbook below, plus the updated Formal Build & Deploy Instructions due by end of month, complete the picture for your records.

To keep the SCFA team fully enabled under our active agreement, we will work directly with Moses and Ediye — including adding Ediye Akpan to the Google Play and Apple Developer accounts — to share and make transparent a single main access point, built from the original move-to-maintenance handoff deck and expanded to include the new custom plugins that power the LIVE It and Activity Trackers and the Executive Dashboard.

The list exists, and we tracked it: the November 2024 items are logged in our shared issues register, summarized in full below. Every item is now closed — ten are resolved in the rebuilt 360° Health Tracker, the build-instructions item was delivered at the April 2024 move-to-maintenance handoff, and one (landscape rotation) was reviewed and determined not technically feasible. For context, a number of issues over this period traced to BuddyBoss app releases; where we held a plugin update, it was a deliberate call to keep a known third-party defect out of users’ hands — the same “no errors in users experience” standard the clause sets, and the Force Majeure provision (§14) expressly recognizes supplier failures as outside either party’s control.

The gap reflects the two stores’ different requirements rather than a lapse. Google’s 2025 platform changes — the target-API-level update and the new 16 KB page-size requirement — forced fresh Android builds, while the iOS binary did not require an equivalent resubmission in the same window. The platforms are maintained continuously on the server side regardless of store-binary dates. It is also worth noting that iOS submissions run through the SCFA-held Apple Developer account; when that account required an update, the fix sat on the account-holder side and was completed in late June 2025 — a dependency that affects iOS release timing independent of our build work. That said, we agree the two should be brought back into sync.

We confirmed the live status directly in Google Play: the developer account shows no policy issues, and the only app-level item is the separate 16 KB warning — the health declaration was not flagged. To be thorough, on June 14, 2026 we re-submitted the Health apps declaration with accurate categories — Diseases & conditions management, Disease prevention & public health, Medical reference & education, Medication & treatment management, and Stress management/relaxation — plus a clarifying note that the 360° SCD Hub is an educational and self-management tool, not a medical-care solution. It is now in Google’s standard ~7-day review.

We responded to the Google notice and the deadline was extended to February 1, 2027. The 360° SCD Hub is in good standing and in compliance as of now — updates continue to release normally, and the Play Console confirms all apps are registered and meeting Android developer-verification requirements. We will add 16 KB page-size support in an app-bundle update before the February 2027 date. Separately, the app’s Android developer verification is complete — package com.scfaz.scdhub shows Registered in the Play Console (since March 5, 2026).

Good flag — and we already have a control in place. At onboarding, the 360° SCD Hub presents new users with an age-verification step and requires them to accept the Terms & Agreements before entering the app. That is precisely the developer-side duty SB 2420 contemplates: consuming the age and parental-consent signals the stores pass through, and gating how minors experience the app. We are already substantially aligned — not starting from zero.

Because this is a brand-new statutory regime that post-dates the original scope, we treated it as a forward-looking compliance item and have now completed a short SB 2420 Applicability Assessment (delivered alongside this log). It finds the Hub substantially aligned: the law’s primary duties sit with Apple and Google, our developer-side items are largely in place, and the remaining store-signal integration is folded into the current enhancement engagement. This isn’t new ground for us: our 2024 user-testing notes already flagged age-appropriate handling — for example, limiting maps for under-18 or guest users — so we begin with a running start.