How do I match DiCloak's timezone settings with BytesFlows proxy geo-location?

DiCloak offers granular fingerprint customization and sub-account management — BytesFlows residential proxies provide the matching clean IP layer needed to prevent cross-profile detection. BytesFlows offers both HTTP (port 8001) and SOCKS5 (port 1080) proxy types with the same credentials — choose based on what DiCloak supports in its proxy configuration.

How many DiCloak profiles can I run simultaneously with BytesFlows?

BytesFlows does not limit concurrent connections by profile count. Your usage is tracked by bandwidth consumed. Create as many sub-users as profiles and run them simultaneously — each will route through a different residential IP.

Do I need a different BytesFlows sub-user for each DiCloak profile?

Yes, for complete IP isolation. Each sub-user gets its own proxy credential that can be assigned to a different geo target. This ensures no two profiles share an exit IP or ASN — the key requirement for multi-account isolation on major platforms.

DiCloak Integration

DiCloak + BytesFlows: isolated residential IP per browser profile

DiCloak offers granular fingerprint customization and sub-account management — BytesFlows residential proxies provide the matching clean IP layer needed to prevent cross-profile detection.

DiCloak

+ BytesFlows

DiCloak profiles: why residential proxy isolation is critical

Platforms detect multi-account operations through IP patterns — not just browser fingerprints.

Feature

✕Without Proxy / Datacenter IP

✓With BytesFlows Residential

IP type

Datacenter / VPN server

✓Real home broadband IP

IP isolation per profile

Shared exit IP

✓Unique IP per sub-user

Geo accuracy

City often wrong

✓City-level residential targeting

Platform detection risk

High — datacenter ASN flagged

✓Low — genuine ISP traffic

Configure BytesFlows in DiCloak

Step-by-step guide for granular profile proxy assignment.

1
Create a BytesFlows sub-user
BytesFlows dashboard → Proxies → Residential → Sub-users → Add User. Create one sub-user per DiCloak profile for complete isolation.
2
Open DiCloak profile settings
In DiCloak, create a new profile or edit an existing one. Navigate to the Proxy or Network settings section.
3
Enter proxy credentials
Set proxy type to HTTP or SOCKS5. Host: p1.bytesflows.com, Port: 8001 (HTTP) or 1080 (SOCKS5). Username: your BytesFlows sub-user (optionally add -cc-XX for country targeting). Password: sub-user password.
4
Test the proxy connection
Use DiCloak's built-in proxy check or our proxy test tool to verify the exit IP shows a residential ISP (not a datacenter).
5
Launch and verify
Start the profile and browse to our proxy test tool to confirm your residential IP is active. Verify the ISP and geolocation match your target.

DiCloak proxy FAQ

Add residential IPs to your DiCloak setup

1 GB free residential traffic — test with your DiCloak profiles before committing to a paid plan.

Residential proxies

Locations

DiCloak + BytesFlows: isolated residential IP per browser profile

DiCloak profiles: why residential proxy isolation is critical

Configure BytesFlows in DiCloak

Create a BytesFlows sub-user

Open DiCloak profile settings

Enter proxy credentials

Test the proxy connection

Launch and verify

DiCloak proxy FAQ

Add residential IPs to your DiCloak setup

Related guides