Trust and permissions
What PostMesa asks each network for, why, what it will not do, and how to stop it.
Exactly what we ask for
This is the list the app sends when you connect a channel, read from the code. You can remove PostMesa at any time in the network's own settings, and the next connect asks again.
Instagram and Facebook (one Meta login)
Connecting a Page and its Instagram account is a single Meta consent screen, so Instagram and Facebook share one list.
public_profile: Meta requires it to sign you in. It gives us your name and ID.pages_show_list: Lists the Facebook Pages you manage so you can pick which to connect.business_management: Finds Pages and Instagram accounts that are owned through a Meta Business portfolio.pages_manage_posts: Publishes the Facebook Page posts you schedule.instagram_basic: Reads the basic details of the Instagram account linked to your Page, such as its name and picture.instagram_content_publish: Publishes the Instagram posts and Reels you schedule.pages_read_engagement: Reads your Page posts and their comments so replies can be matched to the right post.pages_read_user_content: Reads comments that people leave on your Page posts, which Meta requires before a Page can reply to them.pages_manage_engagement: Posts your public reply to a comment on a Facebook Page post.instagram_manage_comments: Reads comments on your Instagram posts and posts your public reply.pages_manage_metadata: Subscribes PostMesa to your Page's comment and message notifications, so an automation hears about a new comment.pages_messaging: Sends the DM from your Page to someone whose comment matched your automation.instagram_manage_messages: Sends the DM from your Instagram account to someone whose comment matched your automation.instagram_manage_insights: Reads how your own Instagram posts perform, to suggest good times to post.
YouTube
Google asks for these on its own consent screen.
https://www.googleapis.com/auth/youtube.upload: Uploads the videos you schedule.https://www.googleapis.com/auth/youtube.force-ssl: Reads comments on your videos and posts your public replies.
Twitter/X
Twitter/X asks for these on its own consent screen.
tweet.read: Lets PostMesa check that a post it sent went through.tweet.write: Publishes the posts you schedule.users.read: Reads the name and ID of the account you connect.media.write: Uploads the pictures and video that go with a post.offline.access: Keeps the connection working at the scheduled time without asking you to sign in again.
TikTok
TikTok asks for these on its own consent screen.
user.info.basic: Reads the name and picture of the account you connect.video.publish: Publishes the videos and photo posts you schedule.
LinkedIn asks for these on its own consent screen. PostMesa connects your personal profile only, not a Company Page. It does not read your feed, your connections or your messages.
openid: Signs you in with LinkedIn so PostMesa knows which member is connecting. It gives us your member ID.profile: Reads the name and picture of the profile you connect.w_member_social: Publishes the text and image posts you schedule to your profile.
Meta shows these as a single consent screen where you pick the Pages and Instagram accounts to connect. Anything you do not pick is not shared.
What PostMesa never does
- It never publishes anything you did not create in PostMesa. A post goes out only because you scheduled it or chose Publish now.
- It never sends a DM unprompted. A DM goes only to a person whose comment matched an automation you set up, either one of your keywords or, if you chose that, any comment on that post.
- The second message, the one with your link, is sent only when that person taps the button in the first DM, inside Meta's 24-hour window. A private reply to a comment must happen within 7 days of the comment.
- It never lets AI send a message. AI only drafts suggestions, and a person on your workspace approves each one.
- It never stores your network password. It stores the access token the network gives it, encrypted.
- On LinkedIn it never posts to a Company Page, and never reads your feed, connections or messages. It asks only to sign you in, read your name and picture, and publish the posts you schedule to your own profile.
- On Bluesky there is no permission screen: you connect with an app password you create in Bluesky. PostMesa uses it once to sign in and does not store it. It keeps the session tokens Bluesky returns, encrypted, reads your handle, name and picture, and publishes the posts you schedule. It never reads or sends Bluesky messages.
How to stop it
- Pause one automation: open it and select Pause. It stops answering new comments. Select Resume to turn it back on.
- Disconnect a channel: PostMesa asks the network to revoke its access and stops acting on that channel. Automations on it stop answering comments.
- Remove PostMesa on the network: in your Instagram, Facebook, Google, Twitter/X, TikTok or LinkedIn settings you can remove the app's access whenever you like. On Bluesky, delete the app password you created for PostMesa.
- Delete your data: see the data deletion instructions.
Every automated reply and DM is logged
Each comment an automation handles becomes a run. The run log shows each step it took (the public reply, the first DM, the second DM), whether it worked, and the reason when it did not.
Activity lists those runs next to your published and failed posts, and you can filter it by channel, automation and outcome. It shows our own status and reason codes, never the commenter's text. It looks back as far as your workspace setting: 30, 90 or 365 days.