I Tested Cape Mobile for 2 Months. Here's What I Found.

Summary

The reviewer describes a two-month, self-funded test of Cape Mobile, a carrier that markets itself as privacy-focused. The video explains Cape’s privacy features, what the reviewer could verify, and whether online accusations that it is a “honeypot” are supported by evidence.

How Cape’s privacy features work

• IMSI rotation: A phone’s IMEI identifies the device, while its IMSI identifies the cellular subscription. Its phone number is technically called an MSISDN. Cape lets customers change their IMSI up to seven times per week. The reviewer set it to rotate daily and verified that the IMSI changed. Rotation can make it harder to link cellular activity across days, but it does not make someone impossible to track.
• Data minimization: Cape says it collects only the information needed to provide its service. The reviewer praises its published breakdown of what data it collects, why it uses it, how long it keeps it, and what it shares with suppliers.
• Short call-detail-record retention: Call Detail Records (CDRs) can include call or text metadata and location information. Cape says it deletes detailed CDRs after 24 hours. The reviewer did not independently verify the deletion, but reports that Trail of Bits reviewed Cape’s source code and AWS implementation and found no evidence that Cape failed to delete the records as promised.
• Legal requests: Cape says it complies with legally issued subpoenas and court orders, rather than informal government requests, and rejects requests it considers overly broad. Its limited retention means it cannot provide years of call logs.

Testing and signup

The reviewer says Cape worked on a Google Pixel 8a running GrapheneOS. Cape was incompatible with the reviewer’s Brax 3 and Unplugged phones because of their operating systems.

Signup involved choosing a phone and OS, confirming the phone was paid off and unlocked, selecting a new or transferred number, and providing payment details. The reviewer used a MySudo virtual card to avoid sharing their real card number. Cape also offered registration without an email address.

Honeypot allegations and conclusion

The reviewer found no evidence for online claims that Cape is a trap for privacy-conscious users. The main suspicion raised was founder John Doyle’s previous work at Palantir; the reviewer argues that this alone is not evidence of wrongdoing.

Based on personal testing and available information, the reviewer considers Cape a legitimate privacy-focused carrier, while stressing that it is one layer of protection, not a complete privacy solution.

The reviewer initially intended to test Cape for a month but says they plan to keep using it. They also note an affiliate relationship with Above Phone, despite having no sponsorship or financial relationship with Cape.

Main speaker and source

• Business Reform presenter: Provides the review, explanations of cellular identifiers and privacy features, personal testing results, and assessment of the allegations.
• Trail of Bits: Cited as the independent auditor of Cape’s CDR deletion practices.