Every term in this space, in plain English
Antidetect browsing, fingerprinting, proxies and agent automation come with a lot of vocabulary. Here is what each term actually means.
Frequently asked questions
What is an antidetect browser?+
An antidetect browser runs many separate browser identities from one machine. Each profile keeps its own cookies, storage and a distinct, consistent fingerprint, so sites see each one as its own ordinary browser and the sessions you run for different accounts or regions stay cleanly separated.
Is using an antidetect browser legal?+
Yes, for legitimate use. Running isolated profiles to manage accounts your business owns, test your sites across configurations, verify ads by region, or collect public web data is normal and lawful. You are still responsible for following the terms of every platform you operate on.
How is Oculr different from other antidetect browsers?+
Most tools patch fingerprint surfaces with JavaScript injected into the page, which leaves wrappers a site can read. Oculr builds fingerprint control into its own Chromium engine at the source level, so detection-relevant getters return the same native code signatures stock Chrome returns, and every surface derives from one profile definition.
What do I need to know before reading these definitions?+
Nothing technical. The glossary explains fingerprinting, proxies and agent automation in plain English, defining each term once and linking related ones together, so you can start anywhere and follow the threads that matter to your work.
Give your agents a browser that sites trust
Spin up your first two profiles free. Point an agent at them, run a task, and watch Oculr turn it into a workflow you can scale.
No credit card required · Cancel anytime
