top of page

How to protect your phone number when testing new AI tools

2 days ago
4 min read
Hands using a tablet with a digital privacy lock

Create an account on any new AI. Email address. Password. Phone number. It's always nice to be asked one thing but when it's 10+ times a year it can get a little out of hand. If you have a second brain or know anything about using a personal AI knowledge base. There's tons of information about you in these systems. Clients, strategy docs etc. Your identity should be just as important as what you're storing in there. Here we will take a deep dive into keeping your phone number private. As a topic of digital identity.

Why AI Tool Sprawl Turned the Phone Number Into an Identity Key

Picture yourself as a product manager. One Tuesday you learn about this AI note taker that will help take notes while you're on research calls. You sign up for it over your lunch break and give them your business email and cell phone number. You may use another tool on Thursday to transcribe a different piece of media. This isn't bad until one day you realize you may have over 10 accounts that you've used your cell number on.

Now that phone number is associated with every account you signed up for. If any of those businesses get hacked your phone number will know what your email and name is. Which can tie into all of those previous hacks that occurred. You can change your password in the blink of an eye. Your cell number is not something you'll be changing anytime soon. With the majority of websites asking for your number for 2 factor authentication your number is going to be linked to your info no matter what. You can always have multiple email's to help but I'm sure you only have one phone number you've had for the majority of your life.

Where Identity and Privacy Are Heading in AI Workflows

They allow you to login using a passkey tied to your device and do not require a phone number. There are many services that now support this but we will likely see more sms code usage until adoption grows.

With the emergence of AI agents there is the question of what they should have an account under. If I have an agent signup to something for me should it use my identity? Have its own or be assigned one each time?

Another thing that will affect identity is AI running on devices. Having less of your information leave your device means there will be less services needing to know who you are. This may also decrease the amount of times we have to give our number away to access a service.

How Phone Verification Works and Where the Privacy Trade-Off Appears

There are many reasons why services want your number. Sending you an SMS code is one. It helps prevent bots from creating thousands of accounts at once.

However there are risks that come with providing your number as well. Data breaches expose databases full of phone numbers. Your number could be added to a marketing list. Phone numbers get reused so some random person could have used your number before. If someone was able to sim swap your number they would have access to all of your accounts that use SMS verification.

People who test many apps often look for ways to keep their primary number separate from low-stakes sign-ups. The usual options are a second physical SIM, a VoIP line, a separate number from a regular carrier, and a verification phone number by eSIM Plus. A second SIM is reliable but adds a bill and a card to carry. VoIP numbers are flexible, though some services refuse them. An eSIM-based option avoids the physical card, while how long a number stays usable varies by provider. Whichever route you pick, settle account recovery before the first sign-up.

Building a Privacy-First Workflow Around Your Knowledge System

First off, minimize what you provide to each service. If all they need is an email, do that. Need a number? Ask yourself if you care about this account in 3 months.

Create two buckets of accounts. You'll want to use your primary number and authentication app for anything you deem important. Work email, banking, cloud, AI you use often. Create another bucket of trial accounts. Give these their own email and password manager that isn't associated with your primary bucket. Use sms as your last resort 2fa.

Since you're capturing information you will probably end up with verification codes, passwords and even backup codes being saved to your second brain. These may be something you want to remove from your knowledge base or at least not be stored in your capture rules.

Utilizing local first tools and bringing your own key is also a good practice.

Responsible Use: Legitimate Scenarios and Clear Limits

Some simple reasons why you may need a second phone number. Maybe you're a QA Engineer and need to test a sign up 12 times. Need to keep a client's apps separate from your own as a freelancer. Want a local phone number when you're abroad. Maybe you want to send pdf's to a website but don't want to use your real phone number your bank is linked to.

What it can't do is allow you to circumvent platform TOS's, bypass a ban on yourself, scam people, create alt accounts or impersonate others. Don't try to circumvent verifications, they're there for a reason.

You also should not use it for accounts you want to keep long term. Such as a bank, work email, cloud storage. If the number expires your means of recovery will expire with it.

Outcome

Knowing things only is not what makes a good knowledge system. There needs to be limitations too. How many numbers can you have connected to your account. What information will you have your auto capture remember. Once you know these things your footprint will be smaller. So just a tip when using an AI has privacy built into your decision making at an early stage. Before you give the 10th app your number.

Give every agent the context to do better work

Connect your agents to the knowledge, decisions, and history already organized in remio.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page