Use case · Agencies
Agency operators on Reddit and ads forums keep hitting the same wall: Meta links people, devices, payment methods, and Business Managers — not just “the browser.” Phantom Profile isolates each client’s cookies and fingerprint on your Windows PC so Client A’s ads session does not sit in Client B’s jar. It does not replace Business Manager structure, clean proxies, or platform policy.
1 client = 1 profile
Rule
Partner, not owner
Access
Local on PC
Sessions
What breaks in the wild
Themes from ads, seller, and social communities — not a promise that every case matches yours. Platforms change enforcement; treat this as operational hygiene.
Logging into several client Business Managers or ad accounts from the same everyday browser mixes cookies, saved logins, and device signals. Platforms treat that as one operator touching many assets — the pattern ads communities report before integrity disables.
Stacking every client’s ad account under your agency Business Manager looks convenient until verification, payment disputes, or a disable cascades. Seasoned teams have each client own their BM and grant the agency partner access instead of full ownership.
Jumping countries, leaving a VPN on a phone, or sharing one office exit for every client login shows up in agency ban threads as “integrity” and unexpected disables — even when spend is low and niches look normal.
Shared payment methods, recovery emails, and contractor laptops that stay signed into everything link assets faster than fingerprint talk. Isolation in the browser cannot undo a shared Visa across five clients.
Skip these
Personal profile + VPN + every client BM on one Chrome user.
Creating fresh personal accounts to “fix” access after a disable on your main identity.
Promising the antidetect tool alone will stop Meta policy or identity-level bans.
Leaving contractor PCs authorized after they leave the agency.
Working way
Map one Phantom Profile browser profile per client workspace — name it the client, not the media buyer.
Prefer client-owned Business Managers with partner access; keep your agency BM for agency work only.
Bind a dedicated HTTP or SOCKS5 exit per client profile; match timezone and language to that exit. No SSH proxy type in the app.
Sign in to that client’s ads or social property only inside that profile — never from your personal Chrome.
Authorize staff PCs only up to your plan’s device cap; revoke a machine the day someone leaves.
Warm sessions with normal admin behavior. Isolation reduces link risk; it does not erase velocity or policy flags.
For each client: confirm they own the Business Manager (or Page). Request partner / agency access with the minimum roles needed. Do not migrate their ad accounts into your agency BM “for convenience.” Document who pays (their card, not yours) before the first login in a profile.
Create profile → name it CLIENTCODE → assign one static residential or ISP HTTP/SOCKS5 exit in their market → set timezone/language to that exit → launch once empty and confirm IP country on a checker → only then sign into Meta/Google. Never paste that proxy into another client’s profile.
Staff open Phantom Profile on an authorized PC, launch only the clients they work today, and close those profiles when done. Do not export cookies to Chrome. When someone leaves, revoke their PC seat the same day and rotate any shared vault passwords that were not per-client.
Stop logging the same identity from random networks. Check whether payment, BM ownership, or a personal profile was the link — not only the antidetect layer. Isolation reduces fingerprint mixing; it does not reopen an identity-level ban.
Phantom Profile keeps each client’s cookies, cache, and site passwords on that profile’s folder on your PC. The cloud account only holds login, plan limits, devices, and optional profile names — not Meta sessions. Use groups and paint colors to keep a roster readable. There is no window synchronizer yet; do not expect mirrored clicks across clients.
Product detail: features · Plans & dollars: Pricing · Basics: home FAQ.
Related: Features · All use cases · Pricing · Download · Contact
When the roster grows, pick a plan on Pricing — caps are not listed on this playbook.
Next step
Create an account, then install the Windows app.
