Publish once, share everywhere.
Zware Automatic Social Posts and Login (ZASP) is a plugin that does two things:
Connect your accounts once and ZASP handles publishing automatically:
Per-post share controls β the post editor includes a ZASP panel where you can share to each connected network individually and see the last share status per network.
Stable token storage β access tokens are stored encrypted in a dedicated database table using libsodium when available. A weekly health check verifies Facebook/Instagram token validity. X tokens auto-refresh before expiry.
Let your visitors skip the registration form:
Three button styles: default (icon + text), rounded, and icon-only.
OAuth callbacks use WordPress REST API endpoints (/wp-json/zasp/v1/login/{network}/callback) for compatibility with caching plugins.
User creation: Social login creates WordPress user accounts using standard WordPress functions (wp_create_user, wp_set_auth_cookie). New accounts are assigned the role configured in Settings Login Social (default: Subscriber). Apple identity tokens are verified against Appleβs public keys before any account is created or accessed. It is strongly recommended to set the default role to Subscriber and to restrict registration via the siteβs General Settings if you do not wish to allow open registration.
Expand to more platforms with the ZASP Premium add-on (available at zwareonline.com):
This plugin connects to the following external services. Data is only sent when you or your users explicitly trigger the relevant action (connecting an account, publishing a post, or logging in).
Meta / Facebook Graph API (https://graph.facebook.com, https://graph.threads.net)
Used to publish posts to Facebook Pages, Instagram Business/Creator accounts, and Threads. Called when: (a) you connect a Facebook, Instagram, or Threads account; (b) a post is published and auto-posting is enabled; (c) you share manually from the post editor.
Data sent: your Facebook Page access token, post title, post content/excerpt, post URL, and featured image (if any).
Meta Terms of Service Β· Meta Privacy Policy
X / Twitter API (https://api.twitter.com, https://twitter.com/i/oauth2)
Used to post tweets and to authenticate your X account via OAuth 2.0 PKCE. Called when: (a) you connect your X account; (b) a post is published and auto-posting is enabled; (c) you share manually; (d) a user logs in with X.
Data sent: your X OAuth credentials, post content, and (optionally) the featured image.
X Terms of Service Β· X Privacy Policy
Bluesky / AT Protocol (https://bsky.social)
Used to post to Bluesky using app passwords. Called when a post is published and auto-posting is enabled, or when you share manually from the post editor.
Data sent: your Bluesky handle, app password (used to obtain a session token), post content, and (optionally) the featured image.
Bluesky Terms of Service Β· Bluesky Privacy Policy
Mastodon (user-configured instance)
Used to post to the Mastodon instance you configure. Called when a post is published and auto-posting is enabled, or when you share manually. The specific API domain depends on your configured instance (e.g., https://mastodon.social).
Data sent: your Mastodon instance URL, OAuth credentials, post content, and (optionally) the featured image.
Mastodon Privacy Policy (varies by instance)
Truth Social (https://truthsocial.com)
Used to post to Truth Social via its Mastodon-compatible API. Called when a post is published and auto-posting is enabled, or when you share manually.
Data sent: your Truth Social OAuth credentials, post content.
Truth Social Terms Β· Truth Social Privacy Policy
Google OAuth2 (https://accounts.google.com)
Used to sign users into your WordPress site via Google (OpenID Connect). Called only during a user login/registration flow initiated by the user.
Data sent: your Google OAuth2 Client ID and Client Secret. Google returns the userβs name, email, and profile picture URL, which are stored in your WordPress database.
Google Terms of Service Β· Google Privacy Policy
Apple ID (https://appleid.apple.com)
Used to sign users into your site via Sign in with Apple. Called only during a user login/registration flow.
Data sent: your Apple Services ID and team credentials. Apple returns a signed identity token containing the userβs name and email, which are stored in your WordPress database.
Apple Terms of Service Β· Apple Privacy Policy
Twitch API (https://api.twitch.tv, https://id.twitch.tv)
Used to sign users into your site via Twitch OAuth 2.0. Called only during a user login/registration flow.
Data sent: your Twitch Client ID and Client Secret. Twitch returns the userβs display name and email, which are stored in your WordPress database.
Twitch Terms of Service Β· Twitch Privacy Policy
Discord API (https://discord.com/api)
Used to sign users into your site via Discord OAuth 2.0. Called only during a user login/registration flow.
Data sent: your Discord Client ID and Client Secret. Discord returns the userβs username and email, which are stored in your WordPress database.
Discord Terms of Service Β· Discord Privacy Policy
No data is ever sent to Zware Online servers by this plugin.
ZASP stores access tokens and user data (names, emails, social network UIDs) in your own WordPress database. No data is transmitted to Zware Online or any third party beyond the social network services listed above and as described in each serviceβs entry.
For support, visit zwareonline.com or email support@zwareonline.com.