Trust center
How Pocket Orbit researches, tests, and corrects content
Our goal is not to publish the most claims. It is to make each important claim inspectable, dated, limited, and connected to the workflow that supports it.
Published and last reviewed: 29 July 2026
1. Validate the search intent
We review the dominant result type, recurring authorities, related searches, People Also Ask questions, and whether the query expects a feature page, guide, comparison, help article, or original research.
2. Write the page brief
Every authority page receives a keyword, cluster, funnel stage, SERP intent, authority patterns, evidence requirements, source list, internal links, schema plan, owner, and refresh date.
3. Test the actual workflow
Pocket Orbit claims are checked in the current app. Comparisons disclose the review date, device context, official sources, use-case strengths, and limitations.
4. Preserve failures and limits
Recognition mistakes, correction effort, missing capabilities, and category boundaries belong next to the benefit. We do not turn a successful demo into a universal performance promise.
5. Connect the evidence
Feature pages link to guides, exact help, comparisons, resources, and research. Supporting pages link back to the relevant product proof and to sibling explanations.
6. Refresh from evidence
Pages are reviewed after product changes, competitor changes, pricing updates, material search-intent shifts, or meaningful user feedback. The visible update date is changed only after a real review.
Comparison policy
We use official competitor sources for current feature and pricing claims. Original screenshots and device tests are added when permission and production evidence are available.
Comparisons name use-case winners instead of declaring one universal winner. Review access does not require positive coverage, and affiliate or sponsored relationships must be disclosed on the page.
Pocket Orbit is our product. That conflict is explicit, which is why primary sources, visible limitations, test dates, and reproducible resources are part of the format.
Source and correction policy
We prefer first-party product documentation, official store listings, support documentation, and original tests. Secondary sources are used for perspective, not to override an official current claim.
Send a correction with the page URL and supporting source to alpaca-labs.dev@proton.me. Material corrections are reviewed, changed in the page, and reflected in its update date.
Research stays noindex until the promised raw observations and limitations exist. VideoObject schema is emitted only for a real, visible video with its final URL, caption context, poster, and publication date.