The logins for an account live on the profile that uses them, 2FA key and all, and the app produces the six digits itself. Everything you have set up goes into one encrypted file that you hold the passphrase to. And there is a screen in the app that tells you which of it leaves your machine.
Start freeNone of this is about detection. It is the four other things you are keeping in step by hand while you work.
Fingerprints, the profile list, team work and proxies each have a page of their own. These four do not, and they are the ones people find in the second week.
Three or four accounts hang off one profile more often than one does, and each gets a row of its own: a name picked from a list of the sites these accounts actually sit on, a username, a password, and the 2FA key. The password and the key are sealed by Windows before they reach the disk, under a key Windows keeps and ties to the Windows account you are signed in to. Copy the database to another machine and neither of them opens, which is deliberate, and which is why the export file exists.
The 2FA key is not kept as a code to read later. Paste the string the site showed when you turned two-factor on, and from then on the app computes the digits itself: HMAC-SHA1 over the clock, six digits, a new one every thirty seconds, checked against the test vectors published with RFC 6238. It shows the code with the seconds left on it and a button to copy. No phone in that loop, and no browser extension either.
One file, extension .sigobak. The first thirty-six bytes are a marker, a random salt and a random nonce; everything after them is AES-256-GCM over gzipped JSON, keyed from the passphrase you type through 210,000 rounds of PBKDF2-HMAC-SHA256. Eight characters at the least, typed twice, and no button anywhere writes the file unencrypted. Two exports made with the same passphrase share no key at all, because the salt and the nonce are drawn again for each one.
Restoring merges rather than replaces. A profile already on this machine is left untouched and named in the report, so an old file cannot write over a session you are in the middle of, and the secrets that do come back are resealed to the machine they land on. The refusals are separate on purpose: a wrong passphrase, a file that is not one of ours, a single flipped byte, and a file written by a newer version each get their own message rather than one failure that tells you nothing.
Everything the app knows sits in one directory called SigologinData: a SQLite database for the account, a cache of the browser kernels it has downloaded, and one Chromium directory per profile, so nothing a profile writes can reach another one. The database is an ordinary file. It is not a service you rent, and reading it needs nothing of ours running.
Where that directory goes is a decision you get to make. The app looks at the SIGOLOGIN_DATA_DIR variable first, then for a SigologinData folder sitting beside its own executable, and only then falls back to the Windows application data folder. So the profiles can live on a second drive without a symlink and without reinstalling. The saved passwords are the one thing that will not move with the folder, because the seal Windows put on them belongs to one Windows account, and moving those is what the export file is for.
Open it from the sidebar and it draws three things: what stays in the folder on your disk, what goes up to our server, and what moves only when you share a profile. It has a second view for working in a team, because sharing is the moment cookies and saved logins have to travel, and it shows the city each teammate is opening from.
That list was written from the network calls themselves, one call at a time, which is why it sits on a screen in the app and not only in a policy document. Three destinations and no fourth: cookies, saved passwords and notes on your disk; a profile's name, group, tags and colour on our server, which is how this site can show you the list; and the whole bundle, which moves only for a profile you shared or handed to a team member. The key that opens a stored bundle is ours, so it is encryption while we hold the file and not end to end, and the screen says which of the two it is rather than leaving the word encrypted to do that work.
None of these sells the product. Each one is a reason not to be annoyed by it.
A running app asks for a new version every ten minutes. An optional one arrives as a bar along the top rather than a dialog over what you are doing, because a dialog thrown in front of somebody halfway through two hundred profiles gets dismissed unread. A release marked mandatory does get the dialog, and that dialog offers update or exit.
The downloaded installer is hashed with SHA-256 and compared against the published manifest before it is allowed to start. Before it starts, open browsers are asked to quit so their cookies reach the disk, and any shared profile hands its lease back. The installer is not code-signed yet, so that hash is the whole of the check: when there is a certificate, the one to add is the Windows signature on the same file.
There is a screen in the app for asking. A title, up to four thousand characters of detail, and the three newest of yours stay listed under the form so you can see the last one went. Ten a day per account.
The full list is on this site, each request with the status we gave it and our reply written underneath. Which means the answer does not depend on you finding the chat thread again in March.
Each profile is a real Chromium user data directory that survives being closed, and the app never passes the flag that turns extensions off. An extension installed inside a profile belongs to that profile and stays in it.
What the app adds is nothing. The usual way to hand Chromium a proxy username and password is a small extension that answers the auth prompt, and any page that looks can see that extension, which makes it one more thing to be recognised by; there is a local relay instead. A screen for installing and switching extensions across many profiles at once is not built.
Share a profile with your team and its cookies and signed-in state travel with it, stored encrypted on our server.
Our server encrypts that bundle while it holds it, under a key of ours, which means we can read it. What is in a bundle, who can open it and what happens when you stop sharing are all on the team page.
Your name, time zone, country and interface language are kept on the account, so the second machine you link comes up the way you left the first one. The email is the one field you cannot change there, because it is the account.
Switching language changes the words before the network call goes out. A button that waits for a server to relabel itself reads as a broken button, and the setting is worth nothing if the app is offline when you want it.
Which way in sits at the top depends on the language you are reading this in.
Messages are answered by the people who build the thing and run accounts on it, which is why a question about the browser kernel does not come back as a link to an article. Zalo is the main channel for customers in Vietnam and Telegram for everyone else, and both are read by the same people.
This site is written in ten languages. The app itself is in Vietnamese and English, and there is no point pretending otherwise: someone reading the Korean pages installs an interface in English.
| Channel | What it is for |
|---|---|
| Telegram | Fastest way to reach us |
| Messenger | If you already have us on Facebook |
| For attachments, invoices and anything about payment |
The floating button in the corner offers whichever of these fits the language of the page you are on. The contact page lists every one of them with its address.
Nothing below is in the app yet, and none of it is part of what you pay for today. Each one goes on the release log when it ships.
The syntax stays compatible with AdsPower, so Selenium, Puppeteer and Playwright scripts you already run move across with almost nothing to change.
Install extensions per group of profiles and switch them in bulk. Your extensions, not ones the software injects.
Ready-made scripts for repetitive work on TikTok, Shopee and Facebook. Run them on a schedule or in bulk.
A history of each profile's launches: when it ran, which kernel version, and whether a proxy was in use. Proxy addresses and passwords never leave your machine.
Take the account you sign into most. Put the username, the password and the 2FA string on its profile, then close the spreadsheet and work that way for a day before doing the other two hundred.
Pick a passphrase you will still have in a year and write it down somewhere that is not the machine you are backing up. Lose it and the file goes with it: we hold no copy and no way in.
It takes two minutes and it is the only place that says which of your data is on your disk and which is on ours. Better to know that before the first profile goes up than after.
It generates them. Paste the string the site gave you when you turned two-factor on and the app produces the six digits from it, HMAC-SHA1 over the clock, a new code every thirty seconds. The key itself is never handed back to the screen; only the code is.
No. There is no autofill in this build. The password and the code each have a copy button and you paste them. Anything more would mean the app reaching into the page the browser is showing, and it does not do that.
No. Windows holds the key and ties it to the Windows account you are signed in to, so the file is useless on another machine or under another user, and anyone already signed in to your Windows account can reveal a password in one click. Lock Windows when you leave the desk.
Every profile on the account, because there is no picker: export takes all of them. Two kinds are left out, profiles somebody else shared with you and profiles that are open at the moment you export, and both are named in the report so you can close them and run it again. The Chromium directory is not in the file either, which is why it stays small enough to send; a site that keeps your session in local storage will ask you to sign in again after a restore. The full list of what a profile carries into the file is on the profile management page.
Not in this build. The encrypted file is how profiles move between your own machines today, and you are the one who moves it. Sync between your machines is on the list above.
Yes. A profile is a real Chromium user data directory and the app does not disable extensions, so what you install inside one stays inside that one. What does not exist yet is a screen that installs and switches extensions across many profiles at once.
Vietnamese and English. This site is in ten languages and the app is in two, and that gap is real rather than a translation still loading.
Three profiles, no card and no end date. The saved logins, the 2FA codes, the encrypted export and the data screen are the same on Free as they are on Business; the number of profiles is what changes.
