You bought a pool of proxies, shared the logins with your colleagues — and within a week, the accounts started getting banned one after another. Sound familiar? Most often, the reason is not the quality of the proxies, but how the credentials are stored and transmitted. A leak of a single password file or a screenshot in Telegram — and your IPs are already being used by competitors or fraudsters. In this guide, we will discuss how to establish secure storage of proxy data for teams of any size.
Why Proxy Credentials Leak and What It Threatens
Proxy credentials are not just a username and password. They are the key to your working infrastructure. If IP addresses, ports, and authorization data fall into the wrong hands, the consequences can be more serious than they seem at first glance.
Let's consider real leak scenarios that arbitrage specialists, SMM professionals, and teams working with advertising accounts face:
- Screenshot in a work chat. A colleague takes a screenshot of the proxy settings and sends it in a general Telegram chat. A month later, someone from former employees uses this data.
- Excel file on a shared drive. A table with proxies is stored in a publicly accessible folder on Google Drive or Yandex.Disk. Anyone with the link can see your credentials.
- Copying to clipboard. The username and password are copied to the clipboard — and accidentally pasted into the wrong field. Or synchronized through an unsecured clipboard manager.
- Storing in the browser. Data is saved in the standard Chrome or Firefox browser. If the computer is infected with a stealer, all saved passwords leak instantly.
- Transmission through messengers. The username and password are sent in a private message via WhatsApp or Telegram without encryption. The chat history is stored on servers.
What Happens After a Leak? Unauthorized individuals start using your proxies. This means: IP addresses are quickly "burned" due to suspicious activity, your accounts in Facebook Ads, TikTok Ads, or Instagram get blocked, and the proxy provider may suspend access due to violation of terms of use. In the worst case — your advertising accounts are linked to the same IPs used by fraudsters and get caught in a mass ban.
Teams of 3-15 people are particularly vulnerable: there are already several people with access, but there are still no proper security processes in place. This guide will be most useful for such teams.
What Exactly Needs to Be Stored: Proxy Data Structure
Before choosing a storage method, let's clarify what data constitutes "proxy credentials." This will help structure the storage properly and avoid confusion during setup.
The complete set of data for one proxy looks like this:
| Parameter | Example | Sensitivity Level |
|---|---|---|
| IP address or host | proxy.example.com | Medium |
| Port | 8080 / 1080 | Low |
| Username | user_12345 | High |
| Password | xK9#mPq2 | Critical |
| Protocol | SOCKS5 / HTTP | Low |
| Proxy type | Residential / Mobile | Low |
| Geolocation | RU / US / DE | Low |
| Linked account | FB_acc_007 | Medium |
| Expiration date | 2025-03-31 | Low |
Note: the password has a critical sensitivity level, while the username has a high level. These two fields require maximum protection. The other data (IP, port, geolocation) is less critical — they do not provide access without the username/password pair. However, it is still not advisable to store everything together in one unprotected location.
If you are using residential proxies with authorization via a white IP (whitelist), you do not have a username and password — only the IP address in the allowed list. This is more convenient from a security standpoint but requires separate control over whose IPs are added to the whitelist.
Password Managers for Teams: Bitwarden, 1Password, Keeper
A password manager is the primary tool for securely storing proxy credentials. It encrypts data, manages access, and maintains a history of changes. Forget about Excel spreadsheets and notes on your phone — that's old school.
Here are three managers that teams in arbitrage and SMM actually use:
Bitwarden — Free and Open Source
Bitwarden is the most popular choice for small teams. The free plan allows storing an unlimited number of passwords and synchronizing them across devices. The team plan (starting at $3/month per person) adds shared collections, rights management, and audit logs.
How to store proxies in Bitwarden: create a separate collection called "Proxies." For each proxy, create a record of type "Login" — enter the username in the login field and the proxy password in the password field. In the URI field, specify the host address. In the notes, add the port, protocol, geolocation, and linked account. This way, all data will be in one place and encrypted.
1Password — For Teams with High Requirements
1Password Teams is a paid solution (starting at $19.95/month for a team of up to 10 people), but it offers more flexible access management. You can create vaults for specific projects, assign roles (view only, edit, admin), and see who accessed a specific record and when. For a team of 5-15 people, where each has their own pool of proxies, this is very convenient.
Feature for Arbitrage Specialists: in 1Password, you can create custom fields. Create a "Proxy" record template with fields: Host, Port, Username, Password, Protocol, Geo, Linked Account. This will speed up work and eliminate errors during data entry.
Keeper — With Advanced Auditing
Keeper Business is suitable for teams that value control and reporting. The system maintains a detailed audit log: who viewed the password, who copied it, who changed it. If proxy credentials do leak — you will be able to quickly identify the source. The price starts at $4.50/user per month.
💡 Tip for Arbitrage Teams
Divide proxies by projects into separate collections/vaults. For example: "FB Ads — RU", "TikTok Ads — US", "Instagram SMM — Client A". A buyer working with Facebook should not see proxies for TikTok from another buyer. The principle of least privilege reduces risks when an employee leaves or one account is hacked.
Storing Proxies in Anti-Detect Browsers: Dolphin, AdsPower, GoLogin
Anti-detect browsers are the main working tool for arbitrage specialists and SMM professionals. In them, proxies are tied to specific profiles, and credentials are stored within the browser's system. This is convenient, but this approach has its risks and security rules.
Dolphin Anty
In Dolphin Anty, proxies are entered when creating a profile in the "Proxy" field. Credentials (username and password) are stored in the Dolphin cloud and synchronized among all team members who have access to the profile. This means: if the Dolphin account is hacked — the attacker gets all the proxies at once.
What to do: enable two-factor authentication (2FA) in the Dolphin account settings. Use a separate email for registration in the anti-detect browser — not corporate and not personal. Limit team members' rights: a regular buyer should only have access to their profiles, not the entire database.
AdsPower
AdsPower stores proxy data similarly — in the cloud, tied to the profile. The advantage of AdsPower: there is a built-in proxy manager (Proxy Manager section), where you can add a proxy once and then link it to multiple profiles without re-entering credentials. This is convenient but creates a single point of failure.
Recommendation: use the Proxy Manager only for proxies assigned to a specific employee. Do not create a shared pool of proxies in the Proxy Manager with access for the entire team — this is a direct path to leakage.
GoLogin and Multilogin
GoLogin and Multilogin offer more flexible rights management. In Multilogin, you can set up roles so that a team member can see a profile and launch it, but cannot view the proxy credentials (they are hidden). This is an ideal scheme for agencies where each buyer has their own tasks and does not need access to the "kitchen."
In GoLogin, the rights system is less flexible, but there is a basic division: account owner and participants. Participants cannot change proxy settings in profiles managed by the owner.
⚠️ Important: Anti-Detect Browser Is Not a Password Manager!
Do not use an anti-detect browser as the primary storage for credentials. If you lose access to the Dolphin or AdsPower account, you will lose all proxy data. Always duplicate credentials in a secure password manager — Bitwarden, 1Password, or Keeper.
Access Control in the Team: Who Sees Which Proxies
One of the most common mistakes is giving all team members full access to all proxies. This is convenient at the start but creates huge risks. The correct access scheme is built on the principle of "least privilege": everyone sees only what they need for their work.
Here’s how it looks in practice for a typical arbitrage team:
| Role | What They See | What They Can Do |
|---|---|---|
| Team Lead / Owner | All proxies from all projects | Full access: add, delete, view passwords |
| Senior Buyer | Proxies for their direction (FB Ads or TikTok) | View and use, no deletion |
| Buyer | Only their 5-10 proxies | Only use (password hidden) |
| SMM Manager | Proxies for their client accounts | View and use |
| Freelancer / Contractor | Temporary access to 1-2 proxies | Only use, access revoked after task completion |
Rotate credentials when team composition changes. This is a critically important point that most teams ignore. When an employee leaves — you need not only to revoke their access in the password manager but also to change the passwords for the proxies they used. If this is not done, the former employee may continue to use "their" proxies — and you won't know about it.
Separate credentials for each direction. If you have the ability to create sub-users with the proxy provider — use it. For example, for mobile proxies, create a separate login for the Facebook Ads team and a separate one for the TikTok team. This way, if one direction is compromised, the other remains secure.
Dangerous Habits That Leak Your Proxies
Most credential leaks occur not due to hacking attacks but due to ordinary work habits that seem harmless. Let's discuss the most dangerous of them.
❌ Storing in Google Sheets or Excel
A table with proxies is the first thing teams create. Convenient, visual, familiar. But Google Sheets is not a secure storage. Anyone with the link can see all the data. If the link is accidentally published in a chat or forum — credentials leak instantly. Moreover, Google may scan the contents of documents. If you need a table to manage proxies — store only IP, port, geolocation, and status in it. Usernames and passwords — only in a password manager.
❌ Sending credentials in messengers
"Send me the proxy" — a standard request in a work chat. And in response, a line like user:password@host:port flies. This line is now stored in the chat history on Telegram or WhatsApp servers, on the phones of all chat participants, in device backups. The correct approach: share a record from the password manager (Bitwarden allows you to send a secure link with a limited validity period), not the data itself.
❌ Saving passwords in the Chrome browser
The built-in password manager in Chrome is convenient for regular sites but not for work credentials. Stealers (viruses for stealing passwords) primarily target the Chrome password database. If a buyer's computer is infected — the attacker gets all saved passwords in seconds, including credentials for proxies and personal accounts in advertising systems.
❌ One password for all proxies
If you have one master password for the entire pool of proxies and it becomes known — you lose everything. Use unique credentials for each proxy or at least for each group of proxies. Most providers allow creating sub-users with separate usernames and passwords.
❌ Screenshots of settings
When setting up proxies in Dolphin Anty, AdsPower, or another tool, the password field is often visible on the screen. A screenshot for "documentation" or to help a colleague — and the data is already in the phone's gallery, in the iCloud or Google Photos cloud. Always close or mask password fields before taking a screenshot.
Proxy Credentials Security Checklist
Use this checklist to audit your team's security. Go through each item and correct what does not meet the requirements.
📋 Basic Security
- ☐ All proxy credentials are stored in a password manager (Bitwarden, 1Password, or Keeper)
- ☐ No password tables in Google Sheets, Excel, or Notion
- ☐ No credentials in messenger histories (Telegram, WhatsApp, Slack)
- ☐ Passwords are not saved in the Chrome or Firefox browser
- ☐ Each proxy or group of proxies has a unique password
📋 Access Management
- ☐ Each employee sees only their proxies, not the entire pool
- ☐ 2FA is enabled on anti-detect browser accounts (Dolphin, AdsPower, GoLogin)
- ☐ 2FA is enabled on the password manager account
- ☐ When an employee leaves — access is revoked and credentials are changed
- ☐ Freelancers and contractors receive temporary access, which is revoked after the task
📋 Operational Security
- ☐ Credentials are not transmitted through messengers — only through secure links from the password manager
- ☐ In screenshots of settings, password fields are closed or obscured
- ☐ Antivirus is installed on all team members' work devices
- ☐ Passwords are changed at least once every 3 months or upon suspicion of a leak
- ☐ A log is maintained: which proxy is linked to which account and which buyer
📋 Incident Response
- ☐ There is an action plan in case of a credentials leak (who changes passwords, who notifies the provider)
- ☐ The proxy provider is notified of suspicious activity on the IP
- ☐ Accounts that used compromised proxies are checked for bans
- ☐ The source of the leak is identified and eliminated before issuing new credentials
If you marked less than 10 items out of 18 — your team is operating under high risk conditions. Start with the most important: set up Bitwarden (it's free), transfer all credentials there, and delete password tables.
It is also worth mentioning the choice of the proxy provider itself. If you are using data center proxies for tasks where speed is more important than anonymity (for example, price monitoring on marketplaces), make sure the provider supports IP-whitelist authorization — this allows you not to store a username and password at all.
Conclusion
Secure storage of proxy credentials is not paranoia, but basic hygiene for any team working with advertising accounts, social media accounts, or marketplaces. A data leak of proxies leads to IP burnout, account bans, and loss of money — all because of an Excel file or a line in a Telegram chat.
Three main takeaways from this guide: use a password manager (Bitwarden is free and sufficient for most teams), limit access based on the principle of least privilege, and change credentials whenever team composition changes. These three steps cover 90% of the risks.
If you are just building your infrastructure and looking for reliable proxies with flexible access management, consider residential proxies — they support both username/password and IP-whitelist authorization, which significantly simplifies credential management within a team and reduces the risk of leaks.