1. Proposed flow
- The desktop app opens the official HTTPS page in the system browser.
- The server creates a one-time transaction, validates state, and receives Meta's callback.
- The App Secret remains server-side and is never returned to the website or installer.
- The desktop app receives only a one-time result code and redeems it over HTTPS.
2. Data and purpose
The app uses authorized Page lists and tasks so the user can select the correct destination. It uses user-approved content, media, and schedules to create or manage posts. Data is not used beyond the selected function.
3. Proposed minimum permissions
- pages_show_list — list Pages the person may manage.
- pages_manage_posts — create, edit, or remove Page posts on request.
- pages_read_engagement — only when required to verify posts/status and reporting.
- business_management — only if the actual customer and Business asset flow requires it; never by default.
4. User control
- Select specific Pages per project.
- Review and approve before publishing according to configuration.
- Disconnect in x100traffic or revoke access in Facebook.
- Request deletion through the Data Deletion page.
5. Safe migration
The current five token sources and 77 Pages must be inventoried, backed up, and reconciled before and after any change. New OAuth runs in parallel per tenant and must not overwrite, disable, or migrate existing tokens without a separate approved rollback plan.