Trust & Governance
RTH spans education, publishing, community impact, research development, youth resources, commerce, and responsible technology. Each area carries different responsibilities. This center explains the public principles RTH uses to keep evidence, privacy, accessibility, youth protection, entity responsibilities, and technology claims appropriately separated.
Core principles
RTH collects only information appropriate to the public workflow being used. General website forms are not intended for medical records, personal health information, emergency requests, or unnecessary sensitive information about children.
RTH distinguishes established guidance, peer-reviewed evidence, RTH synthesis, founder observation, hypotheses, prototypes, and validated results. Claim strength should never exceed evidence strength.
RTH technology is designed around provenance, uncertainty, bounded automation, task-specific validation, and human review. The planned RTH-owned LLM will require documented training-data rights, dataset and model records, adversarial and domain evaluation, release approval, monitoring, rollback, and retirement controls before external use.
Youth-facing pathways prioritize age-appropriate education, adult-supported contact, data minimization, strengths-based participation, and separation of children’s educational activities from health-data processing.
The public site targets WCAG 2.2 Level AA and is designed around keyboard access, visible focus, readable contrast, responsive reflow, reduced motion, semantic structure, and a practical path to report barriers.
Commercial activity, community-impact activity, research development, educational content, and technology development are not treated as interchangeable. RTH identifies the responsible pathway and preserves the limitations appropriate to each.
One ecosystem, different responsibilities
A book purchase, a child-facing lesson, a research hypothesis, a community program, and a technology workflow do not create the same risks. RTH applies different controls according to the activity, audience, data, intended use, and level of consequence.
Public education
Educational content should be understandable, sourced where appropriate, accessible, and clear about the difference between general education, lived experience, and professional advice.
Commerce
Commercial transactions belong to the applicable RTH LLC pathway and should use accurate product status, pricing, fulfillment, return, privacy, and payment disclosures.
Community impact
Community-impact and charitable activity is separated from commercial transactions. Dedicated nonprofit pathways should clearly identify giving, volunteering, programs, accountability, and receipting when those functions are available.
Science & research
The Neurocardiac Model is presented as an evidence-informed, hypothesis-generating framework. Research questions, founder observations, methods, and validated findings must remain distinguishable as the evidence base develops.
Responsible technology
SuperstarIQ remains in development and validation. Public positioning does not authorize diagnosis, treatment, prediction, emergency monitoring, implanted-device interpretation, or return-to-play decisions.
Children & schools
Youth materials use age-appropriate education and participation rather than medical, mental-health, character, worth, or resilience scoring. Child-sensitive information is minimized and separated from general public forms.
Governance 2.0
RTH separates general website policy from product privacy, consumer-health requirements, AI/model governance, connected-source permissions, research, youth safeguarding, vendors, and operational procedures. A prelaunch notice defines the controls required before a future capability is enabled; it does not claim that the capability is already active.
Product privacy
Prelaunch product privacy, health-data separation, user-directed sharing, AI processing, rights, and future regulated-workflow boundaries.
Health data
Sensitive health and wearable information, consent, no-sale/targeted-advertising baseline, retention, rights, and health-breach response.
AI & own LLM
Product processing is separated from model training. The planned RTH-owned LLM requires training-data provenance, evaluations, human-review rules, model transparency, monitoring, rollback, and retirement.
Connected sources
Source-level permission, provenance, disconnection, provider restrictions, and explicit limits on model training or evaluation.
Youth
Adult-youth communication, media, programs, reporting, schools, and an adult-first rule for personalized AI involving sensitive context.
Research
Separates product beta work from human-subjects research and establishes consent, IRB, safety, vulnerable-population, model-development, and publication controls.
Training and model development
RTH distinguishes inference, retrieval, personalization, optional research, model evaluation, fine-tuning, and model training. Ordinary product use does not silently become consent to train a general-purpose RTH model. Identifiable health data and identifiable minor/student data are excluded from general-purpose model training by default, and connected-source restrictions continue to apply even when a user would prefer a broader use.
Research and claims
The founder’s longitudinal experience is an important origin point for RTH, but founder observations are labeled as observations. Population-level conclusions require appropriate evidence, methods, validation, professional review, and—where applicable—research and regulatory oversight.
Operational reporting channels
Role-based mailboxes keep privacy requests, security reports, and general correspondence separated so each can follow the appropriate review and recordkeeping process.
Privacy & data rights
Use for privacy questions, correction/deletion requests, youth-privacy concerns, and questions about public-site data practices. Avoid sending unnecessary sensitive information by ordinary email.
Security reporting
Use for suspected vulnerabilities or security incidents. This reporting channel does not authorize testing, access, disruption, retention, or disclosure of RTH systems or data.
Neither mailbox is an emergency, medical-advice, or clinical-support channel. General RTH questions should use the Contact page. Contact RTH →
Public governance center
The Policy Center is the authoritative index for current website rules and future-ready product, health-data, AI, youth, research, security, and commerce notices. Prelaunch pages describe required controls without implying the feature is already live.
Current public-site data practices and product-data separation.
Access, correction, deletion, portability, verification, agents, and appeals where applicable.
Purpose-based lifecycle rules, backups, de-identification, and legal holds.
Vendor due diligence, data-use limits, and the future SuperstarIQ subprocessor register.
Security reporting, testing limits, triage, and sensitive-data handling.
Child-facing content, adult-facing data collection, and no child scoring.
WCAG 2.2 AA target, release QA, alternatives, and future independent assurance.
The complete layered RTH Governance 2.0 policy index.
