Flow-Flow LinkedIn App Privacy Policy
The Flow-Flow: Social Stream is a WordPress plugin which provides users to use one LinkedIn client ID for easier authorization procedure. With help of our widget users can easily create media feeds to explore and share public content from LinkedIn platform.
If you have any questions or comments about this Privacy Policy, please contact us.
Information Collection and Storage
We do not collect, store or share any of your Linkedin login information, Access Tokens, content or any kind of data. As the plugin is installed on your website then any information is stored within your website’s database. Your LinkedIn login information is not stored in your database by our plugin. Our plugin stores your LinkedIn Access Token for use in retrieving posts from LinkedIn API. It also temporarily stores the raw JSON data from LinkedIn’s API, which is then displayed as HTML when your web page is loaded. The plugin does not collect any data from the visitors to your website.
Information the Plugin Displays
The plugin optionally displays the following data: photos, photo captions, LinkedIn username, account tagline, the date of the photo and the link to LinkedIn account.
Reading of Data
The plugin is built to be “read only” and so is not able to publish any data to, or edit any data on, the LinkedIn platform. The plugin is intended only to display LinkedIn public content and is not able to publish to LinkedIn or access LinkedIn accounts other than in a “read only” mode. It does not allow to edit or delete photos or make comments on the LinkedIn platform.
Removal of Stored Data
When the plugin is removed from your website the saved data is deleted from your database.
Cookies
We don’t use cookies for storing visitors data or any other purpose.
Changes to this Policy
We may revise this Privacy Policy in the future. If a change is made to this policy that we believe is material then we will update this page. By continuing to use the plugin after those changes become effective, you agree to be bound by the revised Privacy Policy.
Effective: 7st May 2016