Thumbnail for Neuro’s ad account connection security guide, shown with a padlock, key, and security shield

Before you connect an ad account to Neuro

Check the permissions you grant, who can access account data, and when a proposed change can run.

On this page

What to check first before connecting an ad account

The moment you connect an ad account to an AI tool, advertisers and agencies tend to worry about the same things: Do we have to hand over our password? Could our data get mixed up with another advertiser’s? Can the AI change our budgets on its own? Is our data being used to train models?

We get delegated permissions, not your password

Neuro does not ask for your ad-account login password. Platforms using OAuth take you to their official sign-in and consent screen; others use dedicated ad API credentials. Check the requested permissions and account scope before connecting.

AreaThe risky wayHow Neuro does it
LoginHand your ad account password to an outside toolYou approve access yourself, in the platform’s official auth screen
PermissionsGrant broad, full-account accessConnect only the scopes the ad API requires
Revoking accessYou have to ask the vendor to cut it offDisconnect in Neuro and revoke the permission in the platform yourself

A public-facing view of the security flow

Neuro keeps the advertiser’s browser, Neuro’s security boundary, and external AI and ad platform APIs as separate pieces. Since this is a public diagram, the real internal infrastructure names and paths are left out.Tap or click to zoom and view the full screen

The model interprets the request and proposes tool calls. Neuro’s server handles account credentials and platform calls. Workspace permissions determine which connections, reports, and files a user can access.

When changes can run

In a regular chat with ad operations enabled, Neuro requests approval for changes. Automatic execution or “Approve all” for a tool changes that behavior. Scheduled operations can also run from the instructions saved in the task.

Review connection permissions and execution settings together. Keep ad operations off for analysis-only work. If you choose automatic execution, specify the targets and allowed changes, then check the results. Prompt instructions do not replace server-enforced permissions.

Does the AI train on your ad data?

Neuro doesn’t collect advertiser data to train its own AI models. The commercial AI API providers Neuro relies on publicly state that, by default, the inputs and outputs sent through their APIs aren’t used for model training. During a security review or contracting, it’s worth confirming this against their latest policy docs.

  • OpenAI states that data sent to its API Platform is not used by default to train or improve models.
  • Anthropic states that inputs and outputs from commercial products such as the Anthropic API are not used by default for model training.

Even so, each provider’s retention periods, exceptions, and custom contract terms should be reviewed against your own security policy. For enterprise security reviews especially, it’s safer to run through the DPA, sub-processors, data retention periods, and region policies with a dedicated checklist.

Frequently asked questions

Sources

Related posts