Profile workspace
Browser state stays attached to the Profile that created it, creating an understandable storage boundary.
Privacy architecture
Clear boundaries are the security model
Agilelogin makes separation visible and manageable instead of hiding it behind a vague privacy claim.
Product documentation · Last reviewed August 4, 2026
Reviewed against the current public product scope by the Agilelogin product team.
1
Profile-bound state
Cookies, storage, and browser settings stay associated with the Profile that created them.
2
Profile-bound network
Proxy configuration is managed alongside the Profile, so its route is easy to inspect.
3
Explicit automation
Automation connects through a local interface you choose to use, rather than an invisible remote workflow.
4
Honest product status
Engine availability and release state are labeled directly; planned features are not presented as shipped.
What is the Agilelogin security model?
Agilelogin uses visible boundaries around browser Profile state, network configuration, and local automation controls. The model helps an operator identify which environment owns a session and how it connects. It is not a claim of absolute security, anonymity, or protection from the rules and data practices of third-party services.
Data flow
Know where each part of the workspace belongs
Network route
The assigned proxy is managed with the Profile so the intended route remains visible before launch.
Local control
Manual launches and approved automation meet at a local control surface chosen by the operator.
What data belongs to each boundary?
This inventory describes the current public product scope. It separates desktop Profile data from website data and identifies the controls that remain with the operator.
| Data or control | Current boundary | Operator responsibility |
|---|---|---|
| Profile cookies, storage, history, and browser settings | Associated with the desktop Profile that created them | Control device access, backups, retention, and who may launch the Profile. |
| Proxy configuration and credentials | Managed alongside the Profile in the desktop workspace | Choose a trusted provider, protect credentials, and verify the intended route. |
| Automation configuration | Explicit local CDP and REST interfaces used by an approved tool | Restrict local access, review tool permissions, and confirm version support. |
| Public website requests and preferences | Static website; locale choices stay in browser storage, while Cloudflare may process technical request data | Review the Privacy Policy and avoid sending secrets through support messages. |
What we will say clearly
Clear boundaries are the security model
- 01
The public website does not receive Profile cookies, browsing storage, proxy credentials, or automation configuration merely because the desktop app is used.
- 02
Third-party websites, proxy providers, and automation tools keep their own terms and data practices.
- 03
No internet-connected product can promise absolute security; product status and known boundaries should remain visible.
Security is a shared responsibility
Agilelogin can make product boundaries visible, but device security, account authority, proxies, automation tools, and third-party services remain separate trust decisions.
- Agilelogin product
- Represent release status honestly and keep Profile, network, and local-control boundaries understandable.
- Workspace operator
- Secure the device, authorize users and workflows, protect credentials, review configuration, and maintain recovery procedures.
- Proxy and tool providers
- Operate under their own security, retention, availability, and privacy practices.
- Websites and account platforms
- Apply their own authentication, access, policy, logging, and data-processing rules.
Known limits and claims we do not make
Clear limitations are part of the security architecture. They prevent a product boundary from being mistaken for a guarantee about the wider internet.
- No internet-connected software can promise absolute security, privacy, anonymity, or uninterrupted availability.
- Profile separation does not replace operating-system security, encryption policy, strong authentication, backups, or physical device controls.
- A proxy changes a network route but does not make the proxy provider or destination website part of Agilelogin's trust boundary.
- A local automation interface does not make every connected script, AI agent, dependency, or instruction safe or authorized.
Security questions
Does the website receive desktop Profile data?
No. The current website is static and has no Profile-data API or website account database.
Does Agilelogin guarantee absolute security?
No product can make that guarantee. Agilelogin focuses on explicit boundaries, inspectable configuration, and honest release status.
How can I report a security concern?
Send a clear description and reproduction details to support@agilelogin.com. Do not include credentials or sensitive third-party data.
Does Agilelogin operate a cloud database of website user accounts?
Not at this time. The current public website is static and has no sign-up, payment form, first-party analytics, or website account database. Cloudflare may process technical request data to deliver and protect the site, as described in the Privacy Policy.
Does a local API mean any program on the device should be trusted?
No. Local access is a boundary, not an automatic trust decision. Operators should restrict device and network access, use approved tools, protect secrets, and verify the exact API behavior of the installed release.