Privacy Policy

Google Ads is a separate, optional connection with its own Google consent, apart from Analytics and Search Console. Google offers one permission for the Google Ads API (adwords), which allows both reading and changing an account, so Crescade asks for that permission and your Google account email. Only a workspace owner or admin can connect it.

What Crescade reads. The list of Google Ads accounts you can open, so you can choose which ones Crescade may use. For the accounts you choose: account settings such as currency and time zone, conversion actions, campaigns, ad groups, keywords, search terms, ads and assets, with their spend, clicks, impressions and conversions, and the review status of ads Crescade created. The ads audit reads the last 30 days and checks your ads' landing pages on the public web.

What Crescade changes, and only after you approve. When you build a Google Search campaign in Crescade, Crescade first asks Google to check the exact request without creating anything. After a workspace owner or admin approves it, Crescade creates the campaign's budget, campaign, ad groups, keywords and ads in your account, all paused, and reads them back to compare them with what was approved. Nothing runs until an owner or admin gives a second, separate approval to turn the campaign on. An owner or admin can also remove a campaign Crescade created that is not running. Crescade does not change campaigns, ads or settings it did not create.

Spend limits. Every campaign has the daily budget and total cap you set when you draft it, and Crescade also applies a limit per workspace. About every six hours Crescade reads each campaign's spend and pauses it when spend reaches its total cap. Google can spend up to twice the daily budget on a single day, so spend can pass the total cap slightly before the pause. Ad costs are billed by Google to your Google Ads account. Anyone who works in your workspace can pause one or all Crescade campaigns at any time; pausing never waits for an approval.

What Crescade stores. The connected account email and the accounts you chose, the campaign drafts and what each approval covered, who approved each step and when, saved audit reports, and a log of every request sent to Google Ads with a fingerprint of each answer. Access and refresh tokens are encrypted at rest. Data read from your Google Ads account is not sent to AI providers.

Disconnecting. Use Disconnect on the Ads page. Crescade removes its stored usable tokens and asks Google to revoke the grant; you can also remove Crescade access in your Google Account. Disconnecting does not remove campaigns already in your account. Before it disconnects, Crescade pauses every running campaign it created, because afterwards it can no longer check their spend or pause them. If one does not pause, Crescade keeps the connection and asks you to pause it, in Crescade or in Google Ads, before you disconnect. Saved audit reports and campaign records stay in your workspace until you ask us to delete them or delete your account.

Crescade's use of information received from the Google Ads API also adheres to the Google API Services User Data Policy, including its Limited Use requirements.

With your approval, Crescade publishes to the sites and social accounts you connect. A post is published only after a workspace owner or admin approves it, at once or at the time they schedule, only when publishing is switched on for your workspace, and only to the destination you chose. After publishing, Crescade reads the post back and keeps a receipt with its address, what was sent and who approved it.

• WordPress with the Crescade plugin. Crescade reads published posts and pages with their SEO fields, links, images, and site details such as the WordPress version, theme and plugins. It writes only if the site admin ticks “Let Crescade apply changes I approve” in the plugin: then it creates or updates the approved post with its categories, tags and featured image, and sets the SEO title and description in your SEO plugin. Undo sets the post back to a draft or moves it to the trash.
• WordPress with an Application Password. Crescade uses the WordPress REST API with that user's rights to create or update the approved post, its categories and tags, and to upload its featured image to the media library.
• Webflow. Crescade reads your sites, pages and CMS collections. It adds or updates the approved post as one CMS item and publishes that item, never the whole site. Undo takes the live item down.
• Ghost. With the Admin API key you paste, Crescade creates or updates the approved post. Undo sets it back to a draft; Crescade never deletes Ghost posts.
• LinkedIn. Each workspace owner or admin connects their own LinkedIn profile; Crescade asks for your name, email address and member ID to show which account is connected and to name you as the posts' author, and for permission to post on your behalf (w_member_social). After you approve a post, Crescade publishes it to your own profile, uploading the one image it carries if it has one, and tries to read the post back to check it; if LinkedIn does not allow that, the receipt says the post was not checked. Undo deletes the post. Crescade does not post to company pages, and does not read your feed, like, comment or post anything you did not approve.
• X. Each workspace owner or admin connects their own X account; Crescade reads your account's name and handle. After you approve a post or thread, Crescade publishes it from your account, with the one image it carries if it has one, and reads the posts back to check them. If an answer from X is lost, Crescade looks at your last five posts before trying again so nothing is posted twice. Undo deletes the posts. Crescade does not like, repost, follow or send messages. X charges Crescade's X developer account for each post and each read on its pay-per-use price list; Crescade shows the estimated cost before you approve and counts it toward its spending limits for X posts.

Credentials for these connections are encrypted at rest. To disconnect, use Disconnect under Connections. You can also deactivate the Crescade plugin or revoke the Application Password in WordPress, remove Crescade's app in Webflow, delete the custom integration in Ghost Admin, remove Crescade under Settings → Data privacy → Permitted services in LinkedIn, or revoke Crescade under Settings → Security and account access → Apps and sessions → Connected apps in X. Disconnecting X also asks X to revoke Crescade's access; LinkedIn offers no way for an app to do that, so remove it in LinkedIn as well. Posts already published stay on your site or profile; disconnecting does not delete them.