Apify
Transparency
Breakdown
| Subprocessor list | 30 / 30 | |
| Processing locations | 8 / 8 | |
| Purposes | 7 / 7 | |
| Data processing addendum | 12 / 12 | |
| Trust center | 8 / 8 | |
| Privacy policy | 6 / 6 | |
| security.txt | 6 / 6 | |
| Security page | 5 / 5 | |
| Status page | 5 / 5 | |
| Vulnerability disclosure | 5 / 5 | |
| Pages still reachable | 8 / 8 | |
| Total | 100 / 100 |
Only documents we can retrieve count: a page behind a login or a broken link scores nothing.
Badge
For Apify's own site; it updates with the rating.
<a href="https://thirdpartyindex.com/vendors/apify"><img src="https://thirdpartyindex.com/badge/apify.svg" alt="Apify transparency rating on Third Party Index" height="20"></a>[](https://thirdpartyindex.com/vendors/apify)Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center vanta | snapshot | ||
| Subprocessor list vanta | snapshot | ||
| Data processing addendum | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| security.txt | snapshot | ||
| Status page statuspage | snapshot | ||
| Security advisories | snapshot |
Subprocessors
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services | AWS is the main cloud provider for Apify platform providing networking, compute, and various storage types.; Cloud provider | US | |
| Mezmo (ex-LogDNA) | LogDNA is used for centralized log collection, search, and alerts based on them. | US | |
| MongoDB Atlas | Data storage and processing; MongoDB Atlas is managed solution for MongoDB used as primary database for all the user metadata. | US | |
| Snowflake | A cloud-based data warehouse for data storage and analytics.; Data storage and processing | US |
Listed as a subprocessor by (1)
Purposes as each company states them.
- Chat Aid chataid.com Website crawling to collect data from connected websites
Service status
9 incidents in the last 90 days (3 major or critical, 5 minor, 1 with no stated impact) · typically resolved in 11 h 49 min · longest major: 37 h 33 min
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated errors in Actor runs | major | — evidence | |
| Degraded Actor performance | none | 2 h 8 min evidence | |
| Degraded performance of SHADER proxy group | minor | 22 h 26 min evidence | |
| Degraded performance of Google SERP Proxy | minor | 21 h 59 min evidence | |
| Degraded performance of Google SERP Proxy | major | 37 h 33 min evidence | |
| Increased error rate on Actor Standby endpoints | minor | 1 h 4 min evidence | |
| Degraded performance of API operations due to slow database operations | critical | 11 h 49 min evidence | |
| High number of Actor run migrations | minor | 5 h 1 min evidence |
As Apify's status page reports its own incidents (scheduled maintenance left out), read every few hours since .
Changes
None since tracking began.