Account safety, and what we cannot promise

Can you get banned for using automation?

It can happen, and anyone who tells you otherwise is guessing with your page. Platforms do restrict automated behaviour, the rules move, and browser session posting sits in a grey area that no vendor can declare safe on your behalf.

What we can tell you is how our posting behaves, which is the part that is actually in our control. The pattern platforms react to is volume, speed and engagement: many actions, fired fast, with a machine cadence, especially replying, liking and following. Our design goal is to be boring on every one of those axes.

Will this get my page banned?

No tool can promise that it will not, and anyone who does is guessing. What we can do is be slow and capped, and tell you exactly how each post is delivered.

Volume is capped per page per day, timing is varied rather than landing on the same second, and one posting session runs per machine so two processes never fight over the same page. We do not automate comments, DMs, follows or likes at all, because that is where account restrictions usually start. There is no approval step in front of each post, so the controls that matter are the ones below, and they run whether or not you are watching.

What controls actually sit around a post?

Seven, and they run for every single post. None of them is optional or configurable away.

1. Spend limits: every paid outside service has a daily cap on requests and records, and a call over budget, or one with no budget at all, is refused and logged.
2. Rate caps: posting is capped per page per day, so a page cannot burst.
3. Jitter: the send time is varied around the schedule instead of landing on the same second every day.
4. Text limits: every format declares its text limits, and a post that breaks them is parked for a person instead of posting.
5. Route stated per platform: each platform page says how a post is actually delivered there, so you never have to guess whether it is an API or your own session.
6. One worker per machine: a posting session is a singleton, enforced by a lockfile, so two processes never fight over the same page and produce half a post.
7. No engagement automation at all: no comment replies, no DMs, no likes, no follows, ever, because that is where restriction stories usually start.

On top of those, you hold two switches: you can pause any scheduled job, and you can press Run now to start a run straight away.

What worries people most?

The same three questions come up before anyone joins, so here they are without hedging.

Will I get my page banned? Nobody can promise immunity. We cap the volume per page, vary the timing, cap the spend, and never touch comments or DMs.

Is this just AI slop? Each post is written fresh from today’s story and rendered into a format with declared text limits, and thin candidates are dropped rather than padded out. The flow is on how it works.

Why not a scheduler, or a workflow builder? A scheduler posts what you already decided and a workflow builder needs you to maintain the wiring. Content OS finds the story, writes it, renders it and posts it, which is the part the other two leave with you. The longer answer is in is social media automation worth it.

Will it post from my account or from some shared account?

Always your page, acting as your page. Nothing is routed through a shared, pooled or third party account.

You sign in yourself, in your own browser, and we never ask you to hand over credentials for us to store. If you change your password, you sign in again and nothing on our side needs to know what it was. Facebook, Instagram, TikTok, X, YouTube, LinkedIn and Snapchat publish today, and what that looks like per platform is on the platform pages, starting with the Facebook page and the Instagram page.

What do you log, and what can I audit?

Every run and every outside call: each run writes a run log with its status and how long it took, and every call it makes to an outside service is logged too. The admin console shows both, and that log is the audit surface today.

You can see when a run happened, whether it worked, and what it reached out to. A per post decision record, showing which story won, what it beat and why, is designed and not built yet, so we do not claim it here. The flow behind each run is on how it works.

What will you never do?

Engagement automation of any kind. No comment bots, no mass DMs, no follow or unfollow cycles, no fake accounts, no pods, no purchased interaction.

This is not a roadmap gap we are working through. It is a boundary, because those behaviours are both the fastest route to a restricted account and the thing that makes automated pages feel like automated pages. We also do not accept a page we would have to run through pooled or borrowed accounts, whatever the reason.

What does it not do yet?

Performance learning is the big one: the engine is designed to weigh how a post performed, but that data is not being collected, so today each run picks its story from trends and available material only. The full planner, its scoring formula and a per post decision log are designed, not built yet.

There is also no approval step, no analytics dashboard, no comment or DM handling, and no client login. We sell software only and we keep the gaps written down.

What can you not promise?

That your account is safe. We will not use the words ban proof, fully compliant or platform approved, on this page or anywhere else.

We also hold no official API certification on any platform today, so we cannot point at a certification as cover. What exists is a set of deliberately slow, deliberately capped controls, described plainly enough that you can decide for yourself whether the risk is one you want. The current publishing routes are on platforms, and the direct answers to the ban questions people actually ask are on the FAQ.