Initial release<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.1.5"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3213018,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3213018,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3213018,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3213018,"resolution":"4","location":"assets","locale":""}},"screenshots":{"1":"What has been shared and coming to share are displayed at screenshot-1.(png|jpg|jpeg|gif).","2":"A list of created schedules are displayed in screenshot-2.(png|jpg|jpeg|gif)","3":"A list of authorized accounts are displayed in screenshot-3.(png|jpg|jpeg|gif)","4":"A list of database logs are displayed in screenshot-4.(png|jpg|jpeg|gif)"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[2015,13082,13078,154,904],"plugin_category":[],"plugin_contributors":[236117],"plugin_business_model":[],"class_list":["post-208194","plugin","type-plugin","status-publish","hentry","plugin_tags-auto-post","plugin_tags-autopost","plugin_tags-repost","plugin_tags-social-media","plugin_tags-social-network","plugin_contributors-sabali33","plugin_committers-sabali33"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/nevamiss.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/nevamiss\/assets\/screenshot-1.png?rev=3213018","caption":"What has been shared and coming to share are displayed at screenshot-1.(png|jpg|jpeg|gif)."},{"src":"https:\/\/ps.w.org\/nevamiss\/assets\/screenshot-2.png?rev=3213018","caption":"A list of created schedules are displayed in screenshot-2.(png|jpg|jpeg|gif)"},{"src":"https:\/\/ps.w.org\/nevamiss\/assets\/screenshot-3.png?rev=3213018","caption":"A list of authorized accounts are displayed in screenshot-3.(png|jpg|jpeg|gif)"},{"src":"https:\/\/ps.w.org\/nevamiss\/assets\/screenshot-4.png?rev=3213018","caption":"A list of database logs are displayed in screenshot-4.(png|jpg|jpeg|gif)"}],"raw_content":"\n
This project is a WordPress plugin that allows site administrators to share their content to social media networks\nIt requires configuration and authorization of the supported social media networks.<\/p>\n\n
\u2013 Install this plugin at Dashboard > Plugins > Add New.\n\u2013 Go to Auto Share > Settings > General > API Keys & Secrets the add API keys for the networks you intend to post to.\n\u2013 Login to the configured networks at Auto Share > Settings > Network Accounts.\n\u2013 That's all<\/p>\n\n
\u2013 Instantly share post to social media accounts\n\u2013 Create crons called schedules to share contents at selected times\n\u2013 Support multiple login to different accounts on the same network.\n\u2013 Re-order the order of sharing for schedule posts.\n\u2013 Track shared posts for schedules\n\u2013 Display upcoming posts and last shared posts\n\u2013 URL shortnering<\/p>\n\n
\u2013 Facebook\n\u2013 X\n\u2013 Linkedin\n\u2013 Instagram<\/p>\n\n
\u2013 Rebrandly<\/p>\n\n
This plugin connects to third-party APIs to provide its features. These connections occur only after explicit authorization by the site administrator. The plugin enables features such as posting content to social media accounts, creating short URLs, and retrieving user account details. Below is a comprehensive explanation of how the plugin interacts with these external services and ensures compliance with privacy and security standards.<\/p>\n\n
The plugin collects and processes the following data to enable integration with external services:\n\u2013 Usernames or full names<\/strong>: Used for account identification.\n\u2013 Remote account IDs<\/strong>: Required for managing external accounts via the plugin.\n\u2013 Access tokens and expiry dates<\/strong>: Used for authentication and secure API communication.<\/p>\n\n This data is:\n1. Stored securely in the WordPress database, encrypted when applicable.\n2. Used solely to perform authorized actions, such as posting content or scheduling tasks.\n3. Removed when the user revokes authorization or deletes the plugin.<\/p>\n\n The plugin does not collect or share any additional data beyond what is required to facilitate its features.<\/p>\n\n \u2013 The plugin requires explicit user authorization<\/strong> before connecting to any external service. Users are presented with a consent screen detailing:\n \u2013 The purpose of the connection.\n \u2013 The data that will be shared.\n \u2013 Links to the external service\u2019s privacy policy.\n\u2013 No data is transmitted to third-party services without user consent.\n\u2013 Users can revoke access at any time via the plugin\u2019s settings. Upon revocation, all related data is securely deleted.<\/p>\n\n The plugin complies with global privacy regulations, including GDPR and CCPA. It minimizes data collection and ensures that users can exercise their rights to data access, correction, and deletion.<\/p>\n\n \u2013 All API communications occur over secure HTTPS connections.\n\u2013 Access tokens are stored encrypted and are not exposed to unauthorized users.\n\u2013 Expired tokens are automatically removed, and users are prompted to reauthorize when necessary.\n\u2013 The plugin implements error handling for API requests, including retries and logging failures in a secure log file.<\/p>\n\n Below are the external services used by the plugin, their APIs, and links to their respective terms and policies:<\/p>\n\n \u2013 Purpose<\/strong>: Short URL generation for social media posts.\n\u2013 API<\/strong>: API Link<\/a>\n\u2013 Terms of Service<\/strong>: Rebrandly Terms<\/a>\n\u2013 Privacy Policy<\/strong>: Rebrandly Privacy Policy<\/a><\/p>\n\n \u2013 Purpose<\/strong>: Content posting, media upload, and account management.\n\u2013 APIs<\/strong>: \u2013 Purpose<\/strong>: Content posting, account retrieval, and page management.\n\u2013 APIs<\/strong>: \u2013 Purpose<\/strong>: Content posting and account management.\n\u2013 APIs<\/strong>: \u2013 Purpose<\/strong>: Content posting and account management.\n\u2013 APIs<\/strong>: \u2014<\/p>\n\n This plugin provides a privacy policy section in the plugin\u2019s settings page, summarizing:\n1. The data collected and its purpose.\n2. The list of external services used.\n3. User rights regarding data access, correction, and deletion.\n4. A direct link to the plugin documentation.<\/p>\n\n The plugin reaches out to the supported social media networks APIs in the following circumstances:\n\u2013 When a user authenticates via their social media account to grant access.\n\u2013 When posting content on behalf of the user (through schedules).\n\u2013 When a user manually decides to instantly share a WordPress post to authorized social media accounts.\n\u2013 Create a UI interface where site managers can post custom content based on a category of posts.<\/p>\n\n\n Yes you need API keys for the supported networks.<\/p><\/dd>\n For some networks such as Facebook, Instagram and X you need to subscribe to their products to be able to get\nproduction API credentials. For LinkedIn probably no unless you are a heavy user.<\/p><\/dd>\nUser Consent and Privacy<\/h3>\n\n
Security Practices<\/h3>\n\n
List of External Services<\/h3>\n\n
Rebrandly<\/h4>\n\n
X (formerly Twitter)<\/h4>\n\n
\n \u2013 Authorization<\/a>: Used for user login and token generation.
\n \u2013 Media Upload<\/a>: Used for uploading media files.
\n \u2013 Posting<\/a>: Used for posting text-based content.
\n\u2013 Terms of Service<\/strong>: Developer Terms<\/a>
\n\u2013 Privacy Policy<\/strong>: X Privacy Policy<\/a><\/p>\n\nFacebook<\/h4>\n\n
\n \u2013 Authorization<\/a>: Used to initiate user login and consent.
\n \u2013 Access Tokens<\/a>: Used to retrieve access tokens after user consent.
\n \u2013 Graph API<\/a>: Used to manage user accounts and post content.
\n\u2013 Terms of Service<\/strong>: Facebook Platform Terms<\/a>
\n\u2013 Privacy Policy<\/strong>: Facebook Privacy Policy<\/a><\/p>\n\nInstagram<\/h4>\n\n
\n \u2013 Authorization<\/a>: Used for user login and token generation.
\n \u2013 Access Tokens<\/a>: Used to retrieve access tokens.
\n \u2013 Graph API<\/a>: Used for posting content and retrieving account details.
\n\u2013 Terms of Service<\/strong>: Instagram Platform Terms<\/a>
\n\u2013 Privacy Policies<\/strong>:
\n \u2013 Developer Privacy Policy<\/a>
\n \u2013 General Instagram Privacy Policy<\/a><\/p>\n\nLinkedIn<\/h4>\n\n
\n \u2013 Authorization<\/a>: Used to create login and consent flow.
\n \u2013 API Root<\/a>: Used for accessing user data and posting content.
\n \u2013 Version 2 API<\/a>: An updated version of the API.
\n\u2013 Terms of Service<\/strong>: LinkedIn API Terms<\/a>
\n\u2013 Privacy Policy<\/strong>: LinkedIn Privacy Policy<\/a><\/p>\n\nPlugin Privacy Policy<\/h3>\n\n
When Does the Plugin Communicate with These Services?<\/h3>\n\n
\n
Do I need API keys for each network?<\/h3><\/dt>\n
Am I going to pay for the API keys usage?<\/h3><\/dt>\n