What is Account Association?
Account association is the process by which a platform or risk system infers that two or more accounts are controlled by the same person, device, network or organization.
English name, abbreviation and common aliases
- English name: Account Association
- Common aliases: Account linkage, Cross-account correlation
How does Account Association work?
Risk systems combine signals such as IP history, device identifiers, app data, login timing, payment details and behavior. No single signal always proves a link; correlation usually comes from several consistent observations.
A concrete example
Two accounts repeatedly sign in from the same IP, use matching device settings and publish identical content minutes apart. A platform may raise their association score even if their usernames differ.
Account Association vs. related concepts
Account association is an inferred relationship, not an identifier. Android ID , GAID and IP reputation are individual signals that may contribute to the inference.
Use cases, benefits and risks
Typical uses include assigning account ownership, separating workspaces, controlling team permissions and auditing repeated operations. The benefit is clearer organization and less accidental state sharing. Risks remain if operators reuse credentials, content, payment details or behavior in ways that violate a platform’s rules.
How does DuoPlus Cloud Phone reduce account association risks?
DuoPlus Cloud Phone helps reduce accidental environment sharing across multi-account workflows at the device, network and team-management levels:
- Isolated device environments: Each DuoPlus Cloud Phone has its own Android runtime, app data, storage and device parameters, preventing accounts from unintentionally sharing local caches, login sessions or device identifiers.
- Independent network configuration: Proxy management can assign a separate, stable proxy IP to each cloud phone. The IP region should remain reasonably consistent with GPS, SIM card, language and time zone settings.
- Consistent account-to-device assignment: In multi-account management , keep each account assigned to one cloud phone over time. Avoid frequent sign-ins across devices, repeated device resets or sudden changes between regions.
- Controlled team access: Team collaboration provides device groups and member permissions for assigning cloud phones to specific operators, reducing accidental cross-account sign-ins, mixed environments and unnecessary credential sharing.
These capabilities can reduce association signals caused by reused device or network environments. They cannot eliminate signals derived from identity data, payment details, similar content or operating behavior, and they do not replace compliance with each platform's multi-account policies.
Frequently asked questions
Can DuoPlus completely prevent account association?
No. DuoPlus can reduce some device- and network-level association signals through isolated environments and separate configurations, but platforms may still infer relationships from identity data, payment methods, content and behavior.
How should I configure DuoPlus for multiple accounts?
Assign each account a dedicated cloud phone and proxy IP, and keep the proxy region consistent with the device's GPS, SIM card, language and time zone. Once the account is in use, keep its environment stable and avoid unnecessary device resets or cross-device sign-ins.
Can multiple accounts share the same proxy IP?
They can technically share an IP, but a common IP may be one of the signals a platform uses to infer a relationship. For business accounts that need separation, avoid unnecessary proxy reuse and choose stable, region-appropriate proxies from a reliable provider.
How can teams avoid using the wrong account environment?
Administrators can use DuoPlus device groups and member permissions to assign specific cloud phones to specific operators. Team members should access the assigned cloud phone with its existing login session instead of sharing passwords or repeatedly signing in from new local devices.
