Privacy policy
Last updated 15/09/2026
SigoLogin has two halves: this website, where you buy and manage a plan, and the app on your own machine. They collect different things, so this page treats them separately.
The website
You sign in with Google. Google gives us your email address and your name, and we store those two along with the time you signed up and the time you last signed in. We never receive your Google password.
Payment is a bank transfer handled by SePay. We store the order code, the amount, the plan, and the transaction reference the bank sends back. Your card number and your banking login never reach us, because you type them into your own bank, not into this site.
We also record a few events on this site: sign-up, sign-in, device link codes, team invitations, orders and app downloads. A device link code record includes your IP address. A download record includes the time, your IP address, country, operating system and browser, and your email if you are signed in. To find the country, our server asks the ipwho.is service about that IP address.
Some of those events are reported to the SigoLogin team over Telegram: sign-ups, sign-ins, device link codes, team invitations, new orders, payment QR codes shown, payments received, and app downloads. The message carries your email. A sign-up also carries your name; an invitation, the invited person's email and what they may see; an order or payment, the plan, amount and order code; a download, the IP address, operating system, browser and country.
There is no advertising pixel, no analytics script, and no third-party tracker on this site. You can check with your browser's network tab.
The app: what it sends
Two reasons, and there is no third one. The first is fixing bugs: the log file on your machine only reaches us if you send it, so we only ever see the errors bad enough to complain about. The second is knowing how the product is used, which decides what we build next.
Every record carries a timestamp and is tied to a device through the device token in the request header. The token itself is never part of the record.
When you open the app
| Field | Example | Why we need it |
|---|---|---|
| App version | 0.1.6 | Tells us which build an error belongs to |
| Operating system | windows | Decides which platform we support first |
| OS version | 19.0.0 | Bugs usually cluster by version |
| Browser kernel version | 152.0.7977.83 | Lets us match a bug to a kernel build |
| Your IP address | 222.253.44.35 | Stops one licence being shared across many places, and tells us which markets we are in |
| Country | VN | Market statistics |
When you close the app
| Field | Example | Why we need it |
|---|---|---|
| Seconds the app was open | 4820 | Real usage instead of a guess |
When you open a profile
| Field | Example | Why we need it |
|---|---|---|
| Profile id | de3d9852b13aa2da… | Connects an error to the exact open that caused it. It is a random id, not the profile name |
| Browser kernel version | 152.0.7977.83 | Lets us match a bug to a kernel build |
| Whether a proxy is in use | true | Most failures to open a profile are proxy failures |
| Proxy country | SG | Shows which routes break often |
When something fails
| Field | Example | Why we need it |
|---|---|---|
| Where it happened | mo_profile | Narrows the search |
| The error message | khong dung duoc lop trung chuyen… | The content of the failure |
Error messages are scrubbed before they leave your machine. Any address shaped like scheme://user:password@host has its login replaced with three asterisks, and anything past 500 characters is cut. The host and port are kept, so a failed proxy connection can carry that proxy's address and port.
To find this computer's IP address and country, the app asks the ipwho.is service each time it opens, and asks again through a proxy whenever that proxy is checked. The service sees the IP address the request comes from and nothing else. For the Your data screen, our server also looks up the city of the people on your team from the IP address their app last reported, and returns only the city name.
If you send a feature request from the app, we store its title, the details you wrote and the app version with your account, and show you its status and our reply. The title, your email and the first 300 characters of the details are also posted to the SigoLogin team's Telegram group.
When you open a profile: signing the fingerprint
SigoLogin's browser only runs with a fingerprint configuration signed by our server. When you open a profile that has no valid signature, or whose fingerprint has just changed, the app sends that profile's full fingerprint to our server to be signed. The fingerprint includes the user agent, timezone, languages, and the exit IP address of the proxy if the profile has one. The server signs it and sends it straight back without storing the fingerprint in its database. A signature lasts seven days, and the app asks for a new one when fewer than two days remain.
What the app does send about a profile
So that you can manage your profiles from this site, the app sends a small set of fields for every profile you own, including ones you have never opened: name, group, tags, colour, and the operating system and device class the profile declares. The list goes up when the app starts, when you create or delete a profile, when you come back to the app window, when you press refresh, and each time you open a profile. It carries no cookies, proxy, saved accounts or notes.
What the app never sends
The app does not send the things below to our servers. For the usage log in the tables above there is also an automated test: the build fails if a forbidden field gets into a record.
- Your notes on a profile, unless you share that profile. That box is free text, and people do paste passwords into it.
- Proxy usernames and passwords, unless you share the profile. A proxy's address and port can appear in an error message, as noted above.
- Accounts you save next to a profile: the name, username, password and 2FA key, unless you share the profile. The password and the 2FA key are wrapped with the same Windows protection as proxy passwords.
- Cookies, saved passwords and login data inside a profile. They sit in the profile folder on your disk and go nowhere — unless you share that profile with someone, which is described below.
- The device token inside a record. It travels only in the authentication header.
- Anything you browse. The app does not read it, does not log it, does not send it.
When you share a profile
Putting a profile in someone else's hands is the one exception to the list above. They sit at another machine, so what normally stays on yours has to travel. There are two ways that happens, and you open both of them deliberately.
- The first is the Share button on one specific profile. Only that profile travels.
- The second is your team: assign a group to a member on the Team page and EVERY profile in that group travels, including ones you create later. Tick "See all profiles" for someone and all of your profiles travel. Your app uploads them by itself at its next sync, with nothing to click. A profile in no group assigned to anyone is never packed up and sent.
- The bundle carries the profile name and note, the fingerprint, the proxy including its password, the cookies, and the accounts you saved next to the profile including passwords and 2FA keys. Leave any of those out and the person you shared with cannot actually use the profile.
- The bundle is encrypted with AES-256-GCM while stored on our server. The key lives in our server configuration, so to be plain about it: this is encryption at rest, not end-to-end encryption, and we are technically able to read the bundle.
- When nobody can see it any more, the bundle is deleted. Removing the last person, taking a member out of a group, or moving the profile to a group nobody is assigned to all end the same way. We keep no copy.
What stays on your machine
Profiles are folders on your disk. The cookies, sessions, saved logins and history of each profile live there and are not uploaded, unless you share the profile. The fingerprint only goes up to be signed and comes straight back. For profiles you do not share we hold no copy, which also means we cannot restore them for you if the machine is lost.
Proxy passwords, and the passwords and 2FA keys of saved accounts, are the secrets the app has to keep on disk. They are wrapped with the Windows data protection service and the key is tied to your Windows account, so copying the data folder to another machine or another user does not carry them with it.
When you have no connection
Records queue in a file inside the data folder and go out the next time the app runs. The file is capped at 2 MB; past that the oldest records are dropped rather than kept forever.
Devices on your account
Activating a device stores its machine name, the Windows machine ID, the operating system, the app version, the kernel version, and the IP address it activated from. The device token is stored as a SHA-256 hash, never in the clear, so a leak of our database would not let anyone impersonate your device.
Cookies
This site sets a sign-in cookie so you stay signed in, and remembers the language you chose. Nothing else.
How long we keep it
Account, payment and subscription records are kept while your account exists, because they are the record of what you bought. App and error records are kept for the same period and deleted on request. Write to us and say what you want removed.
What you can ask for
Ask for a copy of what we hold about you, ask for it to be corrected, or ask for it to be deleted. Deleting the account data also ends the subscription, since the subscription is attached to it.
This page is written from the same document our developers work against, and is updated together with any change in what the app sends. The latest review checked it against every network call in the source code.