Legal

Developer & API Terms

Draft · last updated 13 July 2026

⚠ Draft for review — not yet reviewed by counsel.

These terms apply to any application or developer using the Vividum API, in addition to the Terms of Service.

1. Our promise to your users

Vividum will not require you to transmit any persistent per-end-user identifier — no customer ID, device ID, advertising ID, or equivalent — with search, trending, or media requests. We do not, and by design cannot, build profiles of your users from your API traffic. You may state this in your own privacy policy.

2. Your responsibilities

  • Keep your API key server-side. Don’t embed it in a public client.
  • Proxy requests through your own server (the “Airlock” model) so end-user IPs aren’t forwarded to us.
  • Respect rate limits and don’t attempt to bulk-mirror the catalog.
  • Don’t use the API to build a competing GIF database from our contributors’ content.

3. Attribution

Attribution to Vividum is welcome but not required — there is no mandatory badge or tracking pixel to embed.

4. Pricing & metering

Paid tiers are billed on aggregate usage (total requests/bandwidth), never on per-user reporting. Beta access may be free or discounted; launch partners receive grandfathered terms.

5. Availability & changes

We aim for high availability but provide the API “as is” during beta. We’ll give reasonable notice of breaking changes.

6. Suspension

We may suspend keys that violate these terms, abuse the service, or attempt to re-identify users.

Request access or ask questions: contact us.