How We Protect Your Data

When you connect Google Ads, Google grants access through its standard Google Ads API permission; Google does not offer a narrower read-only version of that permission. What matters is what we do with it: every current Ad Prophet feature reads and analyzes your data. Our analysis does not create, change, pause, or delete anything in your account, and any account-change feature requires your approval before a change is sent.

Meta coverage is in progress. The Meta connection asks for three permissions, including write-capable ones whose account-changing features are switched off in Ad Prophet today. The exact permissions are disclosed on the How It Works page.

You can disconnect Ad Prophet at any time through your Ad Prophet settings or directly in your Google or Meta account permissions. Disconnecting stops any further reading right away.

Sign-in and organization access run on Clerk, a dedicated managed authentication provider. Requests for organization data are authorized on the server: the active organization comes from your session's verified claims, not from arbitrary client input, and a request for another organization's data is rejected. Ad Prophet staff can access workspaces for support and operations.

Application data is handled by Convex, our backend platform. Advertising performance data is stored and processed in Google Cloud BigQuery. Each organization's advertising data lives in its own datasets, named from that organization's identity. One client's data never shares a dataset with another's.

Ad platform access tokens are encrypted at rest with AES-256-GCM and cryptographically bound to the organization and platform they belong to, so a stored token cannot be decrypted under another organization's identity.

Cloud credentials stay server-side. The browser never receives a Google Cloud credential. BigQuery access uses short-lived tokens generated on demand, no per-organization cloud keys are stored, and service secrets live in backend environment configuration, not in client code.

All traffic to adprophet.ai and between our services and providers uses TLS. Our infrastructure providers encrypt stored data at rest as a platform default, and ad platform tokens carry the additional application-layer encryption described above.

We use a small set of infrastructure providers: Google Cloud (including BigQuery) for data storage, processing, and reporting; Convex for backend data handling; Clerk for authentication and organization access; Vercel for hosting and delivery; and Fivetran as a managed data pipeline for some account connections. AI service providers may process data to generate analysis. What each provider receives is detailed in our Privacy Policy.

We use your advertising data only to produce your audit, forecast, and growth plan and to support you. We do not sell it, we do not use it for advertising, and we do not use it to train general-purpose models.

Disconnecting an account stops further reading immediately. You can also ask us to delete the data we already hold; the Data Deletion page lists the exact steps.

Ad Prophet does not currently hold SOC 2 or ISO 27001 certification, and we would rather say that plainly than imply otherwise. If your review process needs a vendor security questionnaire completed, email us and we will answer it directly.

For security questions, vendor reviews, or to report a vulnerability, email west@adprophet.ai. Ad Prophet AI is operated by Four19, LLC.