Ad accounts

Losing one ad account is a cost of doing business. Losing five because one was reviewed is a different problem, and it is rarely about the ban itself.

It is about what the platform can see those five accounts have in common. Open two consoles in one browser and the list is long.

• One jar and one storage

  The login cookie is the shortest link there is, and local storage, databases and service workers persist per browser too.

• One device

  Screen, cores, memory, graphics strings, fonts, timezone and language are identical in every window.

• One exit address

  Two consoles reached from one address minutes apart are related without anyone looking hard.

• One payment identity

  A saved card, an autofilled billing address and the browser's payment profile follow the browser.

Each of the usual answers cuts one of those links and leaves the rest. A reviewer looking at one account has the others one query away.

The answer that cuts every link costs a whole machine, and its updates, for every account you run.

Picking a scenario sets the opening address, the tracker lists, the link cleaning, the page scripts and the rows of the Safe daily ceiling section. It is not a label on a card but a set of settings applied at every launch.

The app reads the same lines at launch and again when it draws the card.

A blocklist built for privacy browsing is the wrong instrument inside an ad console. Cut one request too many and a creative will not upload.

What is left is cross-account correlation: conversion and audience pixels, signal endpoints, the third parties that sell the join. Requests a console needs in order to sign in, bill or work are excluded on purpose.

The fingerprint is derived at launch from the same inputs, so an account does not find its computer changed overnight.

• Template

  One of five: macOS, Windows, Linux, Android phone, Android tablet.

• Profile id

  Seeds the graphics pair, the screen and the platform version out of generation 4's pools.

• Proxy country

  Measured through the proxy itself, then mapped to a timezone and a language stack that agree with it.

• Engine version

  The user agent and the client hints carry the version of the engine that renders the page.

That is what makes a shared profile usable in an agency. A media buyer opening it on their own laptop gets the readings the account saw yesterday, and their real machine does not leak into it.

A saved card, a billing address and an autofilled name are browser data, and every profile has a directory of its own. Two ad accounts are two directories.

The account's own login pair is held by the app (Sign-in details in the profile menu) rather than by the browser, and never sent to our server. A synced profile carries its id, name, group, scenario, template, proxy and tags, and no field for the login password.

• The profile directory

  Cookies, storage, service workers, saved cards and autofill.

• The account password

  Written beside the profile. The system seals it on Windows only: on macOS the key ships inside the program, and on Linux it is written as typed.

• The one-time code

  The secret belongs to the profile, and the code is generated beside it.

• The proxy password

  Never placed on the command line, where a credential shows up in any process listing on the machine.

• The browser's own keys

  The engine encrypts its own cookie and password store instead of asking the system for a key, which keeps a live session portable.

A role covers the whole workspace, so a role alone cannot hide clients from a new buyer. Group access narrows it, one row per member per group.

Once access is set, a member never sees a profile that is in no group, and opening one by its id gives them profile not found rather than forbidden.

• Owner

  Everything, and cannot be removed from their own workspace or restricted to groups.

• Admin

  Billing, the team, the history, other members' profiles and machines. Hands out group access.

• Manager

  Shared working resources: groups and the proxy library, including Change IP on a mobile proxy. No money, no team.

• Operator and member

  Work with the profiles they were given, inside the groups they can see. Change nothing shared.

• No groups chosen

  The member sees every group, and the window says so. Taking their last group away does not strip their access, it opens everything.

• Seats

  Business includes 3, Enterprise 20, and additional seats are 3 dollars a month each.

The page counter is the only number the app measures. It counts top-level navigations, survives a relaunch on the same day and starts fresh at midnight.

The five rows of the Safe daily ceiling section are numbers, not counters, ramped by the same curve. Payment edits are the strictest, because that change is the likeliest to put a human reviewer in front of the account.