Security and trust
Built for teams that publish where mistakes are expensive.
AckPost is designed around approval, visibility, and connected-account accountability. This page explains the practical controls behind the product today and the security direction as the platform matures.
OAuth-based access
AckPost connects to social and publishing platforms through provider-approved authorization flows. We do not ask for or store your social account passwords.
Least-privilege permissions
Connections request the permissions needed for publishing, account mapping, media handling, and status checks where each provider supports them.
Encrypted token storage
Provider tokens and sensitive integration data are stored using managed infrastructure controls and are treated as restricted application secrets.
Approval gates
Teams can keep posts and articles in review before anything is scheduled or published, reducing accidental posts and client-facing mistakes.
Audit history
Publishing, approval, team, and connection events are tracked so teams can reconstruct what changed, who acted, and when it happened.
Connection health
AckPost surfaces destinations that need reauth, mapping, or permission attention so teams can fix problems before busy publishing windows.
Operating model
Security that shows up in the workflow.
AckPost does not treat security as a separate page users never see. The product puts approvals, audit events, and connection health close to daily publishing work.
- Role-aware access to workspace areas and admin surfaces.
- Separate brand, destination, and workspace records for cleaner operating boundaries.
- Operational monitoring for API errors, failed publishing jobs, and security-relevant activity.
- Data deletion, privacy, and account support paths available from the public footer.
- SOC 2 readiness planning as AckPost matures beyond beta.