Browser automation should be planned around an authorized task, clear limits, and safe handling of any account data involved. Cykani provides a desktop workspace for building and running workflows; the person configuring a workflow remains responsible for where it runs and what it accesses.
Start with authorization
Before running a workflow, confirm that you have permission to access the account, site, and data involved. Follow the service's terms and applicable rate limits. Do not use automation to bypass access controls, authentication, CAPTCHAs, or other restrictions.
Protect browser profiles
Profiles can retain cookies and signed-in browser state. Use separate profiles for unrelated tasks, limit access to the device, and remove data when it is no longer needed. Treat screenshots, logs, and exports as potentially sensitive if they contain account or personal information.
Use proxies responsibly
Only configure proxy services that you are authorized to use. Keep proxy credentials private, and avoid sharing them in screenshots or support requests. A proxy does not grant permission to access a site or remove the need to follow its policies.
Review workflow outcomes
Use the desktop app's available monitoring and audit tools to review workflow activity. These tools can help with operational visibility, but they do not guarantee that every external service event or policy issue will be detected.
For product guidance, see Workflows and browser resources and Responsible use.