Home → Use cases → Social media management

A browser profile per brand

Managing social accounts for several brands is ordinary, permitted work. Every major platform expects agencies and freelancers to do it. The problem is not permission, it is that a single browser makes unrelated brands look like one operator, and platforms act on that resemblance without asking whether the arrangement was legitimate.

What goes wrong without isolation

The shape that works

One profile per account, not per client

A client with an Instagram page, a Facebook page and a TikTok account is three profiles, not one. The moment two accounts share a profile they share a fingerprint and a cookie jar, and nothing you do afterwards separates them. This is the single decision that matters most, and it is cheap to get right at the start and expensive to fix later.

A stable address per profile

Bind each profile to a proxy and leave it there. The value is not hiding anything; it is that the account always appears from the same place. An account that has logged in from Lahore for eight months and suddenly appears in Frankfurt is what triggers a verification challenge, and a profile with a fixed address simply never generates that signal. A proxy whose timezone contradicts the profile is worse than no proxy, so set them to agree.

Groups that match how you work

Group profiles by client, so a new starter can be given exactly the brands they handle and nothing else. The grouping is also how offboarding stays simple: remove their access to a group rather than hunting through a list of forty profiles.

Handover without shared passwords

A profile carries its own logged-in session. Hand over the profile and the next person is already inside, without the password being spoken aloud, pasted into a chat, or written in a document that outlives their employment. Team members get their own logins with per-group access, so there is nothing to rotate when they leave, and no shared credential that three former contractors still know.

Scheduling and repetitive work

The parts of this job that are genuinely mechanical, pulling the same weekly numbers out of four dashboards, can be recorded once and run per profile with no-code RPA. It is worth being clear about what that is for: gathering what you already have access to, not manufacturing engagement. Platforms detect automated interaction reliably and penalise it, and no fingerprint work changes that.

What this does not solve

Isolation separates the browser. It does not separate everything, and the gaps are worth knowing before you rely on it:

Setting it up

  1. Make a group per client.
  2. Make a profile per account inside that group, named so anyone can tell what it is.
  3. Bind a proxy to each and leave it bound. Check it in the fingerprint test before trusting it.
  4. Log in once, inside the profile. The session stays with it and follows you to another machine.
  5. Add the people who need access, scoped to their groups.

Three profiles are free, which is enough to move one client across and see whether the shape suits you before committing the rest.

Try it on one client first

Three profiles free, forever. No card.

Download for Windows

Related: agencies, advertising accounts, affiliate marketing, how accounts get linked.