Spreedly
No tracked subprocessors.
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Subprocessor list | snapshot | ||
| Data processing addendum | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| Status page statuspage | snapshot |
Subprocessors
None extracted.
Listed as a subprocessor by (2)
Purposes as each company states them.
Accelevents Event Platform accelevents.com Transactional data tokenization for payment processing.
ChargeBee chargebee.com Payment gateway aggregator and vaulting provider: It is used for connecting with selected payment gateways and processing payments through such gateways. It also securely stores and tokenizes payment card information for gateways connected through Spreedly.
Service status
- 5 incidents in 90 days
- 1 major or critical
- 1 h 32 min typical time to resolve
- 7 h 51 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Degraded performance on transactional APIs | minor | 6 h 20 min | |
| Elevated 5xx Errors on Core API | minor | 20 min | |
| Errors with While Tokenizing and Transacting | major | 7 h 51 min | |
| Intermittent 500 Errors on List and Show Endpoints | minor | 1 h 4 min | |
| Degraded performance on Cybersource Credit transactions | minor | 1 h 32 min | |
| Asynchronous transactions with degraded performance | minor | 6 h 46 min |
As Spreedly's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Changes
None since tracking began.