Auto Capture is in a closed beta and isn’t available to every workspace yet. We’d love your feedback: email support@tella.com. Save a demo or test account rather than your own. The AI sees everything the account can see once it’s signed in, and anything on screen can end up in the recording.
Does the AI see my password?
No. The AI that operates the browser never receives your password, and neither do the AI providers behind it. The password is typed into the page for it, and only on the sites listed under Use on and Sign-in page for that login.
The AI does see the email address, and every page it visits, including everything your product shows after it signs in.
How does Tella store my password?
Passwords are encrypted with AES-256-GCM before they’re written to storage, and Tella keeps only the encrypted copy. The key is reserved for Auto Capture, held in hardware security modules validated to FIPS 140-3, can’t be exported from them, and is rotated regularly.
The part of Tella that saves your credentials can encrypt them but can’t decrypt them. Only the service that runs captures can, and only for a running capture that’s allowed to use that login.
Can Tella staff see my password?
No. Once saved, a password can’t be viewed again, by you or by anyone at Tella. No Tella employee is granted permission to decrypt credentials, and every decryption is recorded in an audit log. Tella’s logs record which login a capture used and when, never the login itself.
Which AI providers see my pages?
Auto Capture uses Anthropic’s Claude by default, or an OpenAI model if one is chosen for the capture. The provider receives screenshots and page text so the AI can decide what to do next. It never receives your password.
Where do captures run?
On Tella’s own infrastructure in Amazon Web Services, in the US East (Ohio) region. Tella doesn’t use a third-party browser service.
Each capture runs in its own browser with its own profile, and both are deleted when the capture ends. Any signed-in session a capture keeps between steps is encrypted and deleted with it.
Will my password or email appear in the recording?
Password fields are masked in recordings. Usually the recording starts already signed in, with no login screen in it. If a recording does show the sign-in, or your product shows the email address on screen, the email address appears in the video; trim that part in the editor.
What does Tella store when I connect 1Password?
Only which vault and item to use, never what’s in the item. Tella reads the item from 1Password each time a capture signs in, so a changed password works on the next capture. Your service account token is encrypted the same way as a password, and the service account only sees the vaults you give it.
If the item has a one-time password, Tella generates each code on its own servers. The secret never reaches the browser.
How are sign-in codes handled?
When a capture needs a code sent by email or text message, it asks the person who started it, through a link to a page on Tella. Only that person can see or answer the request, and workspace logins can’t ask for codes at all.
A code is encrypted as soon as you submit it, used once, and deleted as soon as the capture uses it. Each request expires within 15 minutes. The code is typed into your product’s sign-in page, where the AI can see it.
Tella never asks for sign-in codes by email. If you get an email asking for one, don’t enter it.
Who can use a login I save?
A login saved as Only you is used only by captures you start. A login saved as Everyone in the workspace can be used by captures any member starts, and only workspace owners can add, change or remove one. See Personal and workspace logins.
What happens when I remove a login or leave the workspace?
A removed login is deleted straight away and no new capture can use it; a capture already running can finish with it. Disconnecting a 1Password connection deletes every login added from it.
When you leave a workspace or delete your Tella account, your personal logins and 1Password connections are deleted. Workspace logins stay with the workspace, and are deleted if the workspace is. Encrypted database backups keep encrypted copies for up to 35 days.Last modified on October 15, 2026
