Skip to content

Correct BrainBurst support FAQ: remove unsupported billing and offline claims - #112

Merged
appdevelopsk merged 3 commits into
mainfrom
fix/brainburst-support-truth-20261113
Nov 12, 2026
Merged

appdevelopsk merged 3 commits into
mainfrom
fix/brainburst-support-truth-20261113

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

Why

A publicly crawled BrainBurst support page showed generic payment restoration, iOS subscription cancellation and offline-functionality statements that have not been verified against this app's shipped Android build. These claims are not an appropriate acquisition landing experience.

Changes

  • Remove only the three unsupported FAQ rows (restore purchases / cancel subscriptions / offline guarantee).
  • Remove the 6 now-unused FAQ localization keys in all 17 JS dictionaries (102 values), retaining the legitimate crash-help, language-support and contact FAQs.
  • Add a dependency-free Node regression test to keep removed claims out of HTML and translations and preserve actual Android Play store links, canonical and GA4 download-click event.

Verification

  • Read back both files from the GitHub branch and execute 32 source-level invariants: all passed, including 17-language retained keys and store/analytics integrity.
  • main...branch shows 2 files only, 0 commits behind.
  • Node runtime, full browser/localization QA, GitHub Actions and actual production host have not been verified. Do not infer deployment or improved GSC clicks from merge alone.
  • Existing site deployment/GA4 issue P0: verify appdevelopsk.com growth changes live and GA4 before acquisition rollout #51 remains open.

Release

On authorized checkout run node --test scripts/test_brainburst_support_faq_20261113.cjs plus the existing support/SEO test suite. Then publish only using verified hosting origin and check actual public page. No store or subscription configuration changed.

@appdevelopsk
appdevelopsk merged commit 11dddf3 into main Nov 12, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant