Policies

Data and security

Where your files live, what is kept, how keys are stored, and who to tell about a leak.

Read as Markdown

What RiffAds stores, how long it keeps it, and how to keep your keys safe.

Where files live

  • Outputs are copied into RiffAds storage (Cloudflare R2) when a job finishes. Provider links are never stored or returned.
  • Every file sits under your workspace, which comes from your key or connection, never from request input.
  • Files are private in storage. Outside the app, a file opens only through its link, and RiffAds checks the link and the file on every visit.
  • Finished outputs never expire. Nothing is ever posted anywhere: What RiffAds does not do.

Every file has one link, url, on every surface. It never expires and opens for anyone who has it, with no sign-in. So share it only where you would share the file itself.

  • The link opens that one file and nothing else. Knowing a file's id is not enough: the link carries a key made for that one file.
  • Deleting the file from your library turns its link off.
  • There is no second, short link: Download links.
  • A webhook delivery carries each file's link. It never expires, so it still works on the last retry.
  • Upload links are different: the signed link you PUT a file to lasts 5 minutes. Every lifetime: Limits.

What else is kept

ThingKept
Generation recordsKept. Deleting a project does not delete its generations or outputs.
Content check recordA SHA-256 fingerprint of the input, never the words.
Abandoned upload reservationCleared after 15 minutes.
Revoked API keyDisabled, never deleted, so history shows which key started which job.

There is no self-service workspace deletion.

API keys

  • Shown once. Only a hash is stored, so nobody can recover a lost key. Revoke it and create another.
  • Live only. No test keys and no sandbox.
  • Never expire. Revoke to stop one.
  • Made in the app. Owners and admins create and revoke keys at app.riffads.com/api-keys. No endpoint issues a key.
  • Name a workspace, not a person. For per-person tracking, give each person or system its own key.
  • No IP allowlist. The key is the whole credential.

Revoking works on the very next call. Work already running still finishes and is charged.

Keys belong on servers

Never put sk_live_... in browser code, mobile apps, public repos, CI logs or chat prompts. Whoever reads it can spend until it is revoked.

Webhook signing secrets

  • Shown once, in the answer that registers the endpoint (whsec_...).
  • Stored encrypted, not hashed, because RiffAds signs every delivery with it.
  • Lost or leaked? An owner or admin rotates it on the Webhooks settings page: Webhooks.

No CORS on the REST API

/api/v1 sends no CORS headers, on purpose. Call it from a server, task runner, CI job or terminal.

MCP allows CORS, because its token comes from an OAuth sign-in, not a secret key. MCP setup.

CLI key file

riffads login saves ~/.riffads/config.json with mode 0600. RIFFADS_API_KEY in the environment wins over the file.

riffads logout deletes the file only, so the key works until you revoke it. CLI setup.

Read-only access

A key without the generate or workflows scope can read and estimate, never start work. A read-only MCP connection does not see the spend tools.

Tenancy

  • REST: no workspace parameter or header. The workspace comes from the key.
  • MCP: the token is a person, bound to one workspace and checked again on every call.
  • Another workspace's id and a missing id both return not_found, so nobody can probe what exists.

What never leaves the server

  • Provider names, model keys, prompts, signed URLs and stack traces never appear in an error.
  • Card numbers never reach RiffAds. Checkout runs on the payment provider's hosted page.

Report a problem

Leaked key: revoke it in the app first. It stops on the next call.

Privacy or security report: use the contact address in the Privacy Policy.

On this page