Is Hope Chest safe?

Medium risk

Hope Chest is medium risk. Code analysis shows the extension reads your FamilySearch pedigree and posts ancestor names and your person ID to HopeChestSoftware.com/Posterity, unless the server already recorded you.…

hope-chest-publishersv13.0.7Extension ID gjneklbanpnnjdeddbnkkgeljkhpblhpChrome Web Store
52Risk
Who publishes it

CLEANTECHNOLOGY, INC - 1 other listing from the same operator, none carrying a finding

Publisher
hope-chest-publishers
Declared legal entity
CLEANTECHNOLOGY, INC
Registered address
4274 S Snowcap Ct, Gilbert, ARIZONA 85297, United States
Registered contact
Spencer Thomason

Same operator - 1 listing

Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.

AI-assisted analysis.

Hope Chest findings

Extension sends your FamilySearch tree names and IDs to HopeChestSoftware.com

HighunwantedCWE-200Static analysis

Code analysis shows the extension reads your FamilySearch pedigree and posts ancestor names and your person ID to HopeChestSoftware.com/Posterity, unless the server already recorded you.

What actually happens

You did this

You open your family tree on familysearch.org while signed in.

The extension did this

The extension fetches your pedigree and posts relatives' names plus your person ID to HopeChestSoftware.com.

This runs only when the server reports your tree as not yet recorded.

The code that does this

Pedigree fetch and upload in the content script

Readable version

Head-of-tree name check sent first

js/contentscript.js
chrome.runtime.sendMessage({ url: "Posterity/CheckIfPosterityRecorded", type: "POST", data: {  FullName, HeadName: fatherName, HCUserID, PersonID,}}, function (responseadd) { });

Fields sent to HopeChestSoftware.com

  • Your full name
    Jane Q. Example (illustrative)

    Your FamilySearch display name, sent with the head name.

  • Your person ID
    KWCJ-ABC (illustrative)

    Your FamilySearch tree identifier.

  • Relatives' names
    ChildName: John Example (illustrative)

    Names of people in your pedigree, grouped by head and child.

  • Extension user ID
    HCUserID (illustrative)

    The extension's own account identifier.

Where the data goes

    • hopechestsoftware.com

    Extension vendor backend; receives Posterity, CheckIfPosterityRecorded and AddPossiblePosterities POSTs.

Observation

Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.

FamilySearch extension sends email, name, birth year to HopeChestSoftware.com

MediumunwantedCWE-359Static analysis

Code analysis shows the extension reads FamilySearch session data on page load and sends email, display name, birth year and person ID to HopeChestSoftware.com.

What actually happens

You did this

You open a familysearch.org page while signed in.

The extension did this

The extension reads your session and requests HopeChestSoftware.com with your details.

The code that does this

Session read and request URL construction

Readable version

Source is unminified; same code

js/contentscript.js
// readable as shipped: session fields from user.user.{email,displayName,cisId,personId,birthDate} are sent to HopeChestSoftware.com/User/GetUserLevelAndPosterity

Fields in the query string

  • Email
    jane.doe@example.com

    Your FamilySearch account email.

  • Full name
    Jane Doe (illustrative)

    Your FamilySearch display name.

  • Birth year
    1962 (illustrative)

    Year taken from your profile birth date.

  • Person ID
    KWCZ-4TQ (illustrative)

    Your FamilySearch tree person identifier.

Where the data goes

    • HopeChestSoftware.com

    Receives the GetUserLevelAndPosterity request carrying the account fields.

Observation

Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.

Hope Chest version history

  1. 12.0.5

    Mar 4, 2026

  2. +4 more

  3. 13.0.5

    Aug 16, 2026

  4. 13.0.6

    Aug 29, 2026

  5. 13.0.7

    Sep 17, 2026

Chrome Web Store listing

Versions
13.0.7 latest of 8 seen since March 4, 2026
Store rating
4.1 from 398 ratings
Last updated
January 8, 2025
Size
1.21 MiB
Privacy policy
hopechestsoftware.com
Updated July 21, 2026