Incogniton Proxy Integration

Incogniton is a multi-profile browser that isolates cookies and storage between profiles. Teams can use that separation for authorized clients, QA environments, and account security. Do not use fingerprint controls to impersonate people, create fake accounts, or bypass platform enforcement.

Open a profile's proxy settings, select HTTP or SOCKS5, enter gw.databay.co as the host and 8888 as the port, then add the username and password from the Databay dashboard. Save the profile and run Incogniton's proxy check. Keep credentials in a password manager and never embed production secrets in screenshots or shared templates.

Add a documented country flag such as -countryCode-us when an authorized test needs a US network origin. Add -sessionId-profile01 only when the workflow needs short-term IP continuity. Sticky sessions can last up to 120 minutes, subject to live availability; they are not dedicated devices and do not guarantee the same IP after an idle period.

Inside the profile, open a trusted IP-check endpoint and confirm the observed exit, country, and protocol match the approved test plan. If the direct browser address appears, stop before signing in and correct the connection settings. Use accurate timezone and language settings for reproducible QA, not to fabricate a person's identity.

Residential and datacenter pools provide different network origins, availability, latency, and price. Choose from the authorized test requirement and measure the result. Do not switch pools or session IDs to route around a 403, 429, CAPTCHA, or other source control; stop, back off, or use an approved API or access method.

Maintain written account authorization, role-based access, multifactor authentication, profile ownership, access logs, and offboarding. Give profiles separate storage for security, not as invented identities. Apply source terms and one domain-level request budget across all profiles. Databay's Acceptable Use Policy prohibits spam, deceptive engagement, and unauthorized access.