We never hold a password
Your accounts are connected through each platform's own authorization page. We never ask for a password, never store one, and never log in with a browser pretending to be you.
What protects your account, your code and your money
Every promise on this page is a line of code you can hold us to, not a badge.
Access tokens are encrypted where they sit
Tokens are stored with AES-256-GCM and the key lives outside the database. No token is ever written to a log, and the key can be rotated without you reconnecting anything.
Your code is read once and then deleted
The repository is processed in a single-use, isolated container; secrets are stripped before anything reaches a model. Only the brief we derive is kept. Your code and your data never train a model.
Nothing can be published without passing review
The compliance review is not a step the code can skip: the database itself refuses to record a post whose content is not approved. A bug in our software cannot get around it.
Ad spend has a brake that cannot be lost
Spend is read from two independent sources every fifteen minutes. Over the cap, the campaign is paused at the provider first and written down second, and pausing keeps working even when billing itself has stopped.
You can leave with everything
Export your data in one click. Delete a project or the whole account in one click: that cancels the subscription, pauses live campaigns, removes stored media and model traces, and sweeps again hours later for anything that arrived late.
What we do not have
We are not SOC 2 or ISO 27001 certified. We are a small team and we will not claim an audit we have not had. What we can show you is above, and the code behind it.