Separating devices, browsers, and network environments

Activist accounts can still correlate through shared devices, browsers, cookies, notifications, sync, history, and network environments.

Even if you create an activist account, correlation remains if you use the same device or browser.

Using an activist social media account in a browser where you are logged in to personal accounts. Taking activity photos with your everyday smartphone. Handling materials on the same device as a real-name cloud account. These operations connect through the environment even if accounts are separated.

For anonymity, it is important to separate not only accounts, but also devices, browsers, and network environments.

Why environment separation is necessary

When you use the same environment, login state, cookies, notifications, file syncing, browser history, photos on the device, and cloud backups get mixed.

Environment separation is a system for reducing mistakes.

Create a setup that is harder to mix, rather than relying on willpower to pay attention every time.

In activism, situations arise where you need to post quickly. Sending photos from the field. Contacting allies. Checking materials. Responding to backlash.

At those moments, if the real-name environment and activist environment are the same, they mix as soon as judgment slips. A real name appears in a notification, photos sync to a real-name cloud, someone replies from a personal account, or a saved email address is used. These failures happen through everyday operation, not through technical attacks.

The purpose of environment separation is not perfect anonymization. It is to reduce the entrances where things mix and create a setup where mistakes are less likely even when people are tired.

Levels of separation

Separation has levels.

For low-risk activity, separating browser profiles alone can still be meaningful. For high-risk activity, devices and network environments may also need to be separated.

Stronger separation increases effort.

Choose according to your risk.

Not every activity needs the highest level of separation. For low-risk outreach, separating browsers and accounts can still be a major improvement. For activity where participants would be harmed if a workplace or school learned about it, device and cloud separation are also needed. When repression, whistleblowing, harassment, or real-world tracking are expected, design separation that includes the network environment and posting times.

The stronger separation becomes, the more effort it takes. If effort increases too much, operations collapse. It is important to decide what you are protecting in your activity and choose separation you can sustain.

Where VPNs and Tor fit

VPNs and Tor are tools that change how the communication route appears.

However, if you log in to a personal account or mix activist use and real-name use in the same browser, anonymity breaks even if the communication route changes.

The detailed differences between VPNs and Tor are covered in another article.

Here, focus more on "what must not be mixed with what" than on tools.

VPNs and Tor are not substitutes for environment separation. Even if a VPN changes how the source IP appears, logging in to real-name social media connects the activity to the person. Even if you use Tor Browser, opening your everyday email creates account correlation. Even if you use a separate device, separation breaks if photos sync to the same cloud.

Use tools while understanding which information each tool changes the visible appearance of. Tools that change communication routes, tools that separate browser environments, tools that check file metadata, and operations that separate contacts each have different roles. It is important not to try to solve everything with one tool.

Common separation mistakes

There are common mistakes even when people think they are separating things.

Separation is not something you set once and finish.

Check it regularly.

Automatic syncing needs particular attention. Activity photos taken on a smartphone are uploaded to a personal photo cloud. Materials made on a PC enter a synced folder for a real-name account. Browser bookmarks and history sync to another device. A password manager handles real-name accounts and anonymous accounts in the same vault.

Even if the person thinks they are "using it for activity," the sync destination may have returned to the real-name environment. Check sync settings for devices, browsers, cloud services, password managers, and photo apps.

Steps to maintain separation

Separation needs to be maintained after it is created. Even if it is set up at first, exceptions increase as operations continue.

If you notice that operations have mixed, it may be better not to force continued use of that environment. An environment where cookies, history, files, and login state have mixed may be difficult to clean completely afterward. For high-risk activity, deciding to recreate the environment may also be necessary.

Summary

Even if activist accounts are separated, correlation remains if devices, browsers, and network environments are the same.

This is because cookies, notifications, photo sync, contacts, history, and cloud services get mixed.

Separation has levels: browser, account, device, network environment, and operation.

VPNs and Tor are useful, but they do not solve mixed logins or mixed operations.

To protect anonymity, it is important to design what not to mix before choosing tools.

Related tools

Related articles

• Accounts and operation —Device and browser separation
• Network —Differences Between VPN, Tor, and Proxy
• Activists —Risks From Location Information, Movement History, and Routine Places
• Activists —Reply, backlash, and tracking risks after publishing
• Activists —How activists should think about anonymity
• Activists —Behavioral correlation activists should watch for