Wavefront
Subprocessors
Last updated:
These are the companies that process data on our behalf to run Wavefront. The list matches the “Service providers” section of our Privacy Policy, with more detail on what each one receives and when.
Our subprocessors
| Provider | Purpose | Data involved | When it’s used |
|---|---|---|---|
| Cloudflare | Hosting, database, file storage and security for the app, the API and the MCP server. | Everything Wavefront stores: account details, workspace content, encrypted connection tokens, images, and request and error logs. | Always. |
| Anthropic | AI models that plan strategies and write, check and edit drafts. | The workspace’s brief, voice and documents, the sources a draft cites, the draft itself, and parts of connected search data such as top queries and pages. Inputs are not used to train their models. | Always, whenever Wavefront plans or drafts. |
| Google (Gemini) | AI model that makes and edits images. | Image descriptions written from the draft, and the image being edited. Inputs are not used to train their models. | Whenever a draft needs a drawn image. |
| Firecrawl | Reads public web pages for research and fact checking. | Search queries written from the topic, and the addresses of public pages, including your own site. | Always, whenever Wavefront researches a draft or a strategy. |
| DataForSEO | Keyword and site-authority data about public websites. | Keywords, the target country and language, and your site’s domain. | When Wavefront researches keywords for a plan, and for site metrics. |
| Unsplash | Stock photos. | Photo search terms written from the draft. | Whenever a draft looks for a stock photo. |
| Pexels | Stock photos. | Photo search terms written from the draft. | Whenever a draft looks for a stock photo. |
| Resend | Sign-in codes and notification email. | Recipient email address and name, and the message. | Always, for sign-in codes, invitations and the notifications you set up. |
| Stripe | Payments and invoices. | Billing email, workspace name, plan, credit purchases and invoices. Stripe collects card details directly; we never see or store full card numbers. | When you start a plan or buy credits. |
| Ayrshare | Social posting. | The approved post text and images, and the social profiles you link. | Only when you link social accounts through Wavefront’s social posting. |
| X | Social posting. | The approved post text and images, and the access token for the X account you connect. | Only when you connect an X account. |
Subprocessors and the tools you connect
A subprocessor is a company we choose and pay to process data for us. We are responsible for choosing it and for the terms we agree with it.
The tools you connect are different. Your CMS (for example WordPress, Webflow or GitHub), Slack, Microsoft Teams, Google Search Console and Analytics, Google Drive, Bing Webmaster Tools, newsletter tools, project tools and webhooks are services you or your team choose and connect. Wavefront sends them the content and events you ask it to send, or reads the data you allow it to read, under the permissions you grant. Each one handles that data under its own terms with you, and you can disconnect it at any time.
How we announce changes
We update this page when we add or replace a subprocessor and change the date above. Material changes are announced by email to workspace owners before they take effect, as the Privacy Policy describes. Questions go to privacy@adwave.com.