How AnsBot keeps browser runs contained.
Every AnsBot run opens a fresh headless browser on Anslation's servers that can reach public websites only: a guard refuses private, local and cloud-metadata addresses and checks every redirect. Sign-in details sit encrypted in a vault, values marked secret are masked in step logs, outputs, errors, approvals, exports and callbacks, and a bot is open only to its creator, its team and AnsBot administrators.
The network guard. Public websites only.
- Public addresses onlyEvery request a run's browser makes is fetched through a guard that allows public internet addresses and refuses private, local and cloud-metadata ones.
- Redirects checked hop by hopA redirect to a refused address is stopped, not followed.
- No side channelsWebSockets and WebRTC are cut off when the browser starts.
- A fresh browser for each runRuns start a new headless browser on Anslation's servers; nothing runs in your own browser.
What AnsBot does not do. And what to keep in mind.
It does
- Signs in only with details you stored in the vault or a browser profile you saved.
- Stops for a person at the steps you mark.
It does not
- Solve CAPTCHAs, or get around sign-ins, paywalls or bot checks.
- Reach private, intranet or localhost addresses.
- Encrypt screenshots: they are saved as ordinary image files.
- Encrypt a secret input's default value: it is never shown again, but keep passwords in the vault.
What AnsBot stores, and how.
| Item | How it is kept |
|---|---|
| Vault entries | Encrypted with an application key; shown as a masked preview. |
| Browser sessions | A profile's signed-in session is stored encrypted and used by one run at a time. |
| Callback signing keys | Stored encrypted; used to sign each callback with HMAC-SHA256. |
| Webhook tokens | Shown when created or rotated; stored hashed. |
| Client portal links | Signed, expiring and revocable. |
| Values marked secret | Replaced with [redacted] in logs, outputs, errors, checkpoints and callbacks. |
| Failure traces | Kept outside the public media folder for a limited time; only roles allowed to see traces can download them. |
| Who can open a bot | Its creator, its team and AnsBot administrators. |
Records and limits you can set. Per bot.
- Audit logPublishes, reviews, runs people start, approvals, repairs, token rotations, portal invites and policy changes, for the bots you can open; filter it and export it as CSV.
- Data retentionKeep finished runs for a set number of days; once Anslation switches on the scheduled cleanup, it deletes older ones with their logs, outputs and screenshots, unless a retry or an open repair still needs them.
- Locked published versionsA bot setting, on whenever reviews are required: AnsBot refuses any edit to a published version's steps; you edit a new draft made from it.
- Approval before a run startsAn environment setting that holds each run started with it until a person approves; runs from schedules, webhooks, batches and the client portal do not use environments.
Security questions, answered.
Still have a question? Ask us
Can an AnsBot run reach our internal systems?
No. Every request a run makes goes through a guard that allows public internet addresses only and refuses private, local and cloud-metadata ones, including after a redirect.
Where are passwords for websites kept?
In the bot's vault, encrypted with an application key and shown only as a masked preview. A run fills them through {{credential_username}} and {{credential_secret}}, and every log, output and callback shows [redacted] instead.
Who can see a bot's runs and screenshots?
The bot's creator, the members of its team and AnsBot administrators. Private failure traces also need a team role that is allowed to see traces.
Does AnsBot keep what it types?
Yes, it keeps each run's inputs with the run, so you can see what it typed, except values marked secret: those become [redacted] in step logs, outputs, errors, approvals, exports and callbacks.
Where do I report a security problem I found?
Use the responsible disclosure page, which says what to include and where to send it.
Questions before a security review?
Tell us the web task and the site it runs on. We read every request and reply by email.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838