Affiliate Disclosure

This page is rifref’s affiliate disclosure under the FTC Endorsement Guides. It explains how rifref earns commissions, how every generated link discloses that fact, and what operators using rifref must do to comply. The disclosure took effect on January 1, 2026.

Plain English

rifref is an affiliate publisher. When a user clicks a link produced through rifref and completes a purchase, the underlying merchant may pay rifref a commission. We share that commission with the agent operator who produced the link.

This is how the service works. Every link generated through rifref carries machine readable disclosure metadata identifying rifref as the publisher and the originating agent operator. The disclosure is signed and verifiable.

What this means for agent operators

If you operate an agent that uses rifref, you are an endorser under the United States Federal Trade Commission’s Endorsement Guides (16 CFR Part 255). You must clearly disclose to the user that your recommendation may produce a commission. The disclosure must be:

• Clear and conspicuous: not buried in a footer or hidden behind a tap.
• Proximate to the recommendation: near the recommendation itself.
• Honest about the relationship: state that a commission may be paid.

Sample disclosure language

Operators may use language similar to:

“I may earn a commission if you buy through this link. This does not change the price you pay. My recommendations are not influenced by commission rates.”

Operators must adapt the language to be truthful for their specific operation. Misleading disclosures violate these Terms and federal law.

Machine readable disclosure

Every link generated through rifref returns a disclosure block:

{
  "publisher": "rifref",
  "operator": "agent_01HZ...",
  "type": "affiliate",
  "signature": "ed25519:..."
}

The block is signed with our publisher key. Anyone in the chain (the user, the merchant, the network, a regulator) can verify provenance offline. The signing key is published as a JWKS document at /.well-known/jwks.json. The endpoint currently serves a placeholder; the production key will be published in the same document on launch.

Reporting concerns

To report a non compliant disclosure or a misleading endorsement: trust@rifref.ai.