Skip to content

Trust documentation · 3 of 4

Timing • Reporting • Confidentiality • Responsibilities

The operating commitments behind the partnership.

This page is the public-facing view of how the relationship runs once work begins: what gets acknowledged when, how reporting works, where confidentiality applies, and how quality and replacement obligations are handled.

Executive summary

The core commitments most buyers check before legal review.

Acknowledgment

1–2 business days

Orders and covered issues are acknowledged on documented timelines.

Delivery

Tier-based timing targets

Initial delivery timing varies by package complexity and sourcing difficulty.

Confidentiality

White-label by default

The partner relationship stays behind the curtain unless agreed otherwise.

Reporting

Structured delivery records

Live URLs, anchor details, dates, and coverage context are documented for each placement.

Use this page for

Operational diligence

Read this when legal, operations, or procurement wants the relationship terms in plain English.

Read first

Sections 1, 2, 4, and 5

Those sections explain scope, timing, confidentiality, and reporting expectations.

Best next page

Refund policy

Finish the diligence path with the page focused on cancellations, credits, and remedy boundaries.

1) Scope of services

This agreement covers the white-label fulfillment relationship: publisher sourcing, content coordination, placement delivery, post-publication monitoring, and covered replacement handling where applicable.

It does not convert Referral Authority into the visible client-facing agency unless separately agreed. The default model is partner-behind-the-scenes fulfillment.

2) Delivery timing

Timing depends on package tier, publisher difficulty, and niche complexity, but the baseline commitments are:

  • Order acknowledgment: within 1 business day
  • Covered-issue acknowledgment: within 2 business days
  • Replacement target: within 15 business days of acknowledgment
  • Credit fallback: within 30 business days if no comparable replacement is secured

Exact delivery windows can vary by tier and niche. The point of the SLA is to document the response standard, not pretend every placement lives on the same timeline planet.

3) Quality and replacement alignment

The SLA does not redefine quality independently; it works alongside the Editorial Standards and Domain Auditing Methodology. Those pages establish the quality floor and approval logic this agreement operationalizes.

Covered removals, degradation, and comparable replacement logic are coordinated with the standards page and the Refund Policy.

4) Confidentiality and white-label rules

By default, the relationship is white-label. That means:

  • Referral Authority does not contact partner end clients directly unless authorized.
  • Partner identities, client lists, and campaign specifics are treated as confidential.
  • Deliverables are structured for easy agency-side branding and presentation.
  • Neither side should publicly use the other’s identity or marks without permission.

5) Reporting expectations

Each completed placement should be documented clearly enough that a partner can review, present, and archive the work without interpretive gymnastics.

  • Live URL
  • Publisher domain
  • Anchor text
  • Publication date
  • Package-relevant quality context at time of placement

6) Data and compliance handling

Only the minimum practical data required for service delivery should be processed. Referral Authority is not asking partners to dump end-client customer databases into the workflow like it is trying to collect trading cards.

Where applicable, controller/processor responsibilities, deletion expectations, breach notice timing, and compliance obligations should be governed by the executed agreement and any required DPA.

7) Termination and transition

Either side may end the working relationship under the agreed contract terms. The important transition principles are straightforward:

  • Accepted in-progress work should be completed under the governing terms unless the agreement says otherwise.
  • Covered replacement obligations on already-delivered placements continue for the active protection window.
  • Relevant data should be returned or deleted according to the executed agreement and applicable law.

8) Liability and dispute handling

Commercial relationships work better when neither side discovers the dispute rules during the dispute. This page is not a substitute for legal review, but it reflects the operating intent: first attempt good-faith resolution, then move through the agreement’s documented escalation path if needed.

This page is a public-facing summary of standard operating commitments and is informational. Executed agreement terms govern where more specific language applies.