Why was I signed out unexpectedly?

PostSnag keeps you signed in with a security token that renews itself automatically in the background, and in uncommon situations that renewal can fail. When it does, PostSnag clears your session and shows the sign-in screen again rather than leaving the extension in a half-signed-in state where something might quietly fail. Seeing the sign-in screen after you were already signed in is expected in that situation, not a sign anything is wrong with your account or your data.

Why this happens

A few specific situations can interrupt the automatic renewal:

• A long stretch without opening PostSnag. If you haven't opened the extension or dashboard in a while, the next moment it checks in can land at an awkward time relative to when your token needed renewing.

• A cleared browser session. If your browser, or a privacy or cleanup tool, clears cookies or stored site data, PostSnag's sign-in state can be cleared right along with it, since that's where it's kept.

• A network hiccup at the exact moment a renewal was due. A brief connection drop at the wrong second can cause that one renewal attempt to fail, even though your connection is fine a moment later.

• Reinstalling the extension. Uninstalling and reinstalling PostSnag starts you with fresh local browser storage, which naturally clears your saved sign-in along with it. This is expected after a reinstall, not a problem with the sign-in itself.

• Strict privacy settings on your browser. Some browsers or privacy tools can be set to clear all site and extension data automatically when the browser closes. If that setting applies to extensions, it clears PostSnag's saved sign-in the same way it would clear a website's.

• A different browser profile or a Guest window. PostSnag's sign-in is stored separately for each Chrome profile. Opening Facebook in a Guest window, or in a different browser profile than the one you installed PostSnag in, looks like being signed out, since that's a separate, empty storage area rather than the session you signed into before.

[Screenshot: The sign-in screen appearing again after PostSnag's automatic renewal fails]

What to do

1. Sign back in from the panel or the toolbar popup, using your email and password or Continue with Google.

2. Trust that your captured data is unaffected. Signing out only clears your sign-in state. Anything you've captured locally, or already sent to your dashboard with Export To Dashboard, stays exactly where it was.

3. Keep PostSnag updated to the latest Chrome Web Store version, since staying current keeps you on the most reliable version of the sign-in system.

4. Check your browser's site data settings if this happens often. Look for a setting that clears cookies or site data on close, and add an exception for extensions or for PostSnag specifically if you find one.

5. Contact support if signing back in doesn't work, or if you're being signed out repeatedly within the same day or two, since that's outside the normal pattern.

Keeping your session from lapsing

If you use PostSnag only occasionally, expect an occasional sign-in prompt when you come back to it; that's just the renewal window having passed. If it happens often despite regular use, it's usually a browser privacy setting clearing extension data on close, and checking that setting once tends to fix it for good.

Common questions

Will I lose my captured posts if I'm signed out?
No. Signing out only affects your sign-in state. Posts you've already captured locally or sent to your dashboard are unaffected either way.

Why did this happen if I use PostSnag regularly?
It's usually a one-off: a network hiccup or a cleared browser session at the wrong moment. Signing back in resolves it immediately.

Does this mean my account was compromised?
No. This is a normal, occasional side effect of how automatic sign-in renewal works, not a sign of unauthorized access to your account.

Does being signed out on the extension also sign me out of the dashboard, or the other way around?
Both the extension and the dashboard use the same PostSnag account and sign-in. Being signed out on one can prompt a sign-in on the other, but your dashboard data itself is never touched by this.

What if signing back in doesn't work?
Double check your email and password, or try Continue with Google instead. If you still can't sign in, email support@postsnag.com.

Why does PostSnag show me as signed out in a Guest window or a different browser profile?
Because sign-in is stored per Chrome profile, not shared across every window on your computer. Sign in again on that specific profile or Guest window if you plan to use PostSnag there regularly.