Purpose and scope
This methodology explains how Pocket Genes handles scientific and educational information. It distinguishes provider-supplied report findings, Pocket Genes educational explanations, glossary content, organization-published content, user-generated community content, news, events, and external resources.
Pocket Genes does not present provider findings as independently generated Pocket Genes conclusions. When a report comes from a provider, the provider remains the source and authority for the findings and clinical interpretation.
Who this page applies to
- Users reading educational content or glossary explanations.
- Users accessing provider-connected reports through Pocket Genes.
- Trusted Organizations and publishers submitting educational resources.
- Providers and integrators using Pocket Genes to support post-result education.
Definitions
Provider finding
A result, interpretation, variant, panel, file, or conclusion supplied by the report provider.
Pocket Genes educational content
Content authored or curated by Pocket Genes to explain terminology, concepts, workflows, or general context.
Organization content
Resources, events, education updates, or posts attributed to a third-party organization.
Clinical interpretation
A medical or professional explanation of what a report means for diagnosis, treatment, screening, family planning, or clinical action.
Correction
A content update that fixes an error, outdated source, misleading simplification, or attribution problem.
Types of scientific information
- Provider-supplied report findings and informed-consent materials.
- Pocket Genes glossary definitions, lessons, and plain-language explanations.
- Organization-published articles, events, resources, and education updates.
- User-generated community posts, comments, questions, and experiences.
- News, event listings, external resources, and support materials.
Educational-content lifecycle
Topic selection
Topics are selected based on product workflows, common report concepts, user confusion, provider or organization needs, and safety value.
Source research
Drafting should use sources appropriate to the topic, such as government or public-health resources, recognized genetics databases actually used in the process, professional guidelines, peer-reviewed literature, provider public information, and standard scientific terminology.
Drafting and plain-language review
Content should explain concepts without changing source meaning, overstating certainty, or implying medical advice.
Scientific review and approval
Material that explains scientific or clinical-adjacent concepts should be reviewed by someone with appropriate genetics, scientific, clinical, or product-safety competence before publication.
Versioning and publication
Material changes should keep a version or review record when content is used in a regulated, informed-consent, provider, or safety-sensitive context.
Periodic review, correction, and retirement
Content should be reviewed on a cadence or when sources, terminology, guidelines, provider expectations, or product risk changes. Outdated content should be corrected, labeled, or removed.
Evidence and citations
Pocket Genes should cite or identify source categories when content makes scientific claims beyond basic definitions. Publication dates, guideline updates, source hierarchy, and conflicting evidence should be considered.
When evidence is uncertain, changing, or disputed, educational content should say so in plain language. Simplification should make content easier to understand without turning uncertainty into certainty.
Third-party organizations and user content
Trusted Organization content is attributed to the publishing organization and does not become Pocket Genes-authored scientific content merely because it appears in the app. Organization content must follow content, promotion, and safety standards.
User community content reflects personal experience or opinion unless clearly identified otherwise. Community content is not scientific review, medical advice, diagnosis, or treatment guidance.
Artificial intelligence
AI-assisted drafting, translation, summarization, categorization, or moderation support may be used only as an aid and should not publish scientific or clinical-adjacent content autonomously.
Human review is required before AI-assisted educational content is presented as Pocket Genes content. Errors can be reported through the Trust Center contact and should be corrected through the content-review process.
Clinical boundary
Users should contact the report provider, qualified clinician, or genetic counselor when a report raises questions about diagnosis, treatment, screening, medication, reproductive choices, family risk, urgent symptoms, or clinical next steps.
Pocket Genes responsibilities
- Separate provider findings, Pocket Genes education, organization content, and user content.
- Use sources actually reviewed for the content.
- Communicate uncertainty and source responsibility clearly.
- Review, correct, label, or retire outdated educational content.
User, provider, and organization responsibilities
- Users should use education to prepare questions, not to self-diagnose or self-treat.
- Providers remain responsible for report findings and clinical interpretation.
- Organizations are responsible for the accuracy, sourcing, labeling, and promotional transparency of their own content.
Exceptions and limitations
- Source availability, scientific terminology, and guidelines can change.
- Pocket Genes does not independently verify every provider report finding.
- External resources may be updated or removed by their publisher without notice to Pocket Genes.
How to make a request or report a problem
Privacy, account, deletion, accessibility, safety, trusted-organization, and security requests can be sent to support@goldencrowvs.com. Use a subject line that identifies the issue, the affected Pocket Genes account or workflow, and whether the request is urgent.
Pocket Genes may need to verify the requester before changing or disclosing account information. Verification is handled proportionally to the request, the sensitivity of the information, and the risk of giving account access or private information to the wrong person.
Effective date, version, and review history
| Item | Value |
|---|---|
| Effective date | August 14, 2026 |
| Version | 1.1 |
| Last reviewed | August 2026 |
| Material changes | Expanded Trust Center format, operator identity, data-map boundaries, request paths, and responsibility sections. |
| Previous version | July 2026 Trust Center overview copy. |