Is PostSnag safe to use?

PostSnag is safe to use: it's read-only, runs client-side in your own logged-in Facebook session, and only reads the public posts already loading on your screen. It never posts, likes, comments, messages, or follows anyone on your behalf, and it never asks for your Facebook password.

Here's exactly how that works, mechanically, so you're not just taking that on faith.

PostSnag runs client-side, in your own session

PostSnag runs inside your own browser, using the Facebook account you're already signed into. There's no separate PostSnag login to Facebook happening somewhere else; it's the same session your browser already has open, reading the same page you're already looking at.

PostSnag is read-only

As you scroll, PostSnag reads the post data your own session is already receiving from Facebook, along with what's rendered on the page, and it saves that to your browser. It doesn't request anything beyond what your normal browsing already causes Facebook to send you. The one narrow exception: when you export a Facebook Group capture, PostSnag makes one same-origin request to that group's own public page, in your own session, to read the group's name and cover image, the same way your browser would load that page anyway if you visited it directly.

PostSnag never acts on your behalf

PostSnag has no feature that posts, likes, comments, messages, follows, or friends anyone for you. It only reads and saves data; it never takes an action that Facebook, or anyone looking at your account, would see as you doing something.

No proxies, no fake accounts, no automation

PostSnag doesn't route your capture through proxy servers, doesn't spin up secondary or fake accounts, and doesn't automate actions on Facebook. Nothing pretends to be you, and nothing runs hidden requests behind the scenes beyond the one group-lookup exception above.

What permissions the extension actually asks for

When you install PostSnag, Chrome shows a short list of permissions. Here's what each one does:

• Storage, to save posts you've captured locally in your browser until you export them.

• Active tab, to read the Facebook tab you currently have open.

• Identity, used only if you choose Continue with Google to sign in.

• Declarative net request, a narrowly scoped permission used only to help read a Facebook Group's public name and cover image when exporting a group capture. It is never applied to your regular Facebook browsing.

PostSnag also requests host access to facebook.com, since that's the only site it works on, and to the domain that loads cached post images in your dashboard. See Why does PostSnag ask for the permissions it does? for the full breakdown.

Does PostSnag put your Facebook account at risk?

A common worry: can using PostSnag get a Facebook account restricted or banned? PostSnag behaves like ordinary browsing. You're signed into your own account, looking at public posts you could see anyway, and PostSnag reads and saves what's already there without logging in on its own, using fake accounts, or taking any action Facebook would flag as automated. See Will PostSnag get my Facebook account banned? and Is using PostSnag against Facebook's rules? for the fuller answers to each specific worry.

Is my PostSnag account and data safe?

Separately from the Facebook-safety question, your PostSnag account itself is protected with hashed passwords and encrypted connections, and PostSnag never sees or stores your Google password if you sign in that way. PostSnag doesn't sell your data. See Does PostSnag sell my data? and Where is my data stored, and who does PostSnag work with? for the full privacy picture.

Common questions

Does PostSnag automate anything on Facebook?
No. PostSnag never automates actions like posting, liking, commenting, or following. It only reads public posts already on your screen.

Does PostSnag use fake accounts or proxies?
No. It works entirely through your own logged-in Facebook session, with one narrow exception for reading a Group's own public page during export.

Can PostSnag post, comment, or message on my behalf?
No, never. PostSnag has no feature that takes any action on Facebook for you.

Why does PostSnag need the permissions it asks for during install?
Each permission maps to something specific: saving your captures locally, reading the Facebook tab you're on, signing in with Google if you choose to, and one narrow fix for reading a group's public name and cover. See Why does PostSnag ask for the permissions it does?

Will using PostSnag get my Facebook account banned?
See Will PostSnag get my Facebook account banned? for the full answer. In short, PostSnag is built to behave like normal browsing, not automated activity.

PostSnag is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc.