This End User License Agreement ("EULA") is a legal agreement between you and Keyback Systems Ltd. for the Dual Login desktop software and any updates or documentation (the "Software"). By installing or using the Software you accept this EULA. It is part of our Terms of Service.
In plain English
A policy has to be precise, which makes it hard to read. Here is the same document answered as the questions people usually arrive with. It is a summary: where the two could be read differently, the numbered sections below govern.
What does the licence actually let me do?
Install and run the desktop software on the machines your plan covers, for as long as that plan is active, for your own work or your clients'. That is section 1. It is a licence to use the software, not a transfer of ownership — the same arrangement as every other desktop application you have installed.
What may I not do with it?
Section 2: no reverse engineering, no reselling or sublicensing it as your own product, no stripping the notices, no circumventing the licensing to run it beyond what you have paid for. Building your own product on top of Dual Login's automation API is a different thing and is not what this restricts — see the partner programme if that is the conversation you want to have.
Do I have to take updates?
Section 3 covers them. You should want to: the browser engine is the part of this product that has to keep pace with how sites detect automation, and an old engine is measurably easier to spot than a current one. This is the one piece of maintenance where putting it off has a direct cost in what you are paying for.
The software includes open-source components. What applies to those?
Their own licences, not this one — section 5. The engine is built on Chromium, and the components carrying their own terms keep them; where those terms and this EULA differ for that component, theirs win. Nothing here takes away a right an open-source licence gives you.
What happens to my data if the licence ends?
The licence to run the software ends, under section 6; your profile data is on your disk and stays there. If you have synced profiles to your account, export before you go rather than after — a session that exists only in an account you have closed is a session you have lost, and that is avoidable in about two minutes.
Can I run it on more than one computer?
Within what your plan covers -- a desk machine and a laptop is the ordinary case and is fine. What the licence prevents is turning one subscription into a shared resource for a group who should each hold their own. If your team needs several people working in one workspace, that is what team seats and roles are for, and it is a better fit than sharing a login anyway.
Can I automate the browser with my own scripts?
Yes -- that is what the automation API is for, and building your own tooling on top of it is expected use, not a restriction. What section 2 prohibits is repackaging the software itself as your product. Driving it from your code is the difference between using a tool and reselling it.
What happens to my licence if my subscription lapses?
The licence is tied to the active plan, so it ends with it. The software stops being licensed to run; your data does not go anywhere. If you are winding down rather than pausing, export the profiles you care about before the lapse rather than after -- the sessions you would miss are the ones you never got round to exporting.
Why is there a EULA as well as Terms of Service?
Because they govern different things. The Terms cover the service -- your account, the plan, the hosted parts. The EULA covers the desktop software you install on your own machine, which raises questions the Terms do not: what installing lets you do, what happens to updates, and which components carry someone else's open-source licence rather than ours.
Does the licence cover using this for clients rather than myself?
Yes -- agency work is squarely within it, and it is one of the main ways the product is used. What the licence governs is your relationship with us, not your relationship with your clients; the accounts you manage on their behalf sit under whatever you have agreed with them.
Can I install it on a server rather than a desktop?
Nothing in the licence prevents it, and unattended automation on a VPS is common. The practical constraints are technical rather than legal: memory, since each profile is a real browser process, and graphics, because a host with no GPU produces a software-rendering signature that identifies the session as a virtual machine.
1. Grant of license
Subject to this EULA and your active plan, we grant you a limited, non-exclusive, non-transferable, revocable license to install and use the Software on devices you own or control, for your internal business purposes.
2. Restrictions
You may not:
- •Copy, sell, rent, lease, sublicense or distribute the Software except as expressly allowed.
- •Reverse engineer, decompile or disassemble the Software, except to the extent the law permits despite this restriction.
- •Remove or alter any proprietary notices.
- •Use the Software to build a competing product, or in any way that breaks our Acceptable Use Policy or the law.
3. Updates
We may provide updates, which may be installed automatically to keep the Software secure and working. This EULA covers updates unless an update comes with separate terms.
4. Ownership
The Software is licensed, not sold. Keyback Systems Ltd. and its licensors keep all rights, title and interest in the Software, including all intellectual property rights.
5. Third-party components
The Software may include third-party or open-source components licensed under their own terms, which apply to those components.
6. Termination
This EULA applies until terminated. It ends automatically if you breach it. On termination you must stop using and remove the Software. Sections that by their nature should survive (such as ownership and limitations) will survive.
7. Disclaimers and liability
The Software is provided "as is" without warranty, and our liability is limited as described in our Terms of Service.