Full Transcript

·YouTLDR

The Invisible Phone: Ditch PSTN Forever – No IMEI, No IMSI, No KYC, Total Stealth Calling

22:19EnglishTranscribed Jul 27, 2026
0:00

Today, I'm going to teach you about a

0:01

false stealth solution to your phone.

0:04

First, be aware that the phone network,

0:06

which is called the public switched

0:08

telephone network, or PSTN,

0:12

is the most surveilled communication

0:14

system in the world. In the US alone,

0:17

each call is tracked via multiple

0:19

government surveillance methods. There's

0:22

the Prism program that records all

0:24

metadata and sends it to the infamous

0:27

Utah data center of the No Such Agency.

0:31

There's the Calia law that allows any

0:33

law enforcement officer to wiretap your

0:36

conversation just from some internet

0:39

interface without even requiring

0:41

physical presence. Then there's a cell

0:43

carrier tracking that includes cell

0:45

tower location triangulation and

0:48

identification of your phone by IMSI,

0:50

IMEI, and matches that with your phone

0:53

call. And if you're on a production

0:55

phone, Google is aware of every click.

0:58

To add to its invasiveness, Google will

1:00

now query the carrier network for your

1:01

ID, name, and address. So, there's a

1:04

direct link between your phone, the cell

1:07

network, and your presence on the PSTN.

1:10

And of course, matched to your Google ID

1:13

together with the IMEI and IMSI.

1:16

What if I told you that you can get

1:18

around all this?

1:20

I'm not suggesting that you can evade

1:22

the government if you're being actively

1:24

surveilled, but if you're just a

1:27

privacy-seeking individual that just

1:29

wants [music] to disappear quietly from

1:31

the grid,

1:32

I have a tested answer.

1:35

It's even possible for you to have a

1:36

normal phone with two methods of

1:39

calling. One that looks like a legit

1:41

normie phone and one with stealth and

1:44

use the method that suits you at the

1:46

moment. Total flexibility.

1:49

This works, folks. I tested it and

1:51

surprisingly, it does the job well. And

1:54

partly, it's a misunderstood solution

1:56

because people didn't know how to set it

1:58

up properly.

1:59

So, I'll teach you how to make it work

2:02

correctly.

2:03

Stay right there.

2:12

Big picture of the solution.

2:15

The solution is actually very simple,

2:17

but I will be honest with you. Without

2:19

the proper setup, it is buggy and

2:22

unreliable. For this to work, it has to

2:24

be as steady as a normal phone.

2:27

So, I tested this and I'm documenting

2:30

for you what I did. And when set up

2:32

correctly, it works great. If this

2:34

hasn't worked for you before, it is

2:36

likely because of some incorrect setup

2:38

or maybe it's something unique with the

2:40

phone being used. The pieces of the

2:43

solution involve using a de-googled

2:46

phone, a voice over IP service on the

2:49

phone, a voice over IP app, and a

2:52

data-only SIM. In this instance, I

2:55

tested with all products that came from

2:57

my company.

2:59

You don't have to use a product from me,

3:00

but here I have full control of all the

3:03

pieces, so I know this will work. You

3:06

can certainly find alternate services

3:08

and devices to what I offer, though I

3:10

think this is a brilliant solution in

3:13

combination, since everything works and

3:15

all are vetted and are priced very

3:18

fairly.

3:19

All the services I will discuss feature

3:21

no KYC or no ID, so you're guaranteed

3:25

privacy from the outset. There will be

3:27

no instance of some Google Android

3:30

retrieving your name and address direct

3:32

from the carrier.

3:35

De-googled phone.

3:38

The only really private phone type that

3:40

is commonly available is the de-googled

3:43

phone, which is just a general

3:45

classification of a phone running

3:47

Android Open Source Project or AOSP.

3:52

The most common variety of these phones

3:54

are Google Pixels running some AOSB

3:57

variant like eOS,

3:59

CalyxOS, LineageOS, or GrapheneOS.

4:04

For my testing, my own phone is a Brex

4:07

3, which is running eOS currently.

4:10

What makes these types of phones safer

4:12

is that first, they don't have any

4:14

connection to Google. Standard phones

4:17

send identifiers to HQ when you make an

4:19

internet connection, like your Google ID

4:22

and then your IMSI and IMEI.

4:26

So, they are automatically identified.

4:29

In addition, Google is able to track all

4:31

your app use, so it would be a simple

4:33

matter to track that you used a voice

4:35

over IP app, for example. A de-Google

4:38

phone is invisible to Big Tech.

4:41

The important feature that you need to

4:43

make this solution work is to enable

4:45

notifications via a Google spoofer

4:48

feature called microG.

4:50

I will explain all that later.

4:52

Notifications are key to making this

4:55

seamless, otherwise you'll use up too

4:57

much battery by staying awake

4:59

constantly.

5:02

Voice over IP service.

5:05

The service I'm using for testing is the

5:08

Brex virtual phone service. This is a

5:10

VoIP solution that is only available

5:13

with US and Canada phone numbers,

5:15

though they can be used anywhere in the

5:17

world. The key to this service, as I

5:19

mentioned, is that it is a no KYC

5:22

service. So, your identity is not tied

5:25

to the service, nor is it shared with

5:27

the carrier in any way.

5:29

But, the unique thing about this

5:31

solution is that because it is not

5:34

cellular based, meaning you're not using

5:36

a cell tower for phone communications,

5:39

you're actually not sending an

5:41

identifier with your call.

5:43

Over cell, every call is accompanied by

5:46

the IMSI, or international mobile

5:49

subscriber identity, and the IMEI, or

5:52

the international mobile equipment

5:54

identifier.

5:55

Using voice over IP, the call to the

5:57

phone network is actually initiated at

6:00

the carrier server. That's where the

6:01

bridge is to the PSTN, and you just

6:04

connect to that server using a network

6:07

transport protocol called SIP. S I P.

6:11

Because there's no radio connection, the

6:13

cell identifiers, meaning IMSI and IMEI,

6:16

do not exist.

6:18

By the way, you don't need to understand

6:19

what the SIP acronym means. It's just

6:22

that to the recipient of your call, the

6:24

source device of the call is unknown

6:27

other than the phone number.

6:32

Data only eSIM.

6:34

This is the part that I've been missing

6:36

for a while, and that is where to get an

6:38

affordable no KYC data only eSIM

6:41

service. We announced this product

6:44

recently, and I have partnered with a

6:45

carrier to come up with Brex SIM

6:48

Unlisted. The specific product line

6:51

applicable here is the privacy travel

6:54

eSIM service, which is available in a

6:56

dozen countries.

6:58

It is data only and can be used at a

7:01

very reasonable price. I will try to

7:03

give you estimates of cost later, so you

7:05

can see that this is all doable without

7:07

breaking the bank.

7:09

What is interesting about an eSIM data

7:11

only service is that your phone

7:13

connection to the cell network is via

7:15

internet only, so there is no assigned

7:17

phone number.

7:19

Although an eSIM still has an IMSI and

7:21

IMEI, when there's no cell or SMS

7:24

traffic, no one can associate a specific

7:27

activity to the device, since the

7:29

metadata comes from the phone number,

7:32

and that doesn't exist on a data only

7:34

SIM with internet only use.

7:37

A phone number, by the way, is what

7:39

identifies you on the PSTN. The absence

7:43

of that limits the addressability of the

7:45

base bad modem or the cell radio on your

7:48

phone.

7:49

By the design of the PSTN, the metadata

7:52

is tied to calling or texting activity,

7:55

not internet. In case you didn't know,

7:58

nowadays, most of the internet traffic

8:01

is already encrypted. This is why your

8:04

browser requires you to type HTTPS

8:07

on any website you access. That turns on

8:11

the encryption.

8:13

So, your traffic already enters the cell

8:15

carrier with an encryption layer.

8:19

But, in the case of the Brax and

8:21

service, this is even better because

8:23

though the carrier I'm using is an MVNO

8:26

of T-Mobile, even T-Mobile doesn't see

8:29

the traffic because from your phone, it

8:31

is routed to the Brax and carrier via

8:35

VPN.

8:37

You will see that specified in the APN

8:39

information or access point name

8:42

settings where the internet routing is

8:44

entered.

8:46

And then it exits back to T-Mobile, but

8:49

with the source path removed, meaning

8:52

the originating device.

8:54

So, when using a data only SIM that has

8:57

no KYC like in this example, the

9:00

internet traffic from the phone is very

9:02

protected from the typical mass

9:05

surveillance.

9:08

Using all these together.

9:11

The basic approach is to use all these

9:13

pieces together. You install a voice

9:16

over IP app on the phone to connect to

9:18

the Brax virtual phone service, and in

9:20

this case, I'm using the app Voip MS

9:24

softphone.

9:25

Then as I said, the phone itself is a

9:27

Brax 3, which is a de-googled phone.

9:30

Then it has a Brax SIM travel eSIM,

9:33

which is data only.

9:35

This is a pretty hardened solution from

9:37

the PSTN side of things. There's no

9:40

direct phone number to the phone. The

9:42

internet side is encrypted as I said.

9:44

The voice over IP service trunks your

9:46

traffic and calls are initiated from the

9:48

carrier side rather than on device.

9:52

This works very well when making

9:54

outgoing calls and there is really no

9:56

complexity with that. Where people have

9:58

a problem is to get the phone to ring

10:01

when you are mobile.

10:04

Setting up the voice over IP app.

10:08

I'm going to show you in detail how to

10:10

set up the Brac's virtual phone on the

10:12

VoIP MS app. So, there's no mystery in

10:14

this.

10:15

First, assuming you already provision a

10:17

phone number on Brac's virtual phone,

10:19

your account will look like this.

10:23

The most critical value is your SIP

10:25

username.

10:27

Next, you need to set up these three

10:29

additional important fields. Your SIP

10:31

password, your SIP server, and then the

10:35

transport method. These default to a

10:37

value, but you can change them.

10:40

The password cannot have special

10:41

characters, but I recommend a long

10:43

password with four random words.

10:47

The server is critical. Whatever it is

10:49

needs to match what you enter on your

10:51

voice over IP app. Otherwise, select

10:54

whatever is closest to you.

10:56

The other critical value is that it must

10:58

match the country of the phone number

11:01

you provisioned. If the country does not

11:03

match, you must choose an international

11:06

server.

11:08

Any of them.

11:09

The transport defaults to UDP, which is

11:12

the best in performance, but you can

11:14

select TLS if you want to increase

11:17

security. However, the encryption has a

11:19

performance penalty and may affect the

11:22

quality of the voice, so test it first.

11:26

Also, make sure you have no forwarding

11:28

number for the call. If you forward the

11:31

number, your phone will not ring as it

11:33

resends the call as a fresh call to the

11:36

other number.

11:38

But you can forward your voicemail to

11:40

email or forward SMS.

11:42

Those don't impact the ringing.

11:44

So, given the four values which you have

11:46

set up on the Brax virtual phone setup,

11:49

it is a simple matter of putting the

11:51

same exact information on the Voip MS

11:54

softphone app.

11:59

Reliable ringing.

12:01

Now, what happens once you enter this

12:03

account on the Voip MS app and enable

12:06

the account, it will then state that it

12:09

is registered. This indicates that the

12:12

voice over IP app has a constant

12:14

internet connection with the server, and

12:16

this is the first indication that things

12:19

are set up right.

12:21

If it is not showing as registered, then

12:23

go back to what I said and see what the

12:26

error is, like a typo, non-matching

12:30

server, non-matching transport, or an

12:32

international server wasn't used when

12:34

needed.

12:36

It will be some obvious difference.

12:39

There are other things to consider,

12:41

though. Only one device can be

12:43

registered at a time. So, if you have a

12:46

hardware SIP phone also active, that

12:49

will likely take priority since only one

12:51

device can ring.

12:54

I'll give you alternate approaches on

12:55

that later. In any case, at this moment,

12:58

if you call the voice over IP number,

13:01

the phone will ring and it will be

13:03

flawless.

13:04

However, most people leave it like this,

13:07

and then it doesn't ring when they put

13:09

the phone in their pocket.

13:11

The way registration works is that the

13:14

app must be constantly connected to the

13:17

server, and then if a call arrives, it

13:19

is able to immediately trigger the

13:21

ringer.

13:23

But for those on a mobile phone, you

13:25

will immediately understand that apps go

13:28

to sleep to preserve battery. And having

13:31

an app that never shuts down and causes

13:33

the internet connection to be sustained

13:36

24/7 will inevitably kill the battery in

13:39

a very short amount of time.

13:42

There are several settings to override

13:44

this, which will make this work well.

13:48

First, you must enable notifications on

13:50

the app. For notifications to work on a

13:53

de-Googled phone, you must go to microG,

13:55

which is in settings on a GrapheneOS

13:58

phone, and make sure that cloud

14:00

messaging is enabled. You also enable

14:02

Google device registration, but you

14:04

never create a Google account, so leave

14:08

that part alone.

14:10

What this does is allow microG to spoof

14:12

your identity on Google so that you're

14:15

able to receive notifications from

14:17

Google, but without identifying your

14:19

phone.

14:20

By the way, there is no microG on

14:22

GrapheneOS, and you are forced to log in

14:25

to Google with your real Google ID on

14:28

the sandbox, so I don't recommend that

14:30

method. microG works flawlessly for this

14:34

use.

14:35

In addition to notifications being

14:36

enabled for the VoIP MS app, you go to

14:40

app battery usage and permissions and

14:42

enable allow background usage.

14:46

What it does is that if the phone

14:48

receives a notification and the app is

14:51

not running, the notification will

14:53

actually launch the app in the

14:55

background, and then this will allow it

14:58

to trigger the ringing.

15:00

Using notifications, it is then

15:02

unnecessary for the phone to remain

15:05

connected continuously.

15:07

microG itself is always running even in

15:10

the background. This is the main app

15:12

that must remain connected to the

15:14

internet at all times. But since only

15:17

this app must be running, then there's

15:19

not as much of a drain on the battery.

15:22

By the way, there's an option in

15:23

permissions called manage app if unused.

15:27

This could turn off the app and wreak

15:29

havoc on you. So, make sure you disable

15:31

this feature.

15:33

Now, let's test this out. Just to

15:35

demonstrate, I will force stop the VoIP

15:38

MS app. Then, we will call the number.

15:46

As you can see, it works fine as long as

15:49

notifications are enabled.

15:54

Alternate strategies.

15:57

There's never a one-size-fits-all when

15:59

it comes to a privacy solution. Some

16:02

people need a regular phone with access

16:04

to regular calls, like a business line,

16:06

but the privacy comes from even just

16:08

partitioning your data.

16:11

If, for example, business calls go into

16:13

a regular public PSTN line with a

16:16

regular SIM card, and VoIP calls use

16:19

only the data, then you are providing a

16:21

segregation of traffic since your

16:24

private calls don't announce you on the

16:26

PSTN.

16:28

You can even add a VPN to the setup so

16:31

that the traffic is double encrypted.

16:34

Another variant approach is for the

16:36

voice over IP line to be used for

16:38

outgoing only. So, in this use case, you

16:41

can have all messages be forwarded as

16:44

voicemail. Then, you call back using the

16:47

VoIP SIP app.

16:49

Or, you can forward the actual call

16:51

directly to your main line, and then the

16:53

caller will not know your actual number

16:55

as the forwarding is only known to the

16:58

voice over IP carrier. This, of course,

17:00

is the simplest and most reliable option

17:03

since you don't have to worry about

17:04

notifications or having the SIP app

17:07

always work in the background.

17:09

But, this, of course, requires that you

17:11

have another SIM card on the phone with

17:14

a regular line and data. So, this is

17:16

still subject to PSTN mass surveillance.

17:19

The other combination is that you have a

17:21

SIP hardware phone at your home, and

17:23

then when you don't answer, it triggers

17:25

voicemail, and then you get the

17:27

voicemail via email.

17:31

Then you can fire up your SIP app and

17:33

call them back when you're not home.

17:36

Fortunately, in all these cases, you're

17:38

still getting text messages either via

17:40

the Voip.ms cell phone app or via

17:43

Brax.me my SMS.

17:46

This allows you to use a voice over IP

17:49

number for two-factor authentication,

17:51

which is the ultimate in privacy. The

17:53

only caveat is that some companies, like

17:56

Google and Facebook, deliberately

17:58

disallow a voice over IP number for 2FA.

18:02

But surprisingly, a large number of

18:04

companies allow 2FA using voice over IP,

18:07

including banks. So, it isn't as

18:09

restrictive as you might imagine.

18:12

Remember that SMS itself is another one

18:14

of these highly surveilled

18:16

communications methods, and if tied to

18:18

the PSTN and a cell phone, it identifies

18:21

you and your particular device.

18:24

Routing it via voice over IP eliminates

18:26

that risk, especially for two-factor

18:29

authentication, which is frequently used

18:31

now as a way of forcing you to identify

18:33

yourself.

18:36

Bonus concept.

18:39

Here's a bonus idea. Let's say you have

18:41

two people with the same identical setup

18:43

with Brax virtual phone and data only

18:45

eSIM.

18:47

When these two people talk to each other

18:49

instead of using the normal phone

18:52

number, you just dial each other using

18:55

the extension number provided by Brax

18:58

virtual phone.

18:59

You can even use this even if the other

19:02

person is on a different voice over IP

19:05

service using the external extension.

19:08

So, Voip to Voip, you can always dial by

19:10

extension.

19:12

This is such a privacy bonus because A,

19:15

extension calling is never logged as

19:18

there's no billing associated with it.

19:20

It's free. B, because you're talking

19:23

voice over IP server to voice over IP

19:25

server, you're not even connected to the

19:27

PSTN at all. So, there is no PSTN

19:30

metadata.

19:32

Thus, it is a completely invisible call.

19:34

Yet, for all intents and purposes, it

19:36

looks like a typical call experience.

19:40

And there's no location data or identity

19:42

attached to the event.

19:46

Final thoughts.

19:49

Let me give you a rundown on the cost of

19:51

the solution.

19:53

The Brex 3 phone is $338.

19:56

The Brex virtual phone subscription

19:58

starts at $6.25

20:01

per month. The Brex SIM travel eSIM

20:03

starts at $7.50 per month. The Voip MS

20:07

cellphone app is free. So, for low

20:10

volume minimalist use, we're talking

20:12

about an inexpensive solution, cheaper

20:14

than any equivalent regular phone plan

20:17

even.

20:18

Having a reliable way to have voice over

20:21

IP as a substitute for a normal

20:23

cellphone service has been a point of

20:26

great resistance to this solution for a

20:29

long time.

20:31

But, having tested this with these

20:33

particular combinations of products and

20:36

services, I can vouch for its

20:38

reliability. It just works as long as

20:40

you use notifications.

20:42

We are planning on creating a special

20:44

phone that has no phone calling

20:45

capability. This limitation will be

20:48

built in at the hardware level, so the

20:50

phone can only do cell data. This will

20:53

be the exact scenario I just described

20:56

here with a voice over IP app and data

20:59

only SIM. We are planning to make this a

21:01

minimalist phone, but it will be the

21:04

most private design since you cannot

21:06

make a mistake with the calling.

21:08

In fact, even the cell modem will be a

21:10

separate device from the motherboard so

21:13

it can be switched off for 100%

21:16

security. The cell baseband modem is one

21:19

of the biggest trackers in phone use.

21:21

This will be an incredibly private

21:23

device when it comes out.

21:26

Let me know what you think about all

21:27

this in the comments below.

21:35

Folks, if you're interested in the Brax

21:37

3 phone which was mentioned in this

21:39

video, you can find that at braxtech.net

21:42

and it is available for sale now on its

21:44

second batch.

21:46

And watch out for the upcoming Brax Open

21:48

Slate Android Linux tablet which can be

21:51

pre-ordered now and slated for fall

21:54

release.

21:56

We also have other products and services

21:58

on the Brax Me platform. On our store

22:01

there, we have Brax virtual phone,

22:05

Brax SIM unlisted,

22:07

Brax Mail,

22:09

and Bytes VPN. Thank you to those who

22:12

support us on Patreon, YouTube

22:14

memberships, and Locals. See you next

22:16

time.

More transcripts

Explore other videos transcribed with YouTLDR.

Get the TLDR of any YouTube video

Transcribe, summarize, and repurpose videos in 125+ languages — free, no signup required.

Try YouTLDR Free