Third Party Index

Lago

getlago.com

Transparency

Strong

Breakdown
Subprocessor list30 / 30
Processing locations8 / 8
Purposes7 / 7
Data processing addendumnot found0 / 12
Trust center8 / 8
Privacy policy6 / 6
security.txtnot found0 / 6
Security page5 / 5
Status page5 / 5
Vulnerability disclosurenot found0 / 5
Pages still reachable8 / 8
Total77 / 100

Only documents we can retrieve count: a page behind a login or a broken link scores nothing.

Badge

Lago transparency rating

For Lago's own site; it updates with the rating.

<a href="https://thirdpartyindex.com/vendors/lago"><img src="https://thirdpartyindex.com/badge/lago.svg" alt="Lago transparency rating on Third Party Index" height="20"></a>
[![Lago transparency rating on Third Party Index](https://thirdpartyindex.com/badge/lago.svg)](https://thirdpartyindex.com/vendors/lago)

Compliance

Certified

Certifications as Lago's trust center lists them; reports are usually shared on request (evidence)

Documents

DocumentVerifiedChangedEvidence
Trust center vanta snapshot
Subprocessor list snapshot
Privacy policy snapshot
Terms snapshot
Security page snapshot
Status page incident.io snapshot

Subprocessors

8 third parties. CSV · Atom

NamePurposeLocationListed since
Amazon Web Services, Inc. (AWS) Cloud hosting, compute, storage, database, caching, and networking infrastructure. Processes customer account data, billing events, and usage records.United States or EU, depending on customer datacenter election
ClickHouse, Inc. Analytics database for usage metering and event aggregation. Processes usage events and metering data.United States or EU, depending on customer datacenter election
Functional Software, Inc. (Sentry) Application error tracking and performance monitoring. May process user identifiers and IP addresses in error traces.United States or EU, depending on customer datacenter election
incident.io Ltd Incident management, alerting, and on-call scheduling. Processes internal operational data only.EU (Belgium)
Mistral AI AI model inference for platform features. May process customer billing data and usage patterns.France
Nango, Inc. Integration platform — Lago builds connectors on top of the Nango API to sync customer account data, invoice data, and CRM records with third-party systems (e.g., HubSpot, Xero, NetSuite, Avalara, Anrok). Only activated if the customer uses a supported integration.United States
Peaberry Software, Inc. (Customer.io) Transactional and lifecycle email delivery. Processes email addresses and customer identifiers.United States
Pylon Labs, Inc. Customer support ticketing and communication. Processes customer contact information and support request content.United States

Listed as a subprocessor by (5)

Purposes as each company states them.

Service status

Jul 1: no incident reportedJul 2: no incident reportedJul 3: no incident reportedJul 4: no incident reportedJul 5: no incident reportedJul 6: no incident reportedJul 7: no incident reportedJul 8: 1 incident (1 minor)Jul 9: no incident reportedJul 10: 3 incidents (3 minor)Jul 11: no incident reportedJul 12: no incident reportedJul 13: no incident reportedJul 14: no incident reportedJul 15: no incident reportedJul 16: no incident reportedJul 17: no incident reportedJul 18: no incident reportedJul 19: no incident reportedJul 20: no incident reportedJul 21: no incident reportedJul 22: no incident reportedJul 23: no incident reportedJul 24: 1 incident (1 minor)Jul 25: no incident reportedJul 26: no incident reportedJul 27: no incident reportedJul 28: no incident reportedJul 29: 1 incident (1 minor)Jul 30: no incident reportedJul 31: no incident reportedAug 1: no incident reportedAug 2: no incident reportedAug 3: no incident reportedAug 4: no incident reportedAug 5: no incident reportedAug 6: no incident reportedAug 7: no incident reportedAug 8: no incident reportedAug 9: no incident reportedAug 10: no incident reportedAug 11: 1 incident (1 minor)Aug 12: no incident reportedAug 13: no incident reportedAug 14: no incident reportedAug 15: no incident reportedAug 16: no incident reportedAug 17: 1 incident (1 minor)Aug 18: no incident reportedAug 19: no incident reportedAug 20: no incident reportedAug 21: no incident reportedAug 22: no incident reportedAug 23: no incident reportedAug 24: no incident reportedAug 25: no incident reportedAug 26: no incident reportedAug 27: no incident reportedAug 28: no incident reportedAug 29: 1 incident (1 minor)Aug 30: no incident reportedAug 31: no incident reportedSep 1: no incident reportedSep 2: no incident reportedSep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: no incident reportedSep 9: no incident reportedSep 10: no incident reportedSep 11: 1 incident (1 minor)Sep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: 1 incident (1 minor)Sep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: no incident reportedSep 23: no incident reportedSep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reported

90 days agotoday

BeganIncidentImpactLasted
Degraded performance on our APIminor10 min
Degraded performance on our APIminor3 h 28 min
Degraded performance on our APIminor57 min
Degraded performance on our APIminor5 min
Degraded performance on our APIminor5 min
Degraded performance on our APIminor8 min
Degraded performance on our APIminor28 min
Degraded performance on our APIminor9 min

Incidents per month

0 3 6 Mar 2026: 1 incident (1 minor) · partial: our history begins Mar 25 · typical time to resolve 13 min Apr 2026: 3 incidents (1 minor, 2 no impact stated) · typical time to resolve 17 min May 2026: 5 incidents (1 critical, 1 major, 1 minor, 2 no impact stated) · typical time to resolve 7 min Jun 2026: 5 incidents (2 minor, 3 no impact stated) · typical time to resolve 36 min Jul 2026: 6 incidents (6 minor) · typical time to resolve 27 min Aug 2026: 3 incidents (3 minor) · typical time to resolve 5 min Sep 2026: 2 incidents (2 minor) · typical time to resolve 3 h 28 min Mar 2026AprMayJunJulAugSep

critical major minor no impact stated before or partly before our history

As Lago's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Changes

None since tracking began.