LaunchPilot Security: Access, Approvals and Spending Limits

Access

You connect with Google's own sign-in. LaunchPilot never sees your Google password.
It asks for one permission: managing Google Ads. It uses that only for the ad account you choose.
The access token is encrypted with AES-256-GCM before it is stored, and it is never shown back to you or sent to the browser.
Disconnecting deletes the token and revokes the access at Google. You can also remove it any time in your Google account's security settings.

Every change to Google Ads goes through one approval check in the code. An approval is a fingerprint of one exact change, and it works once.
When you send a draft, the button carries the fingerprint of the version you reviewed. If anything changed since, the send is refused.
Right before writing, LaunchPilot runs its checks again and asks Google to validate the whole campaign. If any part fails, Google saves none of it.
Campaigns are created paused. Turning one on needs a separate confirmation, and LaunchPilot first checks the campaign is still paused in Google Ads and still within your limits.

You set a top daily budget and a top cost per click. Drafts over them can't be sent.
LaunchPilot never raises a budget or bid. It doesn't touch billing or payment settings.
Pausing is always available, on every plan, so you can always stop spending.

The assistant suggests ad text from what you type. It has no access to your Google Ads account, and the code that runs it can't reach Google Ads or approve anything.
Its suggestions face the same checks as your own text, so it can't add discounts, guarantees or delivery promises you didn't enter.

The Activity page lists every attempt to change your account, allowed or refused, with Google's response.
A daily email shows yesterday's spend for each campaign LaunchPilot made. You can turn it off.

Questions or a security concern? Contact NexPoint Studio. Read our privacy policy.