Vendors → apideck.com
apideck.com

apideck.com

Every change Venpo has recorded in apideck.com's public terms, privacy policies and subprocessor lists – each one linked to the document version it came from.

0changes recorded
2documents monitored
11subprocessors declared
0changes in 24 months

Change activity

Recorded changes per month, last 24 months

Terms & privacy changes Subprocessor changes
Nov 2024 · 0 changes
Dec 2024 · 0 changes
Jan 2025 · 0 changes
Feb 2025 · 0 changes
Mar 2025 · 0 changes
Apr 2025 · 0 changes
May 2025 · 0 changes
Jun 2025 · 0 changes
Jul 2025 · 0 changes
Aug 2025 · 0 changes
Sep 2025 · 0 changes
Oct 2025 · 0 changes
Nov 2025 · 0 changes
Dec 2025 · 0 changes
Jan 2026 · 0 changes
Feb 2026 · 0 changes
Mar 2026 · 0 changes
Apr 2026 · 0 changes
May 2026 · 0 changes
Jun 2026 · 0 changes
Jul 2026 · 0 changes
Aug 2026 · 0 changes
Sep 2026 · 0 changes
Oct 2026 · 0 changes
Nov ’24 Feb ’25 May ’25 Aug ’25 Nov ’25 Feb ’26 May ’26 Aug ’26

What changed, and what it meant

Each entry is a diff between two stored versions of a document, marked by whether it weakened, improved or left the customer position unchanged.

No public changes recorded for apideck.com yet.

apideck.com Subprocessors

Parties apideck.com declares in its own subprocessor list and DPA annexes. Nothing here is inferred from traffic or page scripts.

SubprocessorStated purpose
Amazon Web Services, Inc. Amazon Web Services, Inc. aws.amazon.com Infrastructure
Auth0 Auth0 auth0.com Identity
usefathom.com usefathom.com usefathom.com Sales
Front Front frontapp.com Customer support
Google LLC Google LLC google.com Email and Cloud Storage of Documents
HubSpot HubSpot hubspot.com Customer Data
Intercom Intercom intercom.com Customer support
Slack Slack slack.com Customer support
Stripe Stripe stripe.com Payments
Twilio Twilio twilio.com Analytics
Vercel Vercel vercel.com Infrastructure
Showing 11 of 11 declared subprocessors See all subprocessors →
SUBPROCESSOR GRAPH

Explore the next levels

See how apideck.com's declared subprocessors connect, level by level.

The documents behind the timeline

Venpo re-reads each of these on a schedule and keeps every version. When one moves, it becomes an entry in the timeline above.

Document nameLast change
DPA | Apideck Compliance Center
No changes recorded
Subprocessors | Apideck Compliance Center
No changes recorded
Showing 2 of 2 monitored documents See all documents →

FAQs

Where does this come from?

apideck.com's own published pages: privacy policies, terms, DPA annexes and the subprocessor list. Nothing on this page is inferred from network traffic or page scripts, and nothing is supplied by apideck.com directly.

How often are the documents read?

Every monitored document is re-read on a schedule, and each fetch is stored as a dated version. The page as it existed on any given date is retained, so a change can always be traced back to the two versions it sits between.

What counts as a change?

A difference between two stored versions that alters meaning. Reformatting, reordering and typographic fixes are recorded but not surfaced as entries in the timeline.

What do the three counts on each row mean?

They are the clauses that weakened the customer position, the clauses that improved it, and the ones that changed without shifting it either way – read off the redline for that version.

Can I be told when something changes?

Yes. Tracking a vendor sends the redline the day a document moves, along with a plain-language summary of what it changed. The first vendor is free.

Is Venpo affiliated with apideck.com?

No. Venpo reads publicly published documents and records what changed in them. apideck.com is not involved in producing this page.