Frequently asked
honest questions.

Yes, when used as designed. Social Ninja connects to LinkedIn through OAuth and the w_member_social scope, which LinkedIn’s Posts API documentation describes as “post, comment, and like posts on behalf of an authenticated member”. Posts are created via the official Posts API under your authenticated profile, at the time you scheduled, with content you already approved.

That puts us firmly inside the productivity-tool category and away from the browser automation, scraping, and bot tooling that LinkedIn’s User Agreement prohibits in §8.2.

Most of the tools that get accounts restricted are browser extensions, scraping platforms, or bots that automate likes, comments, DMs and reshares. Social Ninja does none of that. We are a writing-and-scheduling tool that uses the official LinkedIn API and treats human approval of every post as a hard requirement, not a setting you can switch off.

Scheduling is part of our system, not LinkedIn’s. We store the time you chose and call the LinkedIn Posts API at that moment with content you already reviewed and approved. From LinkedIn’s side, it looks like a normal publish request from an authenticated app — which is how every legitimate scheduling tool operates.

No. Every post must be reviewed, edited if needed, and explicitly approved by you before it can be scheduled or published. There is no “set it and forget it” mode where AI-generated content goes live unseen. LinkedIn’s API Terms of Use (§3.1) require pre-filled content to be clearly disclosed and editable by the user; our flow goes further and makes explicit approval a hard requirement.

No. In team and agency workspaces, admins, leads, agency operators, and agency admins can draft posts, queue them in the calendar, and request approval — but the LinkedIn account owner is the only person who can approve and publish to their own profile. There is no admin override, no impersonation, and no shared identity.

When the scheduler fires, the publish call runs against the owner’s own LinkedIn access token, on the owner’s authenticated session, with content the owner personally reviewed and approved. Members can revoke approval before publish at any time.

The role split is: admins and agencies own strategy, drafts, and scheduling — members own approval and publication. We enforce this at the API layer, not as a setting an admin can toggle.

Yes — provided you review and approve before sharing. LinkedIn’s User Agreement and API Terms put the responsibility for what gets published on you, the author. Our entire flow — draft, edit, score, approve, schedule — is built around that expectation. We make it easy to make sure you actually mean every word.

No. Your content stays your content. We send your prompts to large-language-model providers (Anthropic, OpenAI) under their commercial-API terms, which exclude API traffic from training by default. We do not pool your writing into a shared model. See the privacy policy for sub-processor detail.

Not by default. The content posts under your profile, in your voice, because you wrote (or curated) the version that publishes. We mark AI-assisted drafts internally for governance and quality scoring, but we don’t append disclaimers to your published posts. You’re the author either way.

No, and we wouldn’t accept it if you offered. Connection happens through LinkedIn’s OAuth flow — you log into LinkedIn, you authorise Social Ninja, and we store an access token. We never see your password, and you can revoke our access from your LinkedIn settings at any time.

From inside Social Ninja, click the unplug icon on the LinkedIn integration card on your dashboard — that deletes our access token. From LinkedIn’s side, go to Me → Settings & Privacy → Data privacy → Permitted services and revoke Social Ninja. Either route works. Any scheduled posts that fall after the disconnect will fail at publish time with a clear “reconnect required” error rather than going through silently — reconnect or delete them.

Account, content, and metadata live in an EU-hosted backend database (eu-west-1). Backups and logs are retained for up to thirty days. Full detail — including a current named sub-processor list — is in the privacy policy.

Yes. You can delete most of your content from inside the app. To delete your entire account, email privacy@getsocial.ninja. We process deletion within thirty days and remove residual backups on rotation.

We surface the failure in your calendar with the LinkedIn error code, leave the post in a failed state, and give you a one-click retry. We never silently retry with altered content. The most common cause is a token that needs reauthorising, which we walk you through.

Yes. We rate-limit publish attempts so the tool can’t be used to spray content in a way that would look spam-like to LinkedIn. The limits sit comfortably above what a healthy daily-presence cadence requires.

Yes — until it publishes. You can edit, reschedule, or cancel any draft right up to the moment our scheduler hands it to LinkedIn. After that, the post lives on LinkedIn and you edit it there.