AI use policy
Effective August 2026 · Last updated August 2026
Every marketing company uses AI now, and almost none of them will tell you where. This page tells you where we use it, where we refuse to, and what happens to your data. It supplements the privacy policy and the terms of service.
1. The assistant on this site
The chat assistant in the corner of every page is software, not a person, and it says so before you type anything. It runs on Cloudflare Workers AI, server side, and answers only from what is published on this site. It cannot quote you a price that is not on the pricing page, cannot agree to anything on our behalf, and nothing it says is a quote, a contract, or a promise of a result. It can still be wrong. When something matters, ask a person.
Your messages go to Cloudflare for inference and are not stored by us beyond what is needed to show you the conversation in your own browser. If you would rather not use it at all, do not open it, or email contact@currentads.net and a person will answer.
2. Where we use AI in client work
As a tool that a senior operator drives, and never as the operator. Specifically: research and competitive scanning, first drafts of ad copy and content, bulk classification work like sorting search terms or tagging creative, summarising large volumes of campaign data, code and schema generation for tracking and technical work, and image or video generation where a client has asked for it and the use is disclosed.
A human reviews everything before it reaches you, before it goes live, and before it is reported as a result. The published pricing buys senior operator time; using a model to make that time go further is not the same as replacing it with one, and if it ever became the same we would be charging you for something you are not getting.
3. Your data is not training data
We do not put your customer lists, CRM records, call recordings, or any personal data belonging to your customers into a third-party AI tool for the purpose of training a model, and we do not permit our contractors to.
The assistant on this site runs on Cloudflare Workers AI, whose published data policy states: “Cloudflare does not use your Customer Content to (1) train any AI models made available on Workers AI or (2) improve any Cloudflare or third-party services, and would not do so unless we received your explicit consent.” You do not have to take our word for that one, which is the point — it is published by Cloudflare, not by us.
Where an engagement needs a tool whose terms are weaker than that, we tell you which tool, what it would touch, and why, and you decide. Silence is not consent and we will not treat it as consent.
4. What we will not do with AI
- Generate reviews, testimonials, or endorsements. Not for us, not for you. A fabricated endorsement is illegal under the FTC’s rule on consumer reviews regardless of who typed it, and we will decline the work.
- Present an AI-generated person as a real customer, employee, or spokesperson. Synthetic people in creative get labelled as synthetic.
- Make or materially influence a decision about a specific person — who gets hired, who gets credit, who gets a price — on your behalf. That is a different category of regulated activity with its own obligations, and it is not what a marketing engagement is.
- Let a model send email, publish content, or spend budget without a human approving it first.
- Claim an AI capability we do not have today. If we say a system does something, it does it now, not in the next release.
5. Disclosure in the work we produce
Advertising platforms have their own rules about synthetic and altered media, particularly for people, political content, and regulated categories, and those rules change. We follow the platform rule that applies to your campaign and we tell you when a deliverable contains AI-generated imagery or video, so that you can make your own disclosure decision as the advertiser. You are the advertiser of record; the final call about what goes out under your name is yours.
6. Subprocessors
Every third party that can touch personal data flowing through currentads.net or an engagement. Tools that sit inside your own accounts — your Google Ads, your GA4, your CRM — are yours and governed by your agreements with those platforms, not ours.
| Subprocessor | Purpose | Data | Region |
|---|---|---|---|
| Cloudflare | Hosting, CDN, security, database (D1), email routing, and Workers AI inference for the site assistant | Site traffic, security logs, form submissions, portal data, assistant messages | United States (global edge) |
| Google Workspace | Business email, calendar invites, and Google Meet video calls | Email correspondence, calendar and meeting details | United States |
| Cal.com | Call scheduling on the booking page | Name, email, and anything entered into the booking form | United States / EU |
| Brevo | Transactional and opt-in marketing email | Name, email, send and engagement events, unsubscribe records | European Union |
| Stripe | Payment processing, when billing is active | Billing contact and card details, entered directly with Stripe | United States |
We will tell clients before adding a subprocessor that would handle their data. If you need this list under a data processing agreement, our DPA is published in full and applies to every engagement.
7. Questions and complaints
If you think an AI system of ours got something wrong about you, or you want to know whether AI touched a specific deliverable, ask and we will tell you plainly: contact@currentads.net. Your rights over your personal information are in the privacy policy.
CurrentAds · Tennessee, United States · contact@currentads.net