Skip to main content
Technology

Connectivity Should Be Part of the Safety Net

Brian LatchfordOctober 1, 20267 min read
Connectivity Should Be Part of the Safety Net

Connectivity Should Be Part of the Safety Net

October is Domestic Violence Awareness Month. It is a time to recognize survivors, support those affected by domestic violence, and consider what each of our industries can do to help.

For those of us in wireless, there is an important question worth asking:

What role can connectivity play in helping someone reach safety?

For most people, a mobile phone is a convenience. It keeps us connected to work, family, entertainment, transportation, banking, and countless other parts of everyday life.

For someone experiencing domestic violence, that same connection can be much more.

It can be a way to call for help.

It can be a connection to a trusted friend or family member.

It can provide access to transportation, financial accounts, employment, housing resources, healthcare, or support services.

In some circumstances, connectivity can be a lifeline.

But the wireless industry also has to recognize another reality: the technology that connects people can sometimes be used to control them.

When Connectivity Becomes Complicated

Mobile technology has become deeply integrated into our lives. Phones know where we are. Accounts can contain years of communications. Family plans connect multiple people under a single account. Applications can share location information across devices.

These capabilities can be incredibly useful. They can also create risks for someone experiencing abuse.

The National Domestic Violence Hotline warns that cell phones can potentially be used to track location and access information about calls and text messages. The National Network to End Domestic Violence's Safety Net Project similarly works specifically on the intersection of technology, privacy, and survivor safety.

That means the solution is not simply more technology.

It is better designed technology, better policies, and better awareness of how connectivity can affect someone in a vulnerable situation.

A Phone Number Can Represent Independence

Consider something as ordinary as a wireless family plan.

For millions of families, putting several lines on one account is convenient and economical. But what happens when the person controlling that account is also the person someone needs to escape?

Suddenly, changing wireless service can become far more complicated.

Congress recognized this problem with the Safe Connections Act, which established protections intended to help survivors separate their mobile service from shared plans while maintaining access to communications.

That legislation represents an important principle for our industry:

Access to communications should not become another mechanism of control.

But regulation should be the beginning of the conversation, not the end.

What More Can Wireless Do?

The wireless industry has spent decades solving extraordinarily difficult technical problems.

We have built nationwide networks capable of connecting hundreds of millions of devices. We have developed eSIM technology that can activate connectivity without inserting a physical SIM card. We have created sophisticated account management systems, fraud detection platforms, APIs, location services, and real time provisioning capabilities.

The same innovation should continue to be applied to safety.

Carriers, MVNOs, MVNEs, device manufacturers, application developers, and other technology providers should continue exploring ways to make it easier for people to establish independent connectivity when they need it.

That could mean improving processes for separating lines from shared accounts.

It could mean making privacy and location sharing controls easier to understand.

It could mean providing clearer visibility into which people, devices, and applications have access to someone's information.

It could mean simplifying the process of establishing a new account or activating a new device.

It could also mean designing systems from the beginning with the understanding that the primary account holder is not always the person whose privacy needs to be protected.

There will not be one feature or one technology that solves this problem. But there are many opportunities to make the technology ecosystem safer.

Technology Will Not Always Be Perfect

There is another reality our industry should be willing to acknowledge.

Technology sometimes fails.

Networks can experience interruptions. Devices can malfunction. Software can contain bugs. Applications can behave in unexpected ways. No technology company can credibly promise that every device, network, platform, or application will perform perfectly every second of every day.

When technology plays a role in someone's safety, however, accepting that perfection may be impossible cannot become an excuse for accepting preventable failure.

We should continue pursuing it anyway.

That means building redundancy where possible. It means testing for circumstances beyond the typical use case. It means thinking about what happens when a network connection disappears, a device loses power, an application stops responding, or a user cannot interact with technology in the way its designers expected.

Most importantly, it means remembering that technology should be one component of a broader safety ecosystem, not a substitute for people, emergency services, support organizations, sound policies, and other resources.

We may never build perfect technology.

But when people could depend on what we build during some of the most difficult moments of their lives, we should never stop trying to make it better.

Safety and Privacy Must Work Together

There is also an important balance the technology industry must recognize.

Features designed to create safety can sometimes create unintended risks.

Location sharing is a perfect example.

Knowing where a family member is can provide reassurance and security. In another situation, that same feature can potentially allow someone to monitor another person's movements.

The same is true for shared cloud accounts, connected devices, smart home products, wearables, and family applications.

That does not mean these technologies should disappear. It means developers and connectivity providers need to think carefully about privacy, permissions, transparency, and control.

A safety feature should never quietly become a surveillance feature.

A Challenge to Our Industry

Domestic Violence Awareness Month should be more than an opportunity for companies to express support.

For those of us who build technology, it should also be an opportunity to ask difficult questions about what we are building.

If you are designing a connected device, what happens when connectivity fails?

If you are developing an application, could a feature intended to help someone also be used to monitor them?

If you operate a wireless service, how easily can someone regain control of their connectivity?

If you build account management systems, have you considered situations in which the account owner and the person who needs protection are not the same person?

If you develop safety technology, what happens when the technology itself fails?

These questions should not only be asked in October.

They should be part of how we design, test, deploy, and improve connected technology throughout the year.

Connectivity Is Infrastructure

At Atomic Mobile, we spend every day thinking about connectivity.

Usually those conversations involve networks, data usage, eSIMs, APIs, billing, IoT, customer experience, and the technology required to launch and operate mobile services.

Domestic Violence Awareness Month is an opportunity to remember what all of that technology ultimately represents.

Connection between people.

For someone experiencing domestic violence, maintaining a safe and independent connection to the outside world can matter enormously.

Our industry has already made progress. There is more work to do.

So this October, our challenge to the wireless and technology industries is simple:

Keep safety in the conversation.

When we design the next device, build the next application, launch the next wireless service, or develop the next connected platform, consider not only what the technology can do when everything works exactly as intended, but what happens when it does not.

Think about privacy. Think about independence. Think about reliability. Think about unintended consequences.

And then keep improving.

Because sometimes a mobile connection is about much more than making a call or using data.

Sometimes, staying connected can be part of finding a way forward.


If you or someone you know is experiencing domestic violence, resources are available through the National Domestic Violence Hotline at 800-799-SAFE (7233), by texting START to 88788, or through TheHotline.org.

Brian Latchford

Author