Frequently Asked Questions

StayLogged is a browser extension that securely syncs your login sessions across multiple browsers. When you log into a website in one browser, StayLogged securely syncs that session to your other browsers so you stay logged in everywhere without re-entering credentials.

StayLogged encrypts cookie-based session data on your device before upload. When sync is enabled for a domain, the encrypted state can be delivered to your other signed-in browsers so the same account session is available there.

StayLogged is designed so cookie payloads are encrypted before upload, account authentication uses protected flows, and sync scope can be limited with domain rules. You should still start with a small trusted domain list and review security details for sensitive workflows.

The client is open source because that is the part users need to inspect for privacy, encryption, and local key handling. The hosted service remains closed to support commercial sustainability, reduce abusive private-host cloning, and protect operational routing and anti-abuse systems. That does not give the server access to plaintext cookie payloads.

Chrome and Firefox on desktop are the clearest starting point. Edge and Brave are also supported, and some other Chromium-based browsers may work. Mobile support is narrower and should be checked against the browser support page.

You can configure sync rules using whitelist or blacklist modes. In whitelist mode, only the domains you explicitly include will be synchronized. In blacklist mode, all domains are synced except those you exclude.

Yes. If the supported browsers are signed into the same StayLogged account and the domain is allowed by your sync rules, your session state can move between those devices.

Removing the extension stops local sync participation on that browser. Any encrypted server-side sync material tied to your account is separate from uninstalling a single browser and should be managed through your account flows.

Yes. Cross-browser session sync between Chrome and Firefox is one of the main product use cases.

Sync is intended to feel close to real time, but exact timing can vary with browser state, network conditions, and whether the target browser is active and signed in.

The browser extension client is open source because that is the part users need to audit for encryption, privacy, and local key handling. The hosted service remains closed to keep the product commercially sustainable, reduce abusive private-host copying, and protect operational routing and anti-abuse logic while still keeping encrypted cookie payloads unreadable to the server.

StayLogged is built for normal browser session data rather than unrestricted arbitrary storage. If you are evaluating larger-scale use, test with your real domains and browser mix first.

Yes, you can manage which domains to sync using whitelist or blacklist controls. This allows you to sync only the sites you trust while keeping sensitive sites local.

If the site rotates or invalidates the session after a password change, you may need to log in again so the updated session state can be synced.

Start by checking that both browsers use the same StayLogged account, the target domain is allowed by your sync rules, and the browser combination is listed as supported. Then move to the troubleshooting page for step-by-step checks.