Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Contribute
Create a page
How to help
Wiki policy
Article suggestion list
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Moderators' noticeboard
Report a bug
Consumer Rights Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Ancestry.com
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
Purge cache
General
What links here
Related changes
Special pages
Page information
Cargo data
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{incomplete|Issue 1=This need work to fit the [[Consumer_Action_Taskforce:Sample/Company/Help|company article format]]|Issue 2= The section regarding the data leak is empty}} {{InfoboxProductLine | Title = Ancestry.com | Release Year = 1996 | Product Type = Genealogy | In Production = Yes | Official Website = https://ancestry.com/ | Logo = Ancestry.svg }} [[wikipedia:Ancestry.com|'''Ancestry.com''']], owned by [[wikipedia:Blackstone_Inc.|The Blackstone Group]], is a genealogy company based in the US, known for its DNA testing and family trees. ==Consumer impact summary== === Problematic Business Practices === '''Strict cancellation rules:''' 14-day window to avoid cancellation fees ($25–$50). === Privacy Failure === '''2-year data breach (2015–2017):''' Credentials leaked via RootsWeb; some of them reused on Ancestry. Exposed data remained public for years. ==Anti-consumer practices== ===Cancellation policy=== Ancestry.com may charge a cancellation fee for "Subscriptions Longer than a Month, Billed Monthly" if users do not cancel within the first 14 days.<ref>{{cite web |title=Ancestry Renewal and Cancellation Terms |url=https://www.ancestry.com/c/legal/renewal-cancellation-terms |website=Ancestry.com |access-date=2025-02-05}}</ref><ref>{{Cite web |last=@rixendeb |title=Cancelation fee ? |url=https://www.reddit.com/r/AncestryDNA/comments/14jqeu9/cancelation_fee/ |access-date=9 Aug 2025 |via=[[Reddit]]}}</ref> <blockquote> Where offered, some subscriptions longer than a month may be eligible for monthly billing. Even though you will be billed monthly, you are committing to the entire length of your subscription (e.g. 6 months or 12 months). … (1) cancel immediately for a full refund of the first month’s fee and immediate loss of access, or (2) cancel effective at the end of the first month, subject to a cancellation fee. If you change from this type of subscription to a different type of subscription before the end of your subscription term, you will receive a prorated refund for the remainder of the current paid month, and you may be charged a cancellation fee. For subscriptions purchased on www.ancestry.com, cancellation fees are the lesser of (i) $25 USD for 6-month subscriptions or $50 USD for 12-month subscriptions (plus any applicable taxes) or (ii) the remaining cost of your subscription </blockquote> Ancestry's older price pages showed an offer which followed these cancellation terms, along with a citation showing the commitment, but this offer has since been removed from the page.<ref>{{cite web |title=Become a member |url=https://www.ancestry.com/offers/subscribe |archive-url=https://web.archive.org/web/20240824032751/https://www.ancestry.com/offers/subscribe |archive-date=2024-08-24 |website=Ancestry.com}}</ref> ==Incidents== ===Data Breach (2015)=== RootsWeb, an Ancestry service, suffered a significant data breach: a file containing the access data of 297.8 thousand users has been publicly accessible on their server from November 2015 to December 2017.<ref>{{Cite web |title=Ancestry |url=https://haveibeenpwned.com/breach/Ancestry |access-date=9 Aug 2025 |website=haveibeenpwned.com}}</ref><ref>{{Cite web |date=22 Feb 2024 |title=What happened in the Ancestry data breach? |url=https://www.twingate.com/blog/tips/ancestry-data-breach |access-date=9 Aug 2025 |website=Twingate}}</ref><ref>{{Cite web |last=Spring |first=Tom |date=27 Dec 2017 |title=Leaky RootsWeb Server Exposes Some Ancestry.com User Data |url=https://threatpost.com/leaky-rootsweb-server-exposes-some-ancestry-com-user-data/129248/ |access-date=9 Aug 2025 |website=threatpost}}</ref> The company published a security update on the official website, now unavailable, stating that they temporarely shut down RootsWeb and locked all the compromised Ancestry accounts, requiring users to change their passwords.<ref>{{Cite web |last=Blackham |first=Tony |date=23 Dec 2017 |title=RootsWeb Security Update |url=https://blogs.ancestry.com/ancestry/2017/12/23/rootsweb-security-update/ |archive-url=https://web.archive.org/web/20171227232406/https://blogs.ancestry.com/ancestry/2017/12/23/rootsweb-security-update/ |archive-date=27 Dec 2017 |access-date=9 Aug 2025 |website=[[Ancestry]]}}</ref> Below the full statement:<blockquote>We want to share an important security update with you. Last Wednesday, December 20, Ancestry’s Information Security Team received a message from a security researcher indicating that he had found a file containing email addresses/username and password combinations as well as user names from a RootsWeb.com server. Our Information Security Team reviewed the details of this file, and confirmed that it contains information related to users of Rootsweb’s surname list information, a service we retired earlier this year. For those of you who are unfamiliar, RootsWeb is a free community-driven collection of tools that are used by some people to host and share genealogical information. Ancestry has been hosting dedicated RootsWeb servers as a favor to the community since 2000. Importantly, RootsWeb does not host sensitive information like credit card numbers or social security numbers, and is not supported by the same infrastructure as Ancestry’s other brands. We are in the process of informing all impacted customers and will also be working with regulators and law enforcement as appropriate. We also reviewed the RootsWeb file to see if any of the account information overlapped with existing accounts on Ancestry sites. We did confirm that a very small number of accounts – less than one percent of our total customer group – used the same account credentials on both Rootsweb and an Ancestry commercial site. We are currently contacting these customers. In all cases, any user whose account had its associated email/username and password included on the file has had their accounts locked and will need to create a new password the next time they visit. '''What Happened''' Immediately after receiving the file containing the RootsWeb surname list user data, the Ancestry Information Security Team commenced its analysis of the file and its contents, and started a forensic investigation of RootsWeb’s systems to determine the source of the data and identify any potential active exploitation of the RootsWeb system. As a result of that analysis, we determined that the file was legitimate, although the majority of the information was old. Though the file contained 300,000 email/usernames and passwords, through our analysis we were able to determine that only approximately 55,000 of these were used both on RootsWeb and one of the Ancestry sites, and the vast majority of those were from free trial or currently unused accounts. Additionally, we found that about 7,000 of those password and email address combinations matched credentials for active Ancestry customers. As part of our investigation, our team also uncovered other usernames that were present on the RootsWeb server that, though not on the file shared with us, we reasonably believe could have been exposed externally. We are taking the additional step of informing those users as well. We believe the intrusion was limited to the RootsWeb surname list, where someone was able to create the file of older RootsWeb usernames and passwords as a direct result of how part of this open community was set up, an issue we are working to rectify. We have no reason to believe that any Ancestry systems were compromised. Further, we have not seen any activity indicating the compromise of any individual Ancestry accounts. '''What We’ve Done''' As a result of this discovery, we have taken two immediate corrective actions. First, for the approximately 55,000 customers who used the same credentials at RootsWeb’s surname list and Ancestry – whether currently active or not – we have locked their Ancestry accounts and will require that they create a new password the next time they visit. We have also sent them emails to alert them to the situation. Though we have seen no activity that indicates these accounts have been compromised, we believe taking this additional measure is the right step to ensure the security of these customers. If you have not received an email or a notice requiring you to change your password, you have not been affected. Again, this issue involves less than one percent of our users, so there is a very good chance your account wasn’t involved. Second, we have temporarily taken RootsWeb offline, and are working to ensure that all data is saved and preserved to the best of our ability. As RootsWeb is a free and open community that has been largely built by its users, we may not be able to salvage everything as we work to resolve this issue and enhance the RootsWeb infrastructure. '''What You Should Do''' If you are a customer whose account was impacted, you will receive an email telling you that you need to change your password. In that case, you will be required to create a new password the next time you visit Ancestry. For the vast majority of customers who are not impacted by this, there is nothing you need to do as a result of this incident. However, we always recommend that you take the time to evaluate your own security settings. Please, never use the same username and password for multiple services or sites. And it’s generally good practice to use longer passwords and to change them regularly. '''What We’re Doing from Here''' As always, your privacy and the security of the data you share with us are our highest priority. We are continually assessing our policy and procedures and always seeking ways to improve our approach to security. We understand the importance of our role as stewards of your information and work every day to earn your trust. We are doing a deep analysis of RootsWeb, its design and how we might be able to help the community enhance the site and its services. It is our desire to continue to host these tools for the community with appropriate safeguards in place. Please let us know if you have any questions at Support Center, and thank you for your understanding.</blockquote> == References == <references /> [[Category:Blackstone]]
Summary:
Please note that all contributions to Consumer Rights Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Rights Wiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)
Template:Cite web
(
edit
)
Template:Incomplete
(
view source
) (protected)
Template:InfoboxProductLine
(
view source
) (protected)
Template:Nowrap
(
edit
)
Module:Citation/CS1
(
edit
)
Module:Citation/CS1/COinS
(
edit
)
Module:Citation/CS1/Configuration
(
edit
)
Module:Citation/CS1/Date validation
(
edit
)
Module:Citation/CS1/Identifiers
(
edit
)
Module:Citation/CS1/Utilities
(
edit
)
Module:Citation/CS1/Whitelist
(
edit
)
Module:Citation/CS1/styles.css
(
edit
)
Category:Pages using the JsonConfig extension