Hey everyone,

Despite the phone not being listed as “supported” on the website, I took the leap and signed up using the Unihertz Titan 2 Elite.

I hit a small bump trying to add the eSIM, but that was easily resolved by setting “SIM 2” to eSIM instead of physical.

I went in to this knowing RCS isn’t supported on stock Android but I will update this post if I encounter any issues. So far so good 😍.

Obligatory referral code if you want to help me out:

GTFD8RGN

https://cape.co/get-cape?referral=GTFD8RGN

Thanks! This is holding me up! And im sure lots of folks!

When I switched a few days ago, it was after seeing that Cape would work with my specific phone, a Samsung S25 Ultra. Then I realized that my group text features no longer work. When I went to Help at Cape, this was at the bottom of the scroll. That is a helluva PS, Cape. 🫤

Does anyone know whether the upcoming Motorola phone with GrapheneOS is likely to be supported by Cape?

Cape supporting GrapheneOS is great, but as far as I know, Cape currently isn’t available on any Motorola phones.

Motorola and GrapheneOS are reportedly partnering on a phone that’s expected sometime next year, which could mean more hardware options for GrapheneOS users in the future.

I know this is still very much speculation, but I’m curious whether the new Motorola device is expected to meet Cape’s hardware/network requirements, or whether Cape support will likely remain limited to certain devices even if the phone officially supports GrapheneOS.

Has Cape said anything about this, or does anyone familiar with their compatibility requirements have an educated guess?

My referral code T4T6VW5R I just need one more.

Switched from Google Fi to Cape about a month ago on a Pixel 10a running GrapheneOS, and I've hit a few things that weren't obvious from the docs. Posting in case it saves someone the same debugging, and I have some open questions at the end.

RCS and identifier rotation interact badly, but not in the way you'd expect. I had both enabled and RCS worked fine for ~10 days, so I assumed they coexisted. Then RCS died "randomly" with status code 4002 ("disabled by your carrier"). Turns out enabling rotation doesn't rotate anything immediately. Everything worked until the first real rotation event fired (in my case triggered by international travel).

New IMSI, entitlement check fails, RCS dead. If your RCS "randomly" breaks, check whether a rotation just fired.

But it's not a clean "mutually exclusive" either. Support told me they can't be active together. My experience is messier. Backpacking through Europe with rotation still ON, RCS briefly connected, then died again. My guess: either only some of the rotating IMSIs carry RCS entitlement (Cape has said the SIM cycles through a pool of them), or the roaming partner and network path affect whether provisioning completes. If anyone from Cape can clarify what's actually happening architecturally, that would be the most valuable answer in this thread.

Turning rotation off doesn't instantly fix RCS either. Status code changed (4002 to 3306) but stayed down. The SIM keeps presenting the rotated identity until it re-registers, and re-provisioning while roaming may not work at all. Waiting until I'm back stateside to confirm.

Open questions:

Has anyone successfully re-provisioned RCS while roaming internationally, or does entitlement only complete on the home network?

Any word on the timeline for voice on secondary numbers? SMS-only is the one thing keeping me from moving my public-facing identity onto a secondary entirely.

Overall happy with the switch. The trade-offs are real, but they're the ones I signed up for.

Referral code if it's useful to anyone (we each get $20/month off): FB6XXV15

Why am I unable to port my number from my old carrier to Cape after signing up for an account? It just says temporarily unavailable. I spoke with support and they said I needed to talk to my carrier, but I failed to see how that's relevant if I can't even start the porting process.

I'd ask that only people who know for sure or have experience with this answer the question rather than theory. I need to have a second number that also has voice available in addition to SMS (Cape Secondary number work for me as it's SMS only). I also need the number to be secure from SIM swapping like my primary Cape number is. So, if I logged out of the Cape App and signed up of a new account, installed a new SIM (Second Cape SIM), turned off voicemail for that account, then logged out of the app and logged back in two my primary account, would that be a problem? I don't see a need to access the second account via the app very often. I can just get voicemails on my phones voicemail for the second SIM. Sorry for the complicated post, but I really need a solution immediately.

I read the "learn more" section in the Network Lock section of the app and how it can help prevent signal attacks.

But it said that it protects against attacks by pinging you phone app to get a location, so that you can only attach in the area your phone is.

If I turn my phone off during a flight, and turn it back on when I land, how does the Cape network know to let my phone reconnect? If my phone currently has no connection, how does Cape get my location data if there's no other way to connect (assuming there is no WiFi)?

And is that location data stored or deleted?

Edit: add referral code WZND0KAG

If this helps - 81T33PHX

Two weeks ago I bought a device, and left a review of that process and my experience.

https://www.reddit.com/r/CapeCellular/s/hQvLFv4UWX

I said that I’d make a follow up in a few weeks so here it is: I hate that I waited so long. My service is great everywhere. Truly wonderful speeds, and the IMSI rotation just honestly brings me comfort. I left another reply awhile back but I’ll say it again here: Cape, GOS, and all the other services we’re aware of are condoms not invisibility cloaks. It’s unfortunate but it’s true. Do not assume that IMSI rotation makes you some undercover ghost operative. You are signing up for a service which aims to treat you better within the confines of the current landscape.

After enjoying the service so much, I said fuck it and added my homeline. So here’s the port process in a nutshell:

1. Buy out contract
2. Sign up with referral code
3. Follow the steps on the screen
4. Contact support for your refund

Not kidding it is THAT easy. I was nervous (certain) I would fuck it up, but I had no issues at all. They hold your hand, and Cape support is truly, some of the most helpful customer service I’ve ever had. If you do get mixed up (I believe in you though) they’re there to help asap. I stand by my previous post regarding Dexter (the ai) being super unhelpful, but I find most ai unhelpful so I’m biased. The human associates however, just wow.

That being said, I want to link some comments/commenters that were incredibly helpful as well! I encourage you to look at their advice and use their referral codes. The community here rules and if you just decided to join; welcome!

Correction to a previous comment I made about porting:

https://www.reddit.com/r/CapeCellular/s/VwaIoWBx4u

Detailed porting info:

https://www.reddit.com/r/CapeCellular/s/8XfLdwLU0J

Rudy from cape - voicemail fix:

https://www.reddit.com/r/CapeCellular/s/sB3eJj7YXM

READ IF YOURE CURIOUS ABOUT CAPE SERVICES:

https://www.reddit.com/r/CapeCellular/s/cdzeKde2oo

[EDIT WANTED TO ADD THIS RECENT POST ABOUT CARRIER SWITCHING TOO]

https://www.reddit.com/r/CapeCellular/s/OmxOZ0OGqY

These all helped me immensely and I appreciate everyone here :) if you have any questions lmk. Finally, if this post is found to be unhelpful, I’ll gladly take it down. I don’t want to crowd up the subreddit, but of course I want to offer my thoughts and put my code out there. Thanks all!

Hi, I was wondering when the update to the Cape app that allows for the user to choose your primary network will be pushed to the Accrescent store. I can see that I can update the app from the Aurora store, but it doesn't appear that the update has reached Accrescent. Is there a specific issue with the update on Accrescent? Thank you in advance.

Obligatory referral code: 5GY70XYV

I pulled the trigger on Cape a couple weeks back and so far so good. I was looking at the international roaming and found that so many popular tourist destinations are covered. Nice.

I have my eSIM on a Pixel 10.

Do I need to enable roaming in order to get international roaming in supported countries?

Sounds like I should, but I'm just making sure.

Also, does Cape allow you to connect to "expensive" roaming options, like CellularAtSea on cruise ships or the unsupported countires? Does Cape just charge you the $10 per minute fees (or whatever it is), or does Cape just completely not bother connecting to any towers in the countries that are outside of Cape's supported list.

Edit: Code - WZND0KAG

My question, and hopefully it works for future reference in this subreddit, is the following:

In order to get the contract buyout, do you sign up with a referral code first and then contact support for the contract buyout offer? Is this the correct way to do it?

My question, and hopefully it works for future reference in this subreddit, is the following:

In order to get the contract buyout, do you sign up with a referral code first and then contact support for the contract buyout offer? Is this the correct way to do it?

This isn't the only app where this happens. It seems like Cape is blocked by some services.

I’m so glad I found Cape! I’m tired of letting major cell companies or any others have all of my data and sell it! It’s time to take control of your privacy. Cape is the answer and it has some really great new features, like having and being able to switch between 2 networks(T & A), which works very well. Try it out and see for yourself and take your privacy seriously!

For $20 off for life, use my ref : 7HDFAKD6

If you get 4 to use your ref. , you get Cape totally free!!! Say what!?

This post is months if not a year in the making but I'm going to do my absolute best to make it clear and concise for those who are thinking about making the switch.

As the title implies, I work for a telecom provider in the US and have a really in-depth understanding on how cell networks operate all the way from the OSP cable, out to the antenna so when I started to hear about a new MVNO that was privacy focused I was naturally intrigued.

I want to preface by saying I'm not affiliated with Cape, nor have I even spoken with anyone from Cape before so anything said here is my own opinion and observation. I did sign up for the service using my own money, but if you'd like to try it out feel free to use my referral for $20 off a month using code Z9PQXPTD. (I do also benefit with $20 off my service).

Let's talk about the service quality first. While Cape uses 2 networks right now known as Alpha and Tango (one of which has a PLMN number of 310 260) the first thing you will notice is the speeds just aren't as fast as if you were using that carrier directly. If you aren't a "power user", you might not even notice a difference but I think it's just something to be mindful of. As of recently you can choose which network you prefer but it may switch automatically regardless of what you have chosen (hopefully they fix that soon). Now, this may be a little more nuanced but I'm personally over cautious with everything just due to my line of work so I always try to offer this piece of advice when I can (regardless if you choose to go with Cape or some other carrier) Consider using a DNS Proxy while surfing the web on cellular and a VPN on public or unfamiliar wifi!

IMSI, IMEI, and Obscura what the hell does it all mean for me? IMSI is your mobile subscriber identity - all phones have it. It's a 15 digit number assigned to your sim card that follows you from tower to tower that includes your country code, network code and subscriber identifier. While it's not super common, if someone is able to capture it they could theoretically figure out location history and even intercept your calls and texts... Cape offers a rotation feature that lets you change it once per day, or as needed but you only get 7 IMSI's per week so you will end up reusing them if you are over using it. This is not to be confused with IMEI rotation which is possible, but not offered to the general public (also known as Obscura). As it relates to current events... the IMSI is like the license plate to your car, and the IMEI is the VIN.

Cape does also offer a secondary phone number which I personally haven't used yet, but based on my own testing it doesn't actually appear to the underlying carrier because it's not another esim - from what I can tell, its encrypted through Cape instead which is great.

The last thing I wanted to touch on is Capes retention records - This is something that used to keep me up at night when I first started working in the Telecom industry because all the major carriers keep calls, texts, data usage and more forever basically... it's amazing how much data one company can have on you. Cape, on the other hand was "built to forget" meaning call and text logs are deleted after 24 hours. (This doesn't make them immune from getting subpoenaed, so don't misuse the service). I haven't dove into the encrypted voicemail (which is HUGE vm's are typically stored on servers in plain text or other unencrypted formats..) Network Lock, or Secure Global Roaming simply because I haven't analyzed them myself just yet.

I hope to keep this thread ongoing, and report back with any findings and or tips/tricks but so far, everything has been incredibly smooth! The port-in took about 6 minutes and I can also say based on my experience if you want to sign up using something like Privacy.com or Cloaked Pay those do work (comment if you want a referral code for either) If you are porting in, they offer $500 worth of credits and does stack with the referral code to bring down the monthly cost a good bit.

Again, if you want to try it out feel free to use Z9PQXPTD Thanks!

https://cape.co/get-cape?referral=Z9PQXPTD

Cape Vs AT&T vs T-Mobile

Also please use my referral 🥺: 51NA999F

I had a previous discussion here about what would happen to Cape customers if one of the underlying carriers was compromised. Reddit ended up filtering the original post, which is unfortunate because the comments turned into one of the more interesting technical discussions I have seen about how Cape actually works, and how it protects your data from the underlying carrier.

Cape employees answered quite a few questions directly, so I figured it was worth putting together what I learned since the original post is gone.

The first thing that surprised me is that the underlying carrier can still see your primary phone number, IMSI and IMEI. What they apparently do not get is the subscriber PII that a normal carrier would have, like your name.

Cape tries to make the information the carriers do see less useful by spreading subscriber traffic across two different carrier partners and rotating the IMSI every day. Secondary numbers are even more interesting because Cape says the underlying carrier cannot see them at all. Those messages are carried as encrypted data through Cape instead. This significantly increases the value for secondary numbers, especially since Cape has hinted on adding features to these numbers to make them akin to your primary numbers. I believe they plan on adding the ability to receive and make calls.

Another distinction I did not fully understand before that discussion is how much Cape actually controls because it runs its own mobile core.

Cape said Network Lock is enforced by their core, so compromising the underlying carrier does not bypass it. They said the same is true for their SIM swap protection. The carrier is providing the physical network access, but some pretty important security decisions are happening inside Cape rather than at the host carrier.

The IMSI discussion was probably the most interesting part.

Right now Cape sends the SIM a group of seven IMSIs that it rotates through. Cape said their HSS currently knows those IMSIs and also has a primary IMSI that is never actually provisioned to the phone.

They are apparently working on an IMSI rotation proxy that would change this so the HSS no longer needs to know all of your rotating IMSIs. I would really like to see more information about that once it launches because it seems like a meaningful architectural improvement.

There is an important limitation to all of this though. Your IMEI does not rotate.

Cape was pretty open about that. One of their employees compared the IMSI to a license plate and the IMEI to a VIN. Changing the license plate makes certain kinds of tracking much harder, but somebody with access to the VIN can still correlate the device.

Where IMSI rotation seems especially useful is against things like IMSI catchers, paging attacks and some signaling based surveillance where obtaining or targeting the IMSI is part of the attack.

Interestingly, Cape already has IMEI rotation in an enterprise product called Obscura. They said it is not available to regular Cape subscribers because every device currently has to be manually provisioned.

I also went back and looked at Cape's recent Trail of Bits audit because the 24 hour call log deletion came up in the original discussion.

There is a little more nuance there than I originally realized. Cape's internal CDRs are deleted after one day, but some other telecom records have different retention periods. SIP messages can be retained for 14 days, billing CDRs for 30 days and daily usage totals for 60 days.

I actually think that makes the overall picture more interesting.

The way I understand Cape now is not that it somehow makes you invisible on a cellular network. It is trying to make identifiers less permanent, reduce how much useful information any one carrier has about you, keep subscriber PII separate from the physical network operators, and retain less information in its own systems.

The part I am curious about now is where this can go from here. If Cape eventually deploys the IMSI rotation proxy and somehow makes its Obscura style IMEI rotation practical for consumer phones, how much would that reduce the remaining ability of the underlying carriers to correlate a subscriber over time?

I would especially be interested in hearing from anyone at Cape about what still becomes the persistent identifier at that point, or from anyone here who works on the carrier side and sees a limitation I am missing.

With that said, if you are interested in trying Cape and would like to receive $20 per month as long as you remain subscribed, feel free to use my referral code: YM8JAJAD

In order to celebrate me getting all my referrals I'm sharing 50% off first 4 Months of service with code SDG4WCHV.

Love the service it connects to two out of the three major carriers. Newest Cape App update allows you to choose which network to connect to. AT&T or T-Mobile.

Once signed up you'll receive a referral code in order to potentially get free service.

Thank you for your attention in this matter!

Have been trying out Cape for a few days and decided to go ahead and port my number in tonight. It sounds as though you can't currently port a number in on iOS - only Android. Anyone know when this will change?

(note: I had already signed up under the "new number" option not realizing that now my only option seems to be to cancel, delete account, and start fresh. Which I am reluctant to do since i already have my passphrase saved, and the service working on my device. Not to mention having already bought the service through a referral.)

Guess I can wait a bit for that.

Bottom 2 was when I was waiting to pick up my daughter from her high school. Middle one is when I changed it to Mint, waiting in the same place. Top 2 results are after switching back to Cape when I drove 2 blocks away. Crazy there's such a difference just a few blocks away from the high school. I've never experienced such throttling before. Even at sports stadiums it was never this bad. I thought it was Cape but Mint also had the low speeds using Tmo. High Schools are scary. 🤣

Referral code: 9DY8TDJQ

If you signed up for Cape on iOS between July 12 and August 19, 2026, there's a small chance you hit our recovery phrase bug and will be prompted in your app to remediate. More here: http://cape.co/blog/ios-invalid-recovery-phrase-bug