Test accounts and login safety

Giving a tool a password deserves care. Here is how ViralDub handles the logins you give it.

Read by code, not by AI

Logins in your request are read by code. For unusual layouts that the code cannot place, a model sees only masked tokens and pairs them with roles; it never sees the values.

Never seen by the agent that drives the browser

The agent that films your app starts on a page that is already signed in. It never types or sees your password. If a login screen appears during filming, it stops and says so.

Kept out of the video and the logs

• The sign-in is done off camera and never appears in the video.
• Passwords are never spoken in the narration or shown on screen.
• Login values are removed from job logs and traces.
• Logins are used only for the job they were given for.

Your browser's saved passwords

The login boxes tell password managers to stay out, so your saved ViralDub sign-in is never filled in by mistake. If your own ViralDub email ends up in a row, the Studio points it out.

Use a test account

Even with all this, give the agent a dedicated test or demo account, never a real user's account or an admin account with access to customer data. The agent clicks through your app the way a user would, and the video shows whatever that account can see.