Airbnb listing isolation for authorized hosts

I follow Airbnb's one-account rule where it applies. I will not write extra-host-account theater. Isolation on this desk is for jobs that should not share cookies: hosting admin versus personal travel versus a storefront you also run.

The useful caveat: competitor posts push extra accounts. Read Airbnb's current host terms. This is not legal advice. Authorized listings and co-hosts only.

What I actually split

Hosting: listings you own or co-host, calendar, messages, official co-host access.

Personal travel: trips you book as a guest, in a different profile or everyday Chrome.

Other businesses: Shopify, eBay, Etsy, affiliate dashboards. Those are other folders. Ecommerce accounts on one PC. Shopify multi-store isolation. eBay seller isolation. Etsy shop isolation. Affiliate dashboard isolation. Affiliate research rooms.

Do not click your own listing's affiliate-style links. Affiliate self-clicks are fraud. Affiliate extensions we refuse.

MaskWright 0.1: Windows 10/11, per-profile user-data-dir. profiles.json is encrypted. Chromium user data is not. No seats. Co-hosts get Airbnb's official co-host invite, then sign in as themselves. Bring your own HTTP or SOCKS5 only if that hosting entity already uses an exit.

Access

Official co-host and additional host tools Airbnb ships. Not cookie dumps. 2FA on a device they hold.

How I run hosting admin on Windows

The hosting profile is acme-airbnb-host. I sign in as the host or co-host Airbnb already recognizes. Calendar, messages, listing edits. Guest trips I book for myself wait in a personal profile or everyday Chrome if Airbnb's model lets me split them. I do not invent a second host identity to "protect" the first.

Co-hosts get Airbnb's official invite. Their PC, empty profile, their 2FA. Cleaning vendors who need calendar access get whatever Airbnb already offers for that job. They do not get a cookie dump.

Shopify, eBay, and Etsy stay other uuids. Affiliate dashboards stay other uuids. I do not click a tagged URL to my own listing. I do not install unofficial multi-account helpers unpacked into this tree.

Geo check only if this hosting entity already uses an exit. Many hosts just use the house IP. That is allowed for listings they are allowed to host from that house. A new residential line is not a new host.

Messages are guest data. Exports go to ops with a retention rule, not into research, not onto a cloud-synced Desktop both profiles write to.

If Airbnb removed a listing, I follow their process. I do not spawn airbnb-2 in a fresh fingerprint.

FAQ

Multiple listings, one account?

That is Airbnb's normal model. One hosting profile can hold that login. Split guest travel and other businesses.

Property manager with many owners?

Use Airbnb's official hosting tools and the permissions they offer. I will not write a stack of unofficial host identities.

Restore a removed listing with a new profile?

No. Complete Airbnb's process as the host.

Cloud hosting admin?

The vendor holds guest messages. I keep hosting on local disk. Compare local versus cloud.

Can co-hosts share one MaskWright profile on a laptop in the unit?

They can physically. You lose who messaged a guest. Each co-host gets their own OS user or their own PC, plus Airbnb's official access.

Host the listings you are allowed to host. Invite co-hosts. Keep shops and affiliate dashboards in other folders. Do not invent extra Airbnb people.

I skip unofficial extra-account helpers, tagged clicks to my own listing, and a second host uuid as a restore kit. I keep guest messages in ops with a retention rule. I close hosting admin when the calendar pass is done. Household IP is allowed for listings I am allowed to host from that house.

I do not host-message from a cafe on a shared laptop. Guest threads are guest data. If a cleaner needs the calendar, they get Airbnb's official access, then their own empty profile if they use the browser. I still will not stack unofficial host identities.

More notes sit under Ecommerce. Download MaskWright for the Windows launcher.