Cookie management — one of those multi-accounting areas often underestimated until first serious incident. Lost cookies = lost session = need for re-authorization = risk of additional platform verification. Working with dozens or hundreds of accounts, lack of cookie management system becomes regular losses and unnecessary risks. Let's break down how to organize cookie infrastructure properly.

What are cookies in multi-accounting context

Cookies — small data files that site saves in browser. For anti-fraud systems, cookies serve several functions:

  • Session token: confirms authorization without password re-entry
  • Device identifier: platforms set long-term cookies to track device
  • CSRF-tokens: protection from cross-site requests
  • User settings: language, region, theme

Loss of session cookie during login may require passing two-factor verification, which in multi-accounting is resource-intensive or risky. Loss of long-term identification cookie — increased anti-fraud attention to "new" device.

Cookie isolation: main principle

Each account must have completely isolated cookie storage. This is provided by antidetect browsers: each profile has separate userdata directory — isolated storage not linked to other profiles.

What's isolated in antidetect profile:

  • Cookies (by domains)
  • localStorage and sessionStorage
  • IndexedDB
  • Cache API
  • Service Workers

Breaking isolation — most common reason for account linking. Never copy cookies from one profile to another, except when intentionally transferring account.

Cookie backup

When and why to backup

Cookie backup is needed in several situations:

  • Moving account to another machine or operator
  • Changing antidetect browser
  • Recovery after crash or profile deletion
  • Creating archive of accounts for seasonal work (e.g., accounts used only in Q4)

Export formats

Standard cookie export format — Netscape/Mozilla Cookie File (text format with domain, flag, path, secure, expiration, name, value fields) or JSON. Most antidetect browsers support JSON export.

In JSON structure looks like array of objects with fields:

  • name, value — cookie name and value
  • domain — domain
  • path — path
  • expires/expirationDate — expiration time (Unix timestamp)
  • secure, httpOnly, sameSite — security flags

Cookie export and import: practice

Dolphin Anty

  • Export: in profile click "Export cookies" → JSON file is saved
  • Import: when creating or editing profile → "Import cookies" → select file
  • To transfer account between operators use "Transfer profile" — transfers not just cookies but all userdata

AdsPower

  • Export via Cookie Editor extension (can be installed in profile)
  • AdsPower supports full profile export (including cookies) via "Export Profile"
  • Profile import includes all browser data

GoLogin

  • Cookies stored in cloud as part of profile
  • Cookie export — via Cookie Editor extension or via API
  • GoLogin API allows programmatically read and write profile cookies

Storage organization: file naming system

Working with 50+ accounts, unsystematic cookie file storage ("cookies_1.json", "cookies_facebook.json") leads to confusion. Recommended naming system:

  • Format: [Platform]_[Region]_[Account_ID]_[Export_Date]
  • Example: Facebook_US_acc047_2026-01-15.json
  • Storage: folder with encryption (BitLocker, VeraCrypt) — cookie files give full account access

Cookies and account warmup

Account warmup — accumulation of legitimate cookies from platform. Fresh account has minimal cookie set; warmed has rich set of cookies showing months of use.

When buying warmed accounts on markets you get them as cookies or profile export. Importing such cookies to new antidetect profile transfers "history" of account — but only cookie part; fingerprint must be configured separately for same device type.

Cookie lifespan: what to control

Cookie typeLifespanConsequences of expiration Session tokenUntil browser close / 1–30 daysRe-authorization Remember me token30–365 daysRe-authorization with 2FA Device fingerprint cookie1–2 yearsAccount loses "device history" Analytics cookies30 days – 2 yearsNo direct access consequences

Monitor long-term cookie expiration: if working with account every few months, some cookies may expire and login will require verification.

Cookie management automation

Working with hundreds of accounts, manual cookie management is unrealistic. Automation via antidetect browser APIs:

  • Script periodically exports cookies from active profiles to encrypted storage
  • When creating new profile for account "move" — automatic import from storage
  • Monitoring key cookie expiration with alerts

Example on Python with GoLogin API: request profile list → for each profile request CDP URL → Playwright connects to profile → call page.context.cookies() → save to file with timestamp.

Cookie file security

Cookie file = account access without password. Critical rules:

  • Never store cookies in regular desktop folders
  • Using encrypted storage mandatory
  • Don't send cookie files via messengers or email without encryption
  • On compromise suspicion — immediate password change, session revocation

Systemic approach to cookie management in multi-accounting — not perfectionism but basic hygiene. Combined with isolated profiles of antidetect browser and mobile proxies from turbon.rent, proper cookie management ensures long-term stability of account farm.