Changes

In 2001, Iron Mountain was the first company ever selected to protect [[registry]] data via escrow agreements. As part of its Registry Agreement with ICANN, each Registry Operator must comply with provisions contained within a [[Registry Data Escrow Agreement]]. This agreement requires registries to periodically transfer registry data for their [[gTLD]]s to a reputable escrow agent to be held in escrow, in order to protect registrant interests in the case of a registry's failure.

In 2001, Iron Mountain was the first company ever selected to protect [[registry]] data via escrow agreements. As part of its Registry Agreement with ICANN, each Registry Operator must comply with provisions contained within a [[Registry Data Escrow Agreement]]. This agreement requires registries to periodically transfer registry data for their [[gTLD]]s to a reputable escrow agent to be held in escrow, in order to protect registrant interests in the case of a registry's failure.

In 2007, Iron Mountain was selected by [[ICANN]] to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref>  

In 2007, Iron Mountain was selected by [[ICANN]] to function as its [[Registrar Data Escrow]] agent.<ref name="icann">[http://www.icann.org/en/announcements/announcement-2-13feb08.htm ICANN announcement], ICANN.org. Published 2008 February 13.</ref> In 2013, Iron Mountain was approved by [[ICANN]] to provide data escrow services to new gTLD clients.<ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-31may13-en Announcement 31May13, ICANN.org]</ref>

The company regularly has a booth and is a frequent sponsor at [[ICANN Meetings]].

The company regularly has a booth and is a frequent sponsor at [[ICANN Meetings]].