Is Group Posting Pro safe?

It can't rule that out — no tool can promise zero risk on a platform it doesn't control. It lowers the risk: randomised gaps between posts, a minimum gap that grows with your daily volume, an optional warm-up for new accounts, a 10 PM–7 AM night pause, a risk check before you start a run by hand, and a 12-hour stop if Facebook blocks the account. Facebook's limits, group rules and admin approval still apply.

Group Posting helps you post to groups you belong to, at a human-like pace, with content you control. You're responsible for following each group's rules and Facebook's terms. The safety layer exists to keep your activity natural and within healthy limits — it's a tool for legitimate marketing, not spam.

You do not give Group Posting your Facebook password. The extension uses your existing logged-in session; Direct API posting uses session cookies and request tokens locally to authenticate requests to Facebook. These credentials are not sent to Group Posting’s servers.

Posting sends your content to Facebook from your own browser. AI features send the text and context needed for generation to our service. Pro includes a daily cloud backup — part of the plan, not an extra — which sends a copy of your group list, templates, campaigns, schedules and recent results to the service so you can restore them; on the free and Plus plans nothing is uploaded. Licensing, diagnostics and checkout also involve service requests. Full details are in our Privacy Policy.

Only if you connect it yourself, inside the extension. A marketing agency can run Group Posting for you: they schedule, and your own browser publishes with your own Facebook login — they never hold a password. Before anything is shared the extension shows you a sheet listing exactly what that agency would see: your group list and collections, the names and Facebook id numbers of your profile and Pages and the picture each one shows on Facebook, the results of the posts they schedule, and general extension health. Nothing about your groups, your profile, your Pages or your posting is shared until you tick the box and press Connect — the only thing that goes out before that is the code itself and a random installation id, to our own server, so the sheet can name the agency that is asking. They never get your password, session, messages, the posts and schedules you made yourself, or your Lead Radar inbox. An agency can also set Lead Radar up for you: which of your groups it watches, the words it looks for, the words that rule a post out, how often it scans, whether it is running, whether it replies to matching posts under your account automatically, and how those replies are written: how helpful they sound, how much they sell, how direct they are, and a short note of up to 400 characters the agency adds about your business. While the agency manages Lead Radar, its groups, keywords, scan interval, daily reply limit and reply preferences are locked. You can switch automatic replies off or pause them in Lead Radar. Once Group Posting confirms your OFF choice, it blocks new managed automatic replies for that Facebook profile or Page across compatible browsers connected to the same agency client. A new agency setup cannot clear it. Only the original browser profile can clear its own OFF choice, with an active connection and an online confirmation. Other browsers' OFF choices remain effective. Clearing a choice does not arm a setup, start replies or remove other holds. Ask the agency to change locked settings, or disconnect to restore your saved settings. This control applies to agency-managed automatic replies, not personal Lead Radar or manually drafted replies. An OFF choice saved in this browser takes effect locally; other browsers are not yet protected by that new choice until the service acknowledges it. If this browser's connection credential has expired or been replaced, reconnect in this original browser profile to send its saved choice. An error does not discard the pending choice. Compatible browsers require a fresh shared-state check before preparing and immediately before dispatching a managed automatic reply, and wait if that check is unavailable. A reply already admitted and sent toward Facebook may still finish. The agency can see whether a shared OFF hold exists for the selected profile or Page, but not which browser set it or an offline choice that has not reached the service. A confirmed OFF choice survives disconnect, reconnect, a new agency setup and Also delete. The service retains its minimal authority and replay-prevention records until 90 days after the last active connection to that agency client ends; a later archive or edit does not restart that clock. Clearing requires the original browser profile's local proof, which exports and cloud backups do not contain. If that proof is lost, another browser, the agency and support cannot clear the choice. What Lead Radar finds is never sent to us for that agency. You can pause their posting or disconnect at any time in Settings, and both work with no internet connection. Full detail is in section 5 of our Privacy Policy.

No. An agency can set Lead Radar up for you — which of your groups it watches, the words it looks for, the words that rule a post out, how often it scans, whether it is running, whether it replies to matching posts under your own account automatically, up to a daily limit of at most ten, and how those replies are written: how helpful they sound, how much they sell, how direct they are, and a short note of up to 400 characters the agency adds about your business. What it finds is a different thing: every matching post, every person behind one, your notes and even how many there were are never sent to us for that agency. There is no screen in the agency dashboard that shows them and no table in our database they could be written to; they stay on your own computer, apart from your own Pro cloud backup if you have one, which section 4 of the Privacy Policy describes. An agency cannot add a Lead Radar webhook, cannot change your notification settings, and cannot read your reply history. Their setup replaces your own Lead Radar settings on that browser while they manage it; yours are saved first and come back when you disconnect. While the agency manages Lead Radar, its groups, keywords, scan interval, daily reply limit and reply preferences are locked. You can switch automatic replies off or pause them in Lead Radar. Once Group Posting confirms your OFF choice, it blocks new managed automatic replies for that Facebook profile or Page across compatible browsers connected to the same agency client. A new agency setup cannot clear it. Only the original browser profile can clear its own OFF choice, with an active connection and an online confirmation. Other browsers' OFF choices remain effective. Clearing a choice does not arm a setup, start replies or remove other holds. Ask the agency to change locked settings, or disconnect to restore your saved settings. This control applies to agency-managed automatic replies, not personal Lead Radar or manually drafted replies. An OFF choice saved in this browser takes effect locally; other browsers are not yet protected by that new choice until the service acknowledges it. If this browser's connection credential has expired or been replaced, reconnect in this original browser profile to send its saved choice. An error does not discard the pending choice. Compatible browsers require a fresh shared-state check before preparing and immediately before dispatching a managed automatic reply, and wait if that check is unavailable. A reply already admitted and sent toward Facebook may still finish. The agency can see whether a shared OFF hold exists for the selected profile or Page, but not which browser set it or an offline choice that has not reached the service. A confirmed OFF choice survives disconnect, reconnect, a new agency setup and Also delete. The service retains its minimal authority and replay-prevention records until 90 days after the last active connection to that agency client ends; a later archive or edit does not restart that clock. Clearing requires the original browser profile's local proof, which exports and cloud backups do not contain. If that proof is lost, another browser, the agency and support cannot clear the choice. The automatic replies also only run while your own AI Studio profile is switched on with your offer described, and only in a group you have marked Allowed for service or promotional replies under Group permissions in Lead Radar's Automation tab, neither of which an agency can do for you. Drafting each reply sends the text of the post, the name of the group it was found in, your own note about that group's rules and whether it allows promotion and links, and your own AI Studio profile and writing voice to our AI provider; the name of the person who wrote the post is not sent. The proof, retention and recovery details are in section 5 of our Privacy Policy.

It's designed for it: the engine spaces posts out with randomised gaps, raises the minimum gap as your daily volume grows, pauses between 10 PM and 7 AM when "Avoid night posting" is on, and stops scheduled posts and campaigns for 12 hours if Facebook blocks the account. Even so, no tool can promise zero risk on a platform it doesn't control. Runs need your computer awake and Chrome open.

No. Direct API posting sends authenticated internal Facebook web GraphQL requests from your own logged-in browser. Classic DOM posting automates the visible composer in the same browser. Neither method uses Group Posting’s servers to log into Facebook, and neither relies on the retired public Facebook Groups API. API posting does not itself mean cloud posting.