How to manage multiple accounts safely, within each site's rules

To manage several accounts safely, first confirm that each site lets you hold them, then give every account a browser of its own: its own cookies and storage, its own network exit, and a name that tells you exactly whose it is. Most trouble with multiple accounts comes from mixing: a session signed in to the wrong account, a post made from the wrong login, a password passed around in a chat.

This guide covers when holding several accounts is allowed, what a website can use to tie accounts together, how to set up one profile per account, how to keep hundreds of them in order, and a checklist to finish with.

Start with the rules: when several accounts are allowed

Plenty of ordinary work involves more than one account on the same site:

• Agencies and freelancers manage advertising, social and marketplace accounts on behalf of their clients.
• Sellers run separate storefronts where the platform permits more than one.
• Businesses keep a company account apart from a founder's personal one.
• QA teams hold test accounts for each role and region a product supports.
• Individuals keep work and personal browsing apart.

Whether a particular site allows it is in its terms of service, and the answer differs by site and by account type. Many platforms have explicit rules for agencies or for business and personal accounts. Read them before you set anything up, and follow them. A separate browser profile changes how cleanly your accounts are kept apart; it does not change what a site permits. Our acceptable use policy applies to every profile.

What can tie accounts together

When two accounts run from one ordinary browser, a website can see that they share a lot. Knowing what is shared tells you what to separate.

• Cookies and site storage. One browser holds one set of cookies per site. Switching accounts means signing out and in, and storage left behind by one session (local storage, IndexedDB, cached files) is still there for the next.
• The browser fingerprint. Screen, fonts, graphics card, timezone and dozens of other values describe the device. Two accounts on one browser present the same device. We explain this in what is browser fingerprinting.
• The network address. Accounts used from the same connection arrive from the same IP address.
• Extensions and saved data. A password manager or an extension shared across accounts can carry state from one into another.
• Details you enter yourself. Shared recovery addresses, phone numbers and payment methods connect accounts in the site's own records. Give each account the details that genuinely belong to it.

None of these is a problem on its own. They become one when accounts that belong to different clients, stores or people end up looking like, and behaving like, one person's.

One profile per account

The simplest rule that works: one account, one browser profile. A profile here means a complete, separate browser with its own cookies, storage, extensions, bookmarks and downloads, kept between sessions. Sign in once, stop the profile, and next time it opens still signed in.

Ordinary browser profiles go part of the way: they separate cookies, but every profile still reports the same device and uses the same connection. An anti-detect browser gives each profile its own consistent device and its own proxy as well. If that term is new, start with what is an anti-detect browser.

Name profiles so nobody has to guess

A good name answers "whose account is this, on which site, for what?" at a glance. A pattern like Client – Platform – Purpose works for most teams:

• Acme – Ads – AU
• Acme – Social – Main
• Store UK – Seller centre
• QA – Admin role – DE

Put the owner first so a sorted list groups by client or store. Keep the site in the name even when it seems obvious; it saves opening the wrong profile when two clients use the same platform.

Folders, tags and notes

Names carry identity; folders and tags carry structure.

• Folders for ownership: one per client, store or team, with sub-folders such as Ads, Social or Shops.
• Tags for things that cut across folders: the platform, the market, "needs review", "paused".
• Notes for what the next person needs: who to ask for a 2FA code, which proxy region the account expects, any platform rule that applies.

Give each account its own exit

A proxy changes the address a site sees. For accounts that should stay apart, each profile wants its own:

• Stable. A signed-in account should come from the same place each visit. A static ISP proxy or a sticky residential session suits this; rotating exits suit one-off visits. Our guide to residential, datacenter, ISP and mobile proxies compares them.
• In the right market. An account that belongs to a business in Germany should normally connect from Germany.
• Never shared by accident. Two profiles on one exit share an address. Assign proxies one to one when the accounts should not look related.
• Never skipped. If the proxy is down, the profile should not quietly start on your own connection.

Then make the rest of the profile agree with the exit: a profile connecting from Frankfurt should keep Frankfurt time and offer German among its languages. A mismatch between timezone and IP location is one of the most common contradictions a site sees.

Save sessions, and keep them safe

Signing in every day is tedious and adds risk: more password typing, more 2FA prompts, more chances to use the wrong login. A profile that saves its session avoids most of that. Two things keep it safe:

• Lock sensitive profiles behind their own password, so one cannot be opened by mistake.
• Encrypt anything that leaves your computer. If profiles sync between machines or go to a colleague, they should be encrypted before they leave.

Working with a team

Once more than one person works on the accounts, the old shortcuts break down: a shared spreadsheet of passwords, a login pasted in a chat, two people signed in to one account at the same time. Share the profile instead of the password. We cover this properly in how to share account access with a team.

How Browz handles multiple accounts

Browz is built around one profile per account, and every part of the setup above is a feature you can check on our site.

• Isolated, saved profiles. Cookies, local storage and IndexedDB are kept per profile, with its own extensions, bookmarks and downloads folder. Sessions survive app restarts (browser profiles).
• Organised for hundreds of profiles. Nested folders, tags, notes, a status and primary site per profile, and search across all of them. Select profiles to start, stop, move, tag or lock them together; bulk jobs are durable, so a restart does not leave one half done.
• A checked exit per profile. HTTP, HTTPS, SOCKS4, SOCKS5 and SSH proxies from any provider. Every check opens a real tunnel and measures the exit over HTTPS; timezone and WebRTC are set from that measurement, and a profile whose proxy fails its check is refused at Start rather than launched on your own connection (proxies).
• A consistent device per profile, set in the browser engine and stable between sessions.
• End-to-end encrypted sync on every plan, Free included: profiles, proxies and browser state are encrypted on your device before they sync (security).
• Teams with roles, sharing at four levels, one device at a time and an activity log (teams).

Set it up in the app

1. Open Proxies, choose Bulk import, and paste your provider's list. Choose Check on each row to see its real exit.
2. Create a folder per client or store.
3. Create a profile per account in its folder, named with the pattern above, and pick its proxy in the new-profile panel.
4. Leave timezone and language on automatic, so they follow the measured exit.
5. Start each profile, sign in to its account, and stop it. The session is saved.
6. In Settings › Network and proxies, turn on Refuse if the exit country changed for accounts that should always come from one country.

Or from the command line

The browz command talks to the app on your own computer:

browz check prints the measured exit, and browz list shows each profile with its proxy. Set BROWZ_PROXY_PASS in your environment to keep the proxy password out of your shell history. Agencies will find a fuller setup in Browz for agencies.

The Free plan covers 5 profiles, enough to try the whole setup. Paid plans start from $4.99 a month, with a 14-day refund on the first payment (pricing).

A checklist

• The site's terms allow each account you hold, and you follow its rules for agencies or business accounts.
• One profile per account, named owner first.
• Folders for ownership, tags for platform and market, notes for the next person.
• One stable proxy per profile, in the account's market, checked before first use.
• Timezone and language follow the exit.
• No fallback to your own connection when a proxy fails.
• Sensitive profiles locked; anything that syncs or leaves your computer encrypted.
• Teammates get access to profiles, not passwords.

Frequently asked questions