Transfer a profile to another account

The "Transfer to another account…" item in the profile menu hands a profile to another person whole: under the same number, which means the same machine for websites. The recipient accepts or rejects it in the "Profile transfers" window, and after accepting the profile leaves your account.

48 hours: The recipient has to answer in
7 days after accepting: To open the transfer file
Up to 10: Profiles at once
The workspace owner on a paid plan: Who sends

What goes to the recipient

The profile number, its template and generation move to the recipient with the record in the account. The profile builds its fingerprint from them at launch, so at the recipient a site sees the same machine.

Everything else travels in an encrypted transfer file the app saves on your side. The file is built even without the session: it carries your manual fingerprint edits and the settings kept only on this computer.

What	How it travels
Profile number, template, generation and fingerprint seed	With the record in the account, at accepting
Name, scenario, extensions from the catalog	With the record in the account
Manual fingerprint edits, start page, launch without a window, address change, pinned browser version	In the transfer file
Cookies, site storage, tabs, bookmarks, browser passwords, extension data, login and 2FA key	In the file, with "Transfer with session (cookies and logins)"
Extensions installed from a file	As a folder in the file when the extension has a key. The window names the rest before sending
Proxy: address, port, login, password, country	With "Transfer with proxy"
Notes, tags and status	With "With notes, tags and status"
Your own server exit	Does not travel. The recipient sees its country only
Browsing history, autofill, downloads, browser components	Do not travel

Cookies between systems

Cookies and passwords saved by the browser move in the file only between two Macs or two Linux computers. The browser encrypts them with a key that on Windows is tied to the machine itself, and Mac and Linux each use their own.

From Windows and between different systems the recipient signs in to the accounts again. The transfer window says so before you press "Transfer".

The session goes past the server

You send the transfer file yourself: by email, in a messenger or on a USB stick. Our server keeps the request and a random key to the file, sealed with our key, and the file itself does not reach the server.

Only the recipient gets the key, and only after accepting. It is erased as soon as the file is placed, on rejection, cancelling and expiry, and 7 days after accepting at the latest.

While the recipient decides

The recipient has 48 hours to answer. Until then the profile does not open and cannot be edited: the server refuses on your other computers and for teammates the profile is shared with.

Changed your mind: "Cancel transfer" in the "Profile transfers" window. Rejection, cancelling and expiry bring the profile back to work as it was.

The recipient decides

A strip with the number of incoming transfers appears above the recipient's profile list, and "Profile transfers" in the account menu opens the "Received" and "Sent" sections. The card shows who sent it, what travels and how many plan slots it takes.

Accepted profiles go into a new group named with the date, into a group of your choice or into no group. You can answer in the dashboard on the website too: the recipient's app catches up by itself.

The same browser at the recipient

A profile from ARMANOS Browser does not open in the built-in browser, and the other way round, even when accepted in the dashboard: sites would see a different browser under the same logins. The recipient needs the same ARMANOS Browser version or a newer one.

Without a proxy the profile goes online from the recipient's address. The accept window names the country the profile went online from, and the first launch asks when the country differs.

After accepting you keep nothing

The profile leaves your account on all your computers and for teammates: the record, the sessions of both browsers, the history, extensions and the copy in the sync folder. On your computers the notification names the account that accepted it.

A line about the transfer stays in the account log on both sides. Only the recipient can give the profile back, with a transfer of their own.

What this does not do

It does not transfer from the free plan: sending needs a paid plan, and receiving works on any plan with enough slots.
It is not revocable access. Only the recipient can give the profile back.
Cookies and browser passwords do not move from Windows or between different systems: the recipient signs in to the accounts again.
The fingerprint is derived from the profile number, but ARMANOS Browser does not yet close one trace of the computer itself: a page can ask whether the system has a font with an exact name. On the recipient's computer the answer is the recipient's own.
It is not storage. You send the transfer file yourself, and if the recipient does not open it within 7 days after accepting, the session is lost for both of you.
The sender may have kept a copy of the logins. The recipient should change the passwords of accounts that are theirs now.
Inside your own team a transfer is not needed: share the profile with a teammate instead.
An API key cannot transfer a profile: a person does it with their account password.

How to check

Each claim above lives in one file.

Accepting moves the record under the same number; the waiting profile is locked; the workspace owner on a paid plan sends; slots are counted on the recipient's side; the file key goes only to the recipient and only after accepting: apps/server/src/profile-transfers/profile-transfers.service.ts · apps/server/test/передача-профиля.js · apps/server/test/передача-профиля-взлом.js
The server refuses cookies, logins and 2FA keys in a transfer request: apps/server/test/куки-и-входы-сервер-не-примет.js
Accept, cancel and the last free slot at once: one decision: apps/server/test/передача-профиля-гонки-postgres.js
Sending from the window, accepting, rejecting, placing the file; nothing left with the sender and the team after accepting: apps/desktop/test/передача-профиля-живьём.js · apps/desktop/test/передача-профиля-проверка-живьём.js
The same machine at the recipient: the fingerprint probe and the API shape match, the browser is the same version: apps/desktop/test/передача-без-новой-приметы.js
What goes in the file and what does not; paths of your computer stay out of it: apps/desktop/src/lib/передача-профиля.js · apps/desktop/test/передача-профиля-разбор.js
Answering from the dashboard: apps/web/components/dashboard/TransfersPanel.tsx · apps/web/test/передача-профиля-кабинет.js

Questions

Who can send?: The workspace owner on a paid plan. The owner gives admins this right with "Admins may transfer profiles to other accounts" in the "Profile transfers" window.
Who can accept?: Anyone with their own account on any plan, with enough slots in their workspace for every profile of the transfer. A member of someone else's team accepts into their own workspace, not into that team. A login created by a team cannot accept.
Is the account password needed?: Yes, when sending, and the app code when two-step sign-in is on. Wrong entries count together with wrong sign-ins.
What if the recipient does not answer?: After 48 hours the transfer expires, the profile is back to work on your side and the file key is erased.
Does a site see anything new?: The machine is the same: number, template and generation stay and manual edits travel in the file. What can differ is on the recipient's side: the address without the proxy, a newer browser version and system fonts asked by exact name.
Can I transfer a profile with a profile password?: Remove the profile password first: the recipient does not know it.