Afina for Beginners in Simple Terms. Part 2. Profiles, Fingerprints, and Proxies

In the first part, we discussed who needs Afina and what pain points it relieves. Now it's time to answer the main technical question in simple terms: how does all this work? There are three key entities in the game: the profile, the digital fingerprint, and the proxy.
In short: a profile is a separate "mini-computer" inside Afina, the fingerprint is its "appearance" in the eyes of websites, and the proxy is the IP address and location from which this mini-computer accesses the internet.
What is a profile in Afina
A profile in Afina can be thought of as a separate virtual browser within the program. Each profile has its own environment that does not intersect with the others.
For each profile, the following are stored separately:
- Cookies and sessions (logins, authorizations, "remember me", etc.);
- Browsing history and local site data;
- A set of technical device parameters (fingerprint);
- A proxy and, consequently, an IP address and geolocation.
If you have 20 accounts, you create 20 profiles — and to a website, each of them looks like a separate, real person with their own device and their own IP, rather than 20 clones on a single laptop.
Why strict profile isolation is needed
The main idea behind profiles is to prevent accounts from dragging each other down. In a regular browser:
- Cookies mix, and sessions from different logins can intersect;
- The exact same browser and IP are exposed across all accounts;
- If one account triggers suspicious activity, it becomes a marker for the rest.
In Afina, each profile operates within its own container. This provides three important effects:
- If one account is blocked, the others do not "burn automatically" because they live in different profiles;
- Cookies and sessions do not overlap — one login does not expose another;
- You can safely test different funnels, offers, and creatives by separating them into profiles and groups.
Essentially, Afina helps sort the mess of dozens of accounts into neat boxes, each with its own name, its own IP, and its own set of parameters.
What is a digital fingerprint
Every time you visit a website, your browser transmits much more information about itself than just "I am Chrome on Windows." Websites and anti-fraud systems usually see:
- The operating system and its version;
- Language and timezone;
- Screen size and scaling;
- A list of installed fonts;
- Data about the graphics card and drivers;
- The specifics of how JavaScript, Canvas, WebGL, etc., operate.
This combination forms the unique "digital fingerprint" of the device. Even if you change your IP through a proxy but log into dozens of accounts using the exact same fingerprint, platforms can easily figure out that the same browser is behind them.
Afina solves this problem by:
- Managing these parameters through a Chromium-based anti-detect engine;
- Generating plausible combinations that look like real devices;
- Preventing different profiles from sharing data with each other.
As a result, each "box" (profile) gets its own fingerprint, and to the website, they appear as different devices, not one weird browser with a hundred accounts.
Why proxies and IPs are needed for each profile
An anti-detect browser does not hide your real IP by itself — that is the job of a proxy server. A proxy is an intermediary server: you connect to it, and it goes out to the internet on your behalf, substituting its own IP and location.
In combination with Afina, it looks like this:
- Afina manages the "appearance" of the browser (fingerprint: system, language, timezone, fonts, etc.);
- The proxy sets the IP address and country/city that the website sees;
- Together, this gives the account a unique "device + IP" combination, distinct from other profiles.
Importantly, in Afina, a proxy is not set "once for the whole browser." It is linked to a specific profile:
- Each profile can use its own separate proxy;
- A common setup is "one profile = one IP" (or an IP pool if the provider uses rotation);
- You can quickly assign different proxies to a group of profiles through a convenient interface.
This way, an ad cabinet, a store, or a crypto account lives in its own "profile + fingerprint + proxy" bundle and does not cross paths with others.
How it looks in practice
Let's take a simple scenario. You have:
- 5 advertising cabinets for different offers;
- 10 working social media accounts;
- Several marketplace accounts.
In Afina, you can:
- Create separate profile groups for arbitrage, SMM, and e-commerce;
- Assign a unique fingerprint and link a separate proxy to each profile;
- Store logins, cookies, and history for each project separately without mixing them.
As a result:
- A cabinet for a white-hat offer doesn't show up next to an aggressive gray-hat funnel;
- Clients' social media accounts don't intersect with your testing profiles;
- A marketplace store doesn't look like a clone of another store on the same device.
If one account gets banned, it doesn't trigger a chain reaction: the others live safely in their containers.
In short: how to remember the profile + fingerprint + proxy combo
You can remember this using a simple analogy: you have several employees who go to different offices.
- The profile is the "employee" themselves: they have their own habits, history, and tasks.
- The fingerprint is their appearance and demeanor: height, clothing, gait.
- The proxy is the address of the office they work from (country, city, IP).
If all employees look identical and come from the exact same office, they will be noticed quickly. Afina allows you to ensure that everyone has their own unique combination of these three parameters.
Now that it's clear how profiles, fingerprints, and proxies work, the logical next step is to stop doing everything manually. In the third part, we will look at how to set up visual scripts and scheduled tasks in Afina so that the browser handles the routine itself, without any code.
