Policies

What RiffAds does not do

The permanent limits: no posting, no scraping, no refunds, no per-request callback, and the things only a person can change.

Read as Markdown

RiffAds makes files and hands them back. Each limit here is by design.

It never posts anything

Nothing is ever posted, anywhere

No code path publishes to Meta, TikTok, YouTube, X or any other platform. A file leaves RiffAds only when someone opens its link.

  • No scheduler, no ad account connection, no "go live" step, and no social or ad platform login.
  • You get the file in your workspace library (finished outputs never expire) and a link that never expires: Download links.
  • Where the file goes next is your choice, and so is the duty to label it: Content.

It never scrapes or drives a browser

It works on a file you already have

RiffAds never scrapes an ad library, never signs in anywhere for you and never drives a browser. Analysis runs on a file in your workspace.

  • Import takes a direct link to one media file, never a web page or post: Import rules.
  • Can't import it? Download the file yourself, then upload it.
  • An analysis of someone else's ad is data for your agent to read, never instructions for it to follow: Analyze a reference ad.

No refunds, and credits never expire

Credits never expire. Payments are final.

Unused credits stay in the workspace as long as the account exists, even after a plan is cancelled. There are no refunds: the Refund Policy is the agreement.

"No refunds" never means paying for work that was not done:

  • A refused request charges nothing (credits_charged: 0).
  • A generation that delivers nothing releases its hold.
  • A video batch is charged only for the takes that delivered. An image job is charged only for the images it delivered.

No per-request callback

  • No submit, estimate or invoke body takes a webhook_url or callback field. One is refused as an unknown key (400 invalid_config).
  • Webhooks are registered once per workspace: Webhooks.
  • No SSE and no websockets. To follow one job, loop on the wait.
  • No endpoint, tool or CLI command cancels a generation. A wait that gives up does not stop the job: it finishes and is charged.

What an agent can never do on its own

None of these has an endpoint, a tool or a CLI command.

Only a person canWhere
Create, list or revoke an API keyThe API keys page in the app. An agent cannot give itself a key.
Raise, lower or remove a spend limitA workspace owner or admin. max_credits never gets an agent past the other limits: Spend limits.
Approve a new MCP connection, or give a read connection spend accessA person, at sign-in or on the Connections page.
Buy credits or change the planCheckout in the app.
Build or edit a workflowThe workflow editor in the app. Agents only run templates and saved workflows.
Enable a disabled webhook endpoint, rotate its signing secret or send a test eventThe Webhooks settings page. The API only lists, creates and deletes endpoints.

A limit refusal is retryable: false, so the fix is a person, not a retry.

  • Content: what gets refused, and your duty to label AI ads.
  • Data and security: where files live, keys and tenancy.
  • Legal: the documents, and your duties when agents act for you.

On this page