Root

root.io

Root declares 8 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Google Cloud and OpenAI. The list last changed on Nov 4, 2026: 0 added, 0 removed, 8 changed. 2 tracked vendors name Root as a subprocessor, including Textkernel and Bullhorn.

Subprocessors CSV of Root's subprocessors · Atom feed of Root's subprocessors DORA draft CSV of Root's subprocessors as declared by Root what's this? · 

8 third parties.

NamePurposeLocationListed since
Amazon Web Services - Aikido: Infrastructure hosting, AI inferenceEU/US/ME/AP
Apideck - Aikido: Task tracker integrations (optional)
Flare - Aikido: Dark web leaked data monitoring (optional) - Noon: Dark web leaked data monitoring
Google Cloud - Aikido: AI inference - Noon: Infrastructure hosting, mail integrationEU/US
Microsoft Azure Cloud - Aikido: AI inference - Noon: Mail integration, AI inferenceEU/US
Monad - Aikido: SIEM integrations (optional)
OpenAI Developer API Access AI- Aikido: AI inferenceEU/US
Vonage - Noon: Delivery of vishingEU/US

Subprocessor of (2)CSV of the companies listing Root · Atom feed of the companies listing Root

2 companies
  • Bullhorn bullhorn.com Cloud hosting services
  • Textkernel textkernel.com Cloud hosting services

ComplianceCSV of Root's compliance · Atom feed of Root's compliance

Security program

How Root says it manages cybersecurity risk, in its annual report to the SEC.

Led by
Chief Information Security Officer reporting to the Company’s President and Chief Technology Officer
quote The Company’s CISO is responsible for assessing and managing risks from cybersecurity threats.Srini Srinivasan is the Company’s CISO and reports directly to the Company’s President and Chief Technology Officer.
Board oversight
Board of Directors
quote Our board of directors oversees an enterprise-wide approach to risk management, designed to support the achievement of organizational objectives, to improve long-term organizational performance and to enhance stockholder value.
Outside review
Engages outside assessors or consultants
quote The Company has engaged third parties to perform information security risk assessments and testing on a periodic basis.
Its own suppliers
Reviews their security
quote In order to identify and manage risk from third parties, the Company has implemented a third-party cybersecurity risk management program involving the assessment of information security risk related to the third-party, with consideration given to the inherent risk level, the adequacy of the third-party’s control environment to mitigate those risks, and areas of residual risk.
Practices named
  • Incident response plan
  • Tabletop exercises
  • Security training
  • Phishing simulations
Material incidents
None so far, it says
quote As of the filing of this Annual Report on Form 10-K, however, we are not aware of any risks from cybersecurity threats, including as a result of any previous cybersecurity incidents, that have occurred that have materially affected, or are reasonably likely to materially affect, the Company, including its business strategy, results of operations or financial condition.
Read Item 1C in full

The Company has processes in place designed to protect its information systems and to assess, identify and manage material risks from cybersecurity threats. Accordingly, the Company has designed and implemented an Information Security Program, designed to protect the confidentiality, integrity, and availability of its information systems and data (including nonpublic information in its possession, custody, or control), as well as to comply with privacy and Information Security Program requirements for insurers as set forth in applicable state laws and regulations. As part of the Information Security Program, the Company has implemented an information security and privacy training and awareness program for Root employees, which includes new-hire training, ongoing periodic training, security tabletop exercises and regular phishing simulation and exercises. In addition, the Company engages third parties as necessary in connection with these processes.

The Company has engaged third parties to perform information security risk assessments and testing on a periodic basis. It also has engaged third parties to provide a variety of services, including providing hosted security products as well as services to support cybersecurity incident detection and response activities. In order to identify and manage risk from third parties, the Company has implemented a third-party cybersecurity risk management program involving the assessment of information security risk related to the third-party, with consideration given to the inherent risk level, the adequacy of the third-party’s control environment to mitigate those risks, and areas of residual risk. The breadth and depth of the assessment activities are designed to be commensurate with the nature and scope of the services provided by the third party.

The Company’s cybersecurity risk management processes are integrated into the Company’s enterprise risk management process. Our board of directors oversees an enterprise-wide approach to risk management, designed to support the achievement of organizational objectives, to improve long-term organizational performance and to enhance stockholder value. A fundamental part of risk management is not only understanding the most significant risks a company faces and what steps management is taking to manage those risks, but also understanding what level of risk is appropriate for a given company. The involvement of our full board of directors in reviewing our business is an integral aspect of its assessment of management’s tolerance for risk and also its determination of what constitutes an appropriate level of risk. In connection with its reviews of the operations of our business, the board of directors addresses the primary risks associated with our business including cybersecurity. In particular, our board of directors is committed to the prevention, timely detection and mitigation of the effects of cybersecurity threats or incidents.

We have previously experienced cybersecurity threats to our information technology infrastructure and have experienced cybersecurity incidents that have resulted in threat actors obtaining customer personal information, attempts to breach our systems, fraudulent activity and other incidents. As of the filing of this Annual Report on Form 10-K, however, we are not aware of any risks from cybersecurity threats, including as a result of any previous cybersecurity incidents, that have occurred that have materially affected, or are reasonably likely to materially affect, the Company, including its business strategy, results of operations or financial condition. However, future threats could materially affect our business strategy, results of operations or financial condition. Risks related to cybersecurity events are detailed in the section of this Annual Report on Form 10-K titled “Risk Factors—Risks Related to Our Business—Cybersecurity incidents, or real or perceived errors, failures or bugs in our or our vendors’ systems, or our website or mobile app could impair our operations, compromise our confidential information or our customers’ personal information, damage our reputation and brand, and harm our business, financial condition, operating results and prospects.”

Cybersecurity Governance

While our full board of directors has overall responsibility for risk oversight, it has delegated oversight of certain risks to its committees, including the oversight of risks from cybersecurity threats. The board of directors delegated the oversight of cybersecurity risks to the Audit, Risk and Finance Committee, which oversees controls for the Company’s major financial and security risk exposures. The board of directors, through the Audit, Risk and Finance Committee, oversees the design and implementation of the Information Security Program. The board of directors and the Audit, Risk and Finance Committee are informed about these risks through regular reports from the Chief Information Security Officer, or CISO, about the Information Security Program.

Additionally, the board of directors is informed of significant cybersecurity incidents, as needed, by the Computer Security Incident Response Team, which is led by the Company’s General Counsel.

The Company’s CISO is responsible for assessing and managing risks from cybersecurity threats. The Company’s CISO also leads the Information Security group and is responsible for the day-to-day management of the Information Security Program. Srini Srinivasan is the Company’s CISO and reports directly to the Company’s President and Chief Technology Officer. Mr. Srinivasan has an extensive background in cybersecurity, technology, and risk management across a variety of industries, including financial services, healthcare, retail, e-commerce and technology. Additionally, Mr. Srinivasan holds various information security certifications.

The Information Security group, senior leadership and the CISO are informed about and monitor the prevention, detection, mitigation, and remediation of cybersecurity incidents through the Information Security Program. At least quarterly, the CISO provides updates to the Audit, Risk and Finance Committee, which includes updates on the overall Information Security Program status and compliance, cybersecurity related risks, and recommended changes to the Information Security Program. Senior members of our Information Security, Internal Audit and Legal functions also provide detailed, regular reports on information security and privacy to the Audit, Risk and Finance Committee.

Security program from Root, Inc.'s Form 10-K for fiscal 2025, filed Feb 25, 2026, Item 1C, in its words (evidence)

Service statusCSV of Root's status page incidents · Atom feed of Root's status page incidents

Aug 14: before our history of this status pageAug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: no incident reportedOct 1: no incident reportedOct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: 1 incident (1 minor)Nov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reported

90 days agotoday

  • 1 incident in 43 days
  • 0 major or critical
  • 10 h 50 min typical time to resolve
BeganIncidentImpactLasted
Persistent permission popups generated by Aikido Device Protectionminor10 h 50 min

Incidents per month

0 2 4 Sep 2026: 0 incidents · partial: our history begins Sep 30 Oct 2026: 0 incidents Nov 2026: 1 incident (1 minor) · typical time to resolve 10 h 50 min Sep 2026Oct Nov

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

Components affected

ComponentIncidentsBar
Device Protection1

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

Incidents reported by Root's subprocessorsCSV of incidents reported by vendors Root lists · Atom feed of incidents reported by vendors Root lists

29 reported incidents in the last 30 days, by 1 of the vendors Root lists as a subprocessor.

A subprocessor list names a company, not the service an incident touched. This does not show that Root was involved.

DateCompanyIncidentImpactLasted
OpenAIIncorrect cost data in Costs API exports no impact stated2 h 20 min
OpenAIElevated Errors On API minor42 min
OpenAIElevated ChatGPT Conversation Errors minor52 min
OpenAIElevated errors with image generation minor1 h 49 min
OpenAIElevated error rates with some U.S. business Mastercards no impact stated3 days
OpenAIChatGPT Work and Dots Errors minor13 h 6 min
OpenAIElevated error rates across paid ChatGPT plans minor1 h 54 min
OpenAIFile upload errors in ChatGPT minor4 h 52 min
OpenAIElevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences minor1 h 35 min
OpenAIElevated errors for GPT Image 2 API image edits minor4 h 1 min
OpenAI6.1 Sol Degraded Model Performance minor1 h 17 min
OpenAIElevated error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories no impact stated29 min
OpenAIElevated error rates for Ads POST requests minor11 min
OpenAIDegraded experience with ChatGPT app connections using CIMD minor50 min
OpenAIHelp Center Chat Support Degraded no impact stated32 min
OpenAIDelays in customer support responses no impact stated2 h 17 min
OpenAINew Ad Accounts failing to provision admins minor4 h 31 min
OpenAIDegraded Performance of Dots on Enterprise minor2 h 4 min
OpenAIElevated ChatGPT conversation and Responses API errors minor6 h 32 min
OpenAIAuthentication errors for some users major—
OpenAIElevated error rates for gpt-5.6-luna API requests minor1 h 9 min
OpenAIElevated FedRAMP API error rates for Astra and Sol minor5 h 17 min
OpenAIDegraded performance in ChatGPT, Codex, and APIs minor1 h 1 min
OpenAIFile Download errors minor42 min
OpenAIWidespread feature degradation major2 h 26 min

And 4 more. All of them: CSV · Who is around them.

ChangesCSV of Root's changes · Atom feed of Root's changes

See the list as we read it on any date: Time machine

  1. Changed subprocessor: Amazon Web Services purpose: (Aikido), Aikido: Infrastructure Hosting → Aikido: Infrastructure Hosting evidence: subprocessor: Amazon Web Services list before and after: subprocessor: Amazon Web Services
  2. Changed subprocessor: Apideck locations: (Aikido) → Aikido: Task tracker integrations (optional); purpose: Aikido: Task tracker integrations (optional) → none evidence: subprocessor: Apideck list before and after: subprocessor: Apideck
  3. Changed subprocessor: Flare locations: Aikido: Dark web leaked data monitoring (optional) Noon: Dark web leaked data monitoring → Aikido: Dark web leaked data monitoring (optional) - Noon: Dark web leaked data monitoring evidence: subprocessor: Flare list before and after: subprocessor: Flare
  4. Changed subprocessor: Google Cloud purpose: Aikido: AI inference Noon: Hosting provider, mail integration → Aikido: AI inference - Noon: Hosting provider, mail integration evidence: subprocessor: Google Cloud list before and after: subprocessor: Google Cloud
  5. Changed subprocessor: Microsoft Azure Cloud purpose: Aikido: AI inference Noon: Mail integration, AI inference → Aikido: AI inference - Noon: Mail integration, AI inference evidence: subprocessor: Microsoft Azure Cloud list before and after: subprocessor: Microsoft Azure Cloud
  6. Changed subprocessor: Monad locations: (Aikido) → Aikido: SIEM integrations (optional); purpose: Aikido: SIEM integrations (optional) → none evidence: subprocessor: Monad list before and after: subprocessor: Monad
  7. Changed subprocessor: OpenAI Developer API Access purpose: (Aikido), Aikido: AI Inference → Aikido: AI Inference evidence: subprocessor: OpenAI Developer API Access list before and after: subprocessor: OpenAI Developer API Access
  8. Changed subprocessor: Vonage locations: (Noon) → EU/US evidence: subprocessor: Vonage list before and after: subprocessor: Vonage
Rating badge for Root's site

Root transparency rating

It updates with the rating.

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