01 / GOVERNMENT AUTHORITY
Claims, intended use, and enforcement context
RUO Clear prioritizes official and primary sources, preserving their type, date, status, applicability, and review history.
FTC staff guidance on express and implied health claims, net impression, disclosures, endorsements, and substantiation.
Regulatory text describing objective intent and relevant evidence. Applicability remains a fact-specific legal question.
A fact-specific warning letter discussing human-use signals despite RUO wording. It is not a statute or universal outcome.
02 / PRIVATE PROVIDER POLICY
Payment rules are contractual and time-sensitive
Processor and platform policies are private rules, not law. They can change and may be applied differently based on products, countries, business model, and account facts.
Current private policy categories and conditions. Inclusion never predicts approval for a specific merchant.
Support guidance addressing restricted categories, including account-specific review and changing program requirements.
03 / INTEGRATION DOCUMENTATION
Platform controls have their own sources
WordPress and Medusa connector findings must distinguish platform requirements from RUO Clear recommended controls and merchant-specific configuration.
04 / CHANGE LOG
Freshness, withdrawal, and corrections remain visible
Every source record requires a status, verification date, owner, content hash, and re-review interval. Stale, superseded, or applicability-uncertain sources fail closed rather than silently supporting a conclusion.