SECURITY + DATAWhat we hold. How we hold it. What it may never do.
Specific controls beat vague badges. Here is the access Scalix needs, the processors involved, and the limits around every automatic action.
1 keyper organization
RLSdatabase-enforced isolation
1 tapto undo supported actions
0training use or data sales
01What we receive
Selected ad accounts, campaigns, ad sets, ads, performance, Pages, Instagram professional accounts, comments and messages, author names and profile identifiers, and access tokens. Google sign-in provides name, email, and profile picture only.
02What we do with it
Run the automation you configure, answer supported customer questions, produce reports, and show an action history. We do not sell it, use it to train models, or use it beyond the configured service.
03Who processes it
Hostinger International Ltd., Cloudflare, Inc., Deepgram, OpenRouter, and Google's image model process limited data on our behalf. The language model sees your words and rule names—not customer messages—and does not make the spending decision.
04What it may never do
Act on stale data, convert currency, restart a kill-switch stop, save a rule without confirmation, or promise a customer money. Budget reductions require explicit permission; configured timed resets are the documented exception.
05Retention and deletion
Performance data is retained while active and for 90 days afterward; comments and messages for 12 months. Tokens are removed immediately when disconnected. A verified full-deletion request is completed within 30 days.
06Public-authority requests
We review any valid request, disclose only what the law requires, and notify the customer unless prohibited. As of 24 September 2026, we have received no such request.