COURSE 25L1100% FREE
Verified 2026-08-14

Reading API service terms

A **literacy** method for reading vendor **service terms**, privacy centers, and product-term updates that govern hosted AI APIs. This is **not legal advice**. Primary docs change—**always re-read the current URL and note the date**. <!-...

What it is

A literacy method for reading vendor service terms, privacy centers, and product-term updates that govern hosted AI APIs. This is not legal advice. Primary docs change—always re-read the current URL and note the date.

<!-- IMAGE: checklist: parties → data use → AUP → region → indemnity carve-outs -->

HIGH PRIORITYCHECKLIST / UI
◷ IN PRODUCTION

Visual Spec & Architecture Diagram

API terms checklist: data use/training, retention, subprocessors, uptime, rate limits, indemnity, export, termination. Checkbox UI. Banner 'not legal advice—read live terms'.

Educational Focus: Practical buying/building literacy.

Why it matters

Weights licenses do not replace API contracts. OpenAI Service Terms, Gemini API Additional Terms, AWS Service Terms (including AI/ML and Bedrock subsections), Microsoft product-term change pages, and Anthropic’s Privacy Center are where retention, prohibited uses, and commercial conditions live for hosted stacks.

How it works (plain)

When you open a terms page, hunt for:

  1. What counts as paid vs unpaid (data-use often differs).
  2. How prompts/outputs may be used (improve services? human review?).
  3. Retention / abuse monitoring windows.
  4. Geographic / age / medical restrictions.
  5. Competing model / reverse engineering limits.
  6. Indemnity scope and carve-outs (if any).
  7. Third-party models on a host (Bedrock: provider terms may also apply).

Literacy examples from fetches around 2026-08-14 (verify again before reliance):

  • Gemini Additional Terms (effective March 23, 2026 per page): 18+; unpaid vs paid data-use differences; no competing-model development / weight extraction; medical-device style restrictions; region rules for EEA/CH/UK user-facing clients.
  • AWS Service Terms §50 / Bedrock: AI Services definitions; abuse detection may store inputs/outputs for ~30 days for certain models; third-party model terms; customized model access limits.
  • OpenAI Service Terms: govern Services alongside broader agreements; API use must follow docs; output IP indemnity with listed carve-outs (see live page).
  • Anthropic Privacy Center: separates commercial vs consumer collections—start at the correct hub.
  • Microsoft EAEAS product-term changes: track generative AI / Azure AI related licensing updates on the official change list.

Everyday example

Apartment lease vs house deed: both let you “use a kitchen,” but the rules about guests, sublets, and repairs differ. APIs are leases.

Try it

Pick one vendor. Paste five headings from their current terms into a note with today’s date. Mark which heading affects your data retention story.

Myths

⚠️ Myth: Marketing “we don’t train on your data” replaces reading terms.
✓ Reality: Tier, region, and product line matter; unpaid tiers often differ.
⚠️ Myth: One read at contract signing lasts forever.
✓ Reality: Terms and product sheets update—calendar a review.

Sources