AquaFutures IP and Device Policy: Single Login Rules and VPN Restrictions

Written by Paul

Published on

January 16, 2026

AquaFutures enforces single-user access policies: each account must be accessed from consistent devices and IP addresses registered to the account holder, with multiple logins from different locations flagging potential account sharing violations. VPN usage is typically restricted or prohibited during evaluations and funded trading because VPNs mask true location and enable account sharing, though some firms allow VPNs if disclosed upfront with static IP addresses. Traveling traders must notify support before accessing accounts from new locations (hotels, airports, different countries) to avoid automatic security locks.

The policy exists to prevent: account sharing where hired traders use your credentials, coordinated trading groups accessing multiple accounts from single locations, and fraud where stolen accounts are accessed from foreign IPs. Violations result in immediate account suspension pending investigation—if you can't prove legitimate access (travel itinerary, work relocation), the account terminates permanently. Most traders never encounter issues by simply trading from home/office consistently and notifying support for travel.

I'm breaking down single login rules, VPN restrictions by use case, how to notify support for travel, IP tracking methods, what triggers security flags, how to prove legitimate multi-location access, handling work/home trading setups, and mobile device considerations.

Quick heads-up: This article is based on my real experience with Aquafutures and the info available when I published/updated this. Things change in prop trading — rules, payouts, promos, all of it.

For the absolute latest, check Aquafutures´s website or their faq page.

Single Login Policy Explained

Core rule: One account = One person = Consistent devices and locations

What AquaFutures tracks:

✅ IP addresses: Where you log in from

✅ Device fingerprints: Computer ID, browser type, operating system

✅ Login timestamps: When you access account

✅ Geographic location: City, state, country derived from IP

Normal pattern (no flags):

Login from Home IP (New York) 90% of time
Login from Office IP (New York) 10% of time
Same laptop, same browser
Consistent timezone (EST)

Suspicious pattern (flagged):

Login from New York at 9am
Login from London at 9:30am (impossible—6 hours apart geographically)
Login from Singapore at 10am (10+ hours apart)
Result: Account locked, investigation triggered

For account sharing rules, see the account sharing guide.

VPN Usage: Restricted or Prohibited

Why VPNs are restricted:

❌ Masks true location: Can't verify who's actually trading

❌ Enables account sharing: Hired trader in India appears to be you in New York

❌ Facilitates fraud: Stolen account accessed from anywhere

❌ Violates coordinated trading detection: Multiple traders in same room appear as one person

Typical AquaFutures policy:

During evaluations:

❌ VPNs prohibited (instant termination if detected)

During funded trading:

⚠️ VPNs restricted (allowed only with prior approval + static IP disclosure)

Exceptions (if disclosed upfront):

✅ Work requires VPN (corporate security policy)

✅ Geographic restrictions (your country blocks broker access)

✅ Privacy concerns (with static VPN IP that's disclosed)

If you need VPN, email support BEFORE using:

"Hello,

I need to use a VPN for [specific reason: work requirement / geographic access / privacy]. My VPN provider is [X] with static IP address [Y]. I will only access my account through this VPN.

Can you whitelist this IP to avoid account flags?

Thank you,[Your Name]"

If approved: VPN allowed, must use disclosed IP only

If denied: No VPN allowed, find alternative

Legitimate Multi-Location Scenarios

Scenario 1: Travel for business/vacation

Problem: You normally trade from New York, traveling to California for 2 weeks.

Solution: Email support BEFORE traveling

"Hello,

I'll be traveling to Los Angeles from [date] to [date] for vacation. I'll access my account from hotel WiFi and possibly mobile hotspot.

Expected IPs:

Hotel: [Unknown, but Los Angeles area]
Mobile: Verizon network, LA

Please note this temporary location change to avoid account locks.

Thank you,[Your Name]"

Result: Support notes your account, won't flag LA logins during those dates.

Scenario 2: Work from home + office

Problem: You trade from home (Comcast IP) 3 days/week, office (Corporate VPN) 2 days/week.

Solution: Disclose both IPs upfront

"Hello,

I trade from two locations:

Home: Comcast IP (New York)
Office: Corporate VPN IP (New York)

Both are legitimate locations. Can you whitelist both to avoid flags?

Thank you,[Your Name]"

Result: Both IPs whitelisted, no issues.

Scenario 3: Relocation (moving to new city)

Problem: You move from New York to Texas permanently.

Solution: Notify support, update account info

"Hello,

I'm relocating from New York to Austin, Texas on [date]. My new home IP will be Spectrum network (Austin area).

Please update my account location to reflect this permanent move.

Thank you,[Your Name]"

Result: Account updated, Texas IP expected going forward.

For customer support details, see the customer support guide.

What Triggers Security Flags

Flag 1: Impossible travel

Example:

9:00am: Login from New York
9:15am: Login from Los Angeles (3,000 miles, 6-hour flight)

System: This is impossible—either VPN or account sharing.

Result: Account locked immediately.

Flag 2: Foreign IP logins

Example:

Account registered: United States
Login attempt: Nigeria, India, Romania

System: High-risk countries for fraud, likely stolen account.

Result: Account locked, verification required.

Flag 3: Multiple devices simultaneously

Example:

10:00am: Logged in on laptop (New York)
10:05am: Logged in on phone (New York)
Both active at same time

System: Normal—you're using phone and laptop together.

No flag.

But:

10:00am: Logged in on Device A (New York)
10:00am: Logged in on Device B (Texas)
Both active at same time

System: Impossible—account sharing.

Flag triggered.

Flag 4: New device from new location

Example:

You've only logged in from New York on Laptop A for 3 months
Sudden login from California on Laptop B

System: Unusual—could be stolen account or unauthorized access.

Result: Account locked, verification email sent.

Flag 5: TOR/Anonymous proxy detected

TOR, anonymous proxies, or data center IPs (not residential):

Result: Instant account lock (extremely high fraud risk).

How to Prove Legitimate Access

If your account gets locked due to location change:

Step 1: Respond to verification email

AquaFutures sends: "We detected unusual login activity. Please verify."

Step 2: Provide evidence

Email with:

✅ Travel itinerary: Flight confirmation, hotel reservation

✅ Work documentation: Letter from employer confirming travel/relocation

✅ Government ID matching new location: Driver's license, utility bill

✅ Explanation: "I'm traveling for business and notified support on [date]."

Step 3: Selfie verification

Take selfie holding government ID next to your face.

Step 4: Video call (if required)

Some firms require video call to confirm identity.

If proof is legitimate: Account unlocked within 24-48 hours.

If proof is insufficient or contradictory: Account remains locked, terminated if fraudulent.

Mobile Device Trading

Question: Can you trade from phone while also logged in on laptop?

Answer: Yes—multiple devices from same location is allowed.

Example:

Home WiFi: Laptop trading ES
Same Home WiFi: Phone checking positions
Both connected to same IP

Result: No flag ✅

But:

Home WiFi (New York): Laptop trading
Mobile hotspot (California): Phone checking positions
Two different IPs, same time

Result: Flag if not disclosed ⚠️

Best practice: If trading from phone while traveling, notify support first.

Work VPN vs Personal VPN

Corporate VPN (work requirement):

Scenario: Your employer requires VPN for security, you trade during lunch break.

Solution: Disclose to AquaFutures

"Hello,

My employer requires VPN for all internet access. I trade during lunch break from office using corporate VPN.

VPN provider: [Company's IT dept]Static IP: [X.X.X.X]Location: New York

Please whitelist this IP.

Thank you,[Your Name]"

Likely outcome: Approved (legitimate business reason).

Personal VPN (privacy/access):

Scenario: You use NordVPN for privacy or to access restricted content.

Solution: Disclose and explain necessity

"Hello,

I use NordVPN for privacy. I'll be using static IP [X] from [VPN provider].

Can you whitelist this IP?

Thank you,[Your Name]"

Likely outcome: Denied (no compelling reason, security risk).

If denied: Don't use VPN. Trade without it or find another prop firm that allows VPNs.

Account Sharing Detection Methods

Method 1: IP/Device correlation

Pattern 1 (legitimate):

Account A: New York IP, Device X, 9am-12pm trading
Account B: New York IP (different), Device Y, 9am-12pm trading
Two separate people, no sharing

Pattern 2 (account sharing):

Account A: New York IP, Device X, 9am-10am
Account B: Same New York IP, Same Device X, 10am-11am
Two accounts, one person/device = sharing

Method 2: Trading style analysis

Pattern (account sharing):

Account A: Day 1-30, Strategy X (50 EMA bounces), New York IP
Account A: Day 31+, Strategy Y (order flow), London IP
Style and location changed = different person trading now

Method 3: IP geolocation + timestamp

Pattern (account sharing):

Account registered: United States
Consistent logins: Philippines IP
Registered in US but traded from Philippines = hired trader

For coordinated trading detection, see the coordinated trading guide.

Penalties for IP/VPN Violations

Violation 1: Unauthorized VPN use

Detection: VPN IP detected (NordVPN, ExpressVPN data center range)

Result: Account locked, email sent

If first offense + innocent explanation: Warning, unlocked

If repeated: Account terminated

Violation 2: Account sharing

Detection: Two accounts accessed from same device, or impossible travel

Result: Both accounts terminated immediately, permanent ban, profits voided

Violation 3: Fraud (stolen account)

Detection: Login from foreign IP, unusual trading, withdrawal attempt

Result: Account terminated, law enforcement notified (if significant money involved)

For prohibited activities, see the prohibited strategies guide.

How to Trade Safely Across Multiple Locations

Strategy 1: Notify support for every major change

Traveling? Email support with dates and destination
Moving? Update account info with new address
New office? Disclose new IP

Strategy 2: Use consistent devices

Trade from same laptop always
If switching to backup laptop, email support first

Strategy 3: Avoid public WiFi during trading

Why:

Shared IPs (100+ people on same network)
Security risk (hackers on public WiFi)
Unpredictable geolocation (hotel, airport IPs flagged)

Better: Use mobile hotspot (your phone's data plan).

Strategy 4: Document your locations

Keep records of:

Where you trade from regularly (home, office)
Travel dates and destinations
IP addresses (check "what is my IP" on Google)

If ever questioned, you have proof.

Strategy 5: Don't share login credentials

Never:

Give login details to friend/mentor
Let someone "test your account"
Share credentials with paid trading service

All of these = account sharing = termination.

Mobile Hotspot Considerations

Question: Can you trade using phone hotspot while traveling?

Answer: Yes, but notify support first.

Why it's okay:

Mobile IPs are dynamic (change location as you move)
Still tied to your carrier (Verizon, AT&T, T-Mobile)
Can be verified through carrier if needed

Best practice:

"Hello,

I'll be traveling and may trade using Verizon mobile hotspot. IP will vary based on location (traveling through 3 states).

Expected timeframe: [dates]

Please note this temporary access method.

Thank you,[Your Name]"

Final Thoughts: Trade From Consistent Locations

95% of traders never have IP/device issues because:

✅ They trade from home consistently

✅ They notify support for travel

✅ They don't use VPNs without disclosure

✅ They don't share accounts

The 5% who get flagged:

Use VPNs without disclosure (instant lock)
Share accounts with hired traders (termination)
Access from suspicious foreign IPs (lock + investigation)
Forget to notify support before travel (temporary lock, easily resolved)

Simple rules:

Trade from consistent locations (home, office)
Notify support before travel
Don't use VPNs without approval
Never share login credentials
Use same device when possible

Follow these, and you'll never have IP/device issues.

Frequently Asked Questions

Can you use a VPN with AquaFutures?

Usually restricted or prohibited. Evaluations: VPNs typically banned (instant termination if detected). Funded: Restricted but may be allowed with prior approval + static IP disclosure. Exceptions: Work VPN requirement, geographic access issues, privacy with disclosed static IP. Must email support BEFORE using VPN to request whitelisting. Unauthorized VPN use triggers account lock.

What happens if you log in from different locations?

Legitimate travel: Notify support before accessing from new location (hotel, airport, different city/country) with dates and destination—account won't be flagged. Suspicious pattern: Impossible travel (New York 9am, London 9:30am), foreign IPs without notice, multiple locations simultaneously—triggers account lock pending verification. Proof required: Travel itinerary, hotel reservation, work documentation.

Can you trade from both home and office?

Yes, if disclosed. Email support: "I trade from two locations: Home (Comcast IP, New York) and Office (Corporate VPN, New York). Please whitelist both." Support notes account, no flags. Don't disclose = possible flag when switching locations frequently. Same city different IPs usually fine, but disclosure prevents issues.

How do prop firms detect account sharing?

Three methods: (1) IP/Device correlation—two accounts accessed from same device or one account from impossible simultaneous locations, (2) Trading style analysis—strategy changes coinciding with location changes (different person trading), (3) Geolocation + timestamp—account registered US but consistently traded from Philippines (hired trader). Detection certain if account sharing occurring.

Can you trade on your phone while traveling?

Yes, but notify support first. Mobile hotspot IPs are dynamic (change as you move) but tied to your carrier (Verizon, AT&T). Email support: "I'll be traveling [dates], may trade using [carrier] mobile hotspot, IP will vary by location." Multiple devices from same location is allowed—laptop + phone from home WiFi is fine.

What triggers an account security lock?

Five triggers: (1) Impossible travel (different countries within minutes), (2) Foreign IP logins (account registered US, login from Nigeria/Romania), (3) Multiple devices simultaneously from different locations, (4) New device from new location suddenly, (5) TOR/anonymous proxy detected. Lock requires verification—provide travel itinerary, ID, selfie, explanation. Legitimate proof = unlocked 24-48 hours.

Do you need to notify support every time you travel?

Yes, for major travel. Notify for: Different cities/states, international travel, extended stays (weeks), first time accessing from new location. Don't need to notify for: Same city different WiFi (home to friend's house), mobile hotspot in same metro area, brief location changes (across town). Better to over-communicate than risk account lock.

Can you trade from public WiFi?

Technically yes, but not recommended. Risks: Shared IPs (100+ people on same network—appears suspicious), security vulnerabilities (hackers on public WiFi), unpredictable geolocation (hotel/airport IPs flagged as high-risk). Better: Use mobile hotspot (your phone's data) for security and clearer identity verification. If must use public WiFi, notify support with location/dates.