Saved Logins

A saved login stores your browser session state (cookies, local storage, IndexedDB) so the agent can access pages that require authentication without you entering credentials each time.

How it works

1. Log into the target website in your own browser
2. Export your session using a browser extension (cookies + storage state)
3. Import the exported data into Ev3ry under the website's settings
4. The agent loads your session when it opens the browser — it arrives on the site already authenticated

What gets saved

Your actual credentials (username and password) are never stored. Only the resulting session state is saved.

Session expiry

Login sessions expire. When that happens, the agent lands on a login page instead of the expected content, and the run fails with an authentication error.

Check the session lifetime of your target site. Some sites expire sessions after hours; others last weeks or months. When a run fails with a login error, re-export your session from a fresh browser login and import it again.

Browser compatibility notes

Session data exported from Chrome may have minor compatibility differences when injected into the Camoufox (Firefox) browser:

• SameSite=None cookies require the Secure flag on Firefox. Ev3ry applies this fix automatically.
• Cookie expiry > 400 days — Firefox 142+ caps cookie lifetime at 400 days per spec. Ev3ry clamps long-lived cookies automatically.

If you use a cloud browser (Chromium-based), no compatibility adjustments are needed.

Security

• Session data is stored encrypted at rest
• Sessions are scoped to your workspace — team members with access to the website can use the saved login
• You can delete a saved login at any time from the website's settings page
• For sensitive accounts, consider using a dedicated browser profile just for session exports