Users authenticate before Pages are imported. This avoids asking non-technical users to manually paste user access tokens.
Facebook Page access should be treated as production infrastructure
Security and data handling notes for PubliNest: Facebook Login, encrypted Page tokens, Postgres storage, admin controls, and disconnect workflows.
Page access tokens are stored through the backend token vault and encrypted before they are persisted.
Workspace data, queue posts, billing state, audit events, and publish status are stored in Supabase Postgres.
Operators can disconnect a Page, which removes the stored token and pauses publishing for that Page.
Admin screens expose launch readiness, token state, Page operations, and billing controls.
Authenticated workspace routes are marked noindex so search engines focus on public product content.