PressQueue keeps its settings and sharing history in your WordPress database. It has no hosted service, no account and no tracking.
What is stored
For every post it checks and every share it creates, PressQueue keeps a record: post and user IDs, channel details, the message it prepared, image addresses and Buffer's receipts. These records explain in Activity what happened, and they stop a post from being shared twice.
Your Buffer key
The key is encrypted with your site's security keys and salts and stays on your server. It is sent to Buffer only, and it is never part of an export. If you change the keys and salts, the saved key becomes unreadable. Paste it again under Channels, "More", "Replace API key".
What leaves your server
When you connect Buffer or refresh channels, PressQueue sends your API key to api.buffer.com and reads your account name, organizations and channels.
In Live mode, each share sends Buffer the message text, the post link, the channel, the timing and, when the share has an image, the image address and alt text. Choosing an image may also contact the image's host to check the file type, size and dimensions.
PressQueue sends no analytics or tracking requests. For what Buffer does with the data, read Buffer's terms and privacy policy.
Download your data
Under Settings, Data and privacy, "Download your data" gives you a JSON file with your rules, channels, settings and sharing history. The Buffer key is never included. The text of each share and the links to its images are left out unless you tick "Include message text and image URLs" and confirm it. Treat a file that contains message text as private site data.
One file holds up to 10,000 records. If a file ends with "truncated": true, copy its "next_cursor" value into "Continue from" under "Very large sites" and download again.
The WordPress privacy tools under Tools, "Export Personal Data" and "Erase Personal Data", cover PressQueue records linked to a person's WordPress user as well. Erasure clears the fields that say which user carried out an action. It keeps references the history needs, such as the post author, and the erasure report says so.
Keep history
Automatic removal of old history starts switched off. To turn it on, tick "Remove old history automatically", set "Keep history for" to a number of days between 30 and 3650, confirm that old history is deleted for good, and click "Save history settings". Cleanup then runs once a day in the background. "Clean up now" runs it right away.
What is removed: test runs, cancelled shares, finished batches and the checks behind them, once they are older than the period. Buffer error details on old shares are cleared, and so is the message text of old shares Buffer accepted.
What stays: shares that are waiting, failed or need checking. For every share Buffer accepted, PressQueue keeps a small record without the message, so no post is shared twice by accident. Rules, channels and settings are never removed.
When you delete PressQueue
Deactivating never deletes anything. Deleting the plugin keeps your data too, so you can install it again and continue where you left off.
To remove everything, tick "Delete all PressQueue data when the plugin is deleted" under "When you delete PressQueue", confirm, and click "Save deletion setting" before you delete the plugin. That removes rules, channels, history, settings, the saved Buffer key, sharing settings on posts and scheduled background tasks from the site. Posts Buffer already accepted stay in Buffer.
On a multisite network, each site has its own deletion setting.
Background sharing status
The top of the Data and privacy page says whether background sharing is running. If it is stopped, it says why and what to do. Shares wait until it runs again.