Official authorization
Connections use the authorization method the platform supports. Aboveboard does not scrape a logged-in session, reuse browser cookies or automate a browser behind your back.
Security
Controls you can inspect. No borrowed credibility.
Narrow access, encrypted credentials and private storage protect your work. Publishing requires approval, with individual review as the default.
Protection by mechanism
Six controls around the work that matters
Security is not a single lock. These controls limit how credentials, content and publishing authority move through Aboveboard.
Encrypted credentials
Connection credentials are encrypted at rest. They are made available only to the authorized service path that needs to call that provider.
Private media
Uploaded media stays in private object storage. Time-limited signed links handle upload and provider delivery instead of turning the bucket public.
Separated permissions
Workspace roles separate administration, drafting and approval. An editor can prepare content without gaining the reviewer’s publishing permission.
Human approval
New drafts wait for a permitted reviewer. Eligible unchanged public posts from your own account may follow an explicitly authorized reuse rule; edits and sensitive content return to individual review.
AI and data boundaries
Aboveboard uses customer context to return the requested draft or research result, not to train a shared model. Provider handling is governed by the published privacy commitments.
The outbound path
Nothing goes straight from a prompt to a platform
Publishing is a sequence of checks. Each gate answers a different question before the next one can open.
- Member
Authenticated request
A signed-in workspace member starts the action.
- Role
Permission check
The member’s role must allow the requested operation.
- Person
Explicit approval
A permitted reviewer signs off on the exact draft.
- Provider
Official API
Only then is the approved content sent to the platform.
Your data, your exit
Control should still work when you leave
Workspace owners can download a bounded data export and request account or data deletion for manual review. The Privacy Policy explains how to request deletion and how retained records and backups are handled.
Content already published to a social platform remains subject to that platform’s own controls and retention. Disconnecting Aboveboard does not rewrite another company’s systems.
Export
Take a workspace data export before closing the account.
Disconnect
Remove a channel connection and revoke access at its platform.
Request deletion
Submit a deletion request in Settings or contact privacy support. A person reviews the request before data is removed.
Clear boundaries
What Aboveboard will not do
-
Scrape logged-in platform pages or automate a browser session.
-
Put uploaded customer media in a public object-storage bucket.
-
Let drafting permission silently become publishing permission.
-
Use customer content to train a shared AI model.
-
Present an unearned certification as proof of safety.
Questions and reports
Tell a person, not a form funnel
If you have a security question or believe you found a problem, contact the support team with sensitive values removed.
support@aplora.orgStart with one channel
See whether the workflow earns your trust.
Start with 1 connected channel and core drafting and review. The included 60 credits cover about 15 post drafts, or a mix of smaller actions. Publishing depends on availability and permissions; growth intelligence and paid X messaging require a paid plan. No card required.