X brand accounts on a local profile

I keep each X brand account I am authorized to run in its own local profile. Personal X stays out. Ads Manager stays out if that is a different job. I will not write an engagement farm.

The useful caveat: isolation is cookies, localStorage, and extensions on your Windows disk. It is not a substitute for X's rules about spam and related accounts.

One brand login, one folder

Multiple accounts on one PC is the parent how-to. MaskWright 0.1: Windows 10/11, per-profile user-data-dir, no seats, no cloud phones. profiles.json is encrypted. Chromium user data is not. Bring your own HTTP or SOCKS5 if that brand already uses an exit.

X's account switcher is convenient. I still prefer two folders when two brands must not share drafts, DMs, or download trays.

Ads, APIs, and unofficial helpers

Ads: X Ads Manager isolation. If X gave you an official API, use that. X API versus unofficial helpers. Growth extensions that want the session stay out of the brand profile.

Other brand surfaces on the same PC

YouTube Brand Accounts and Studio are Google gravity. Keep them out of X. YouTube Brand Accounts. YouTube Studio on a local profile. YouTube and Google account clusters. Discord and Telegram brand work are other folders. Discord brand and community rooms. Telegram brand channels on a local profile.

How I set it

Empty cookies. Official sign-in. 2FA on a device I hold. Confirm the account switcher is not a pile. Close the profile when posting is done. Invite teammates through X's official team features where they exist. Do not export cookies.

Web is not every mobile feature. I do not paste a mobile UA onto a desktop fingerprint.

On a real Windows desk

Brand X is a named profile. I open x.com, sign in, confirm the account, post, close. I do not leave a draft sitting on a shared tower. Media for posts lives in ops, not in the profile tray.

If Ads Manager is a different login, I do not hop using X's switcher inside the brand folder. I stop this profile and start the ads profile. Switchers are how billing and drafts meet.

Unofficial growth extensions stay off the unpacked list. --load-extension will load whatever I put in the folder. I put nothing that wants the session.

Sticky proxy only if this brand already pays for one. Geo check before password. I do not paste an iPhone UA. Desktop is desktop. 2FA on a device I hold. Team features X actually ships, not a cookie zip.

FAQ

I own three brand accounts. Three profiles?

If they must not share DMs and ads pixels, yes. If X already expects one login to switch among them, match that official model and still keep personal and ads split when those jobs use different logins.

Will a new profile fix a locked account?

No. Complete X's process as the owner. I will not write restore steps.

Is MaskWright an X bot?

No. No Playwright product. Bulk start opens profiles you already run. A person still types.

Cloud X session?

The vendor holds the cookies. I keep brand X on local disk. Compare local versus cloud.

Can I run the official X app and this profile at once on the same login?

Two clients can fight over the same account. I pick web-in-MaskWright or the official app for that brand, not both logged in as a habit. Isolation is still the cookie store in the folder I chose.

Own the account. Put it in a local folder. Invite people. Leave farms and unofficial helpers out.

I skip engagement pods, mobile UAs on desktop, and mailing cookies to an editor. I geo-check a sticky exit if the brand already pays for one. I close the profile when the posting pass is done. Drafts do not sit on a shared tower.

More notes sit under Social media. Download MaskWright for the Windows launcher.