TikTok Ads is coming to Adrails

Security

Security boundaries for connected advertising data

Adrails connects systems that contain campaign and business data. The security model limits provider permissions, encrypts stored credentials, verifies callbacks and checks every ad-account write against the live state before it runs.

01

Provider access is scoped to the connector

Each connector declares the capabilities and permissions it uses. Read-only connectors do not receive an application write path merely because another provider supports writes.

OAuth callbacks and incoming provider webhooks are validated before data is accepted. API keys are checked against the provider before a connection becomes active.

02

Credentials are not agent context

Stored provider credentials are encrypted and resolved only for the server-side connector that needs them. They are not included in agent prompts, activity copy or browser responses.

Logs and connection errors are designed to describe the failure without returning tokens or authorization codes.

03

Account writes are scoped and checked

Every change names its target and values. Only owners and administrators apply changes to an ad account, Adrails reads the live state again before writing, and a single budget change is capped at 30%.

Disconnecting a provider removes its stored credential and stops future provider calls. Data deletion requests are handled through the published deletion process and privacy policy.

Common questions

Are provider credentials sent to AI models?

No. Credentials are resolved server-side for connectors and are not added to agent prompts.

What happens when an integration is disconnected?

The stored credential is removed and Adrails stops calling the provider until a new connection is authorized.