Telegram brand channels on a local profile

I operate brand Telegram channels I already control. I will not write ban-recovery steps. Isolation here is a local browser profile for Telegram Web, plus the same rule as every other login: do not mix brand, personal, and ads cookies.

The useful caveat: MaskWright is a desktop browser. Telegram's native app is a different client with its own session. Web is not a full replacement for every Telegram feature. Authorized accounts only.

Web session is still a session

Telegram Web stores login state in the browser. Two brand accounts in one Chromium folder share that store. Cookie jars are not optional. Multiple accounts on one PC.

MaskWright 0.1: Windows 10/11, per-profile user-data-dir. profiles.json is encrypted. Chromium user data is not. No cloud phones. Bring your own HTTP or SOCKS5 if that brand already uses an exit.

Native app versus web

I use the native Telegram app on a machine I control for the features web lacks. I do not paste a mobile UA onto a desktop profile and call it Android. I do not rent a cloud phone so a vendor holds the session.

2FA and the phone number stay with the person who owns the account. I do not clone sessions onto a contractor's laptop. Add them as admins in Telegram's official admin tools.

Other brand logins stay out

Discord: Discord brand and community rooms. X: X brand accounts, X Ads Manager isolation. Unofficial helpers: X API versus unofficial helpers. Google: Gmail and Google account isolation.

What I will not write

Recovery from a banned number. Mass DM. Scraping member lists. Unofficial clients that copy the session.

If Telegram asked for a check, complete it as the owner on a device you hold.

On a real Windows desk

Telegram Web in MaskWright is acme-tg-web. I confirm which account the QR or phone login bound. I do not scan a QR for a contractor. I add them as channel admins in Telegram's UI.

The native app on my phone or desktop holds the features web lacks. I do not copy session strings between app and browser as onboarding. Session strings are the login.

Channel posts drafts live in ops if they are files. The profile tray is not a DAM. I close web when the admin pass is done. I do not leave a logged-in Telegram Web window in a cafe.

Gmail and X stay other folders. Bulk start is not an excuse to have Telegram, Discord, and ads all cookie-sharing because I used one profile with many tabs.

If Telegram asked for a phone check, I complete it on the number I own. I do not write a second-SIM farm.

FAQ

One phone number, two brands?

Telegram's account model is number-based. Follow Telegram's rules. A second profile does not invent a second number. I will not write number farms.

Is web enough for a brand channel?

For some admin tasks, yes. Check the feature on web before you promise a client it lives in MaskWright.

Cookie export as onboarding?

No. Add admins. Cookie import files are plaintext. Treat them as keys for machines you control, not as staff kits.

Cloud Telegram?

The vendor holds the session. I keep brand admin on local disk or on a native app I control. Compare local versus cloud.

Can I run Telegram Web and the native app as two "backups" of the same brand?

Two clients holding one account is messy. Pick one primary for admin. Do not treat a second client as a spare identity.

Operate channels you already own. Put Telegram Web in a local folder if you use web. Invite admins. Do not write recovery theater.

I skip session-string onboarding, number farms, and ban-recovery chapters. I add admins in Telegram's UI. I keep file drafts in ops. I complete phone checks on the number I own. I close web when the pass is done.

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