Privacy policy
Last updated 28 September 2026
AdsAI is an internal tool operated by Brand Wisdom Solutions (“BWS”, “we”), India. It helps BWS staff review Google Ads search terms for the advertisers BWS manages and prepare negative-keyword recommendations. This policy explains what AdsAI stores, why, who can see it, how long it is kept and how to ask for it to be deleted.
Who can use AdsAI
Only BWS staff on the AdsAI staff list can sign in. An administrator adds each person and sends them a one-time invite link. Staff have one of three roles: administrators manage staff, accounts and the Google connection; managers review and export recommendations; viewers can only read. AdsAI has no public accounts.
BWS can also give its own software assistants a key to AdsAI. Each key belongs to a named entry on the staff list. It can read what a viewer can read and the record of actions, and add notes to that record; it cannot approve, change or export anything. Every use of a key is recorded.
Staff account data
- Name, work email address and role.
- A password, stored only as a secure hash by the sign-in system.
- Sign-in sessions, which end after 7 days without use. The sign-in system can store, with each session, the IP address and the browser description (user agent) it came from. Session records can stay in the database after the session has ended.
- When each person last signed in, and failed sign-in attempts (the email entered and the reason, never the password).
- A record of each action a person takes in AdsAI, such as approving a recommendation, creating an export or changing a setting.
We use this data to decide who may use AdsAI, to keep sessions secure and to keep an accountable record of every decision.
Google Ads reporting data
For the client accounts BWS manages and a staff member has switched on, AdsAI stores:
- Account identifiers: customer ID, account name, currency and time zone.
- Campaign and ad group names and identifiers.
- Search terms with their impressions, clicks, cost, conversions and conversion value for a date range, and the keyword that triggered each one.
- The account's keywords and negative keywords. A suggestion that would block an active keyword is flagged for staff, and existing negatives are not suggested again.
- A business profile that staff write for each account (what the business sells, locations served, brand and competitor terms, target cost per acquisition).
- The recommendations AdsAI prepares, the decision staff made on each, and the export files created from them.
- Account groups that staff set up (a name and a short description) and which accounts are in each.
- Alert rules that staff set up, and the alerts AdsAI raises when an account's figures cross one: the figure and the threshold, the report window, the campaign name for a rule that looks at campaigns, and how the alert closed. Staff can snooze an alert (AdsAI keeps who snoozed it and until when), give it to a member of staff (who, by whom and when) and mute a rule for one account (which rule, which account, who muted or unmuted it and when). Alerts are worked out from the data above; they never change anything in Google Ads.
- Portfolio reports, made every week and when staff ask for one: for each switched-on account, its group, its latest report window's spend, conversions and spend on searches that never converted, the waste waiting for a decision, the review backlog, approved suggestions not yet exported and its live alerts. They are kept inside AdsAI and are not emailed or sent anywhere.
- The report files staff upload, as described under “How long we keep it”.
This data comes from a search terms report that staff download from Google Ads and import, or, once the Google connection is verified and switched on, from read-only requests to the Google Ads API. It is used only to find wasted spend, prepare negative-keyword recommendations and raise the alerts described above for that advertiser.
Google authorization
An administrator can connect one Google account that has access to BWS's Google Ads manager account. AdsAI asks Google only for the Google Ads permission. Connecting Google is separate from staff sign-in: staff do not sign in to AdsAI with Google.
- AdsAI stores a record of the connection: its label, the email address an administrator records for the connected Google login, the manager account's customer ID, who connected it and when, and the last error, if any.
- The refresh token Google returns is encrypted (AES-256-GCM) before it is stored and is only decrypted inside server-side jobs. It is never sent to a browser.
- AdsAI uses it only to read account structure and reporting data. It does not change campaigns, bids, budgets, ads or keywords.
- Disconnecting in AdsAI asks Google to revoke the token and deletes the stored copy, even if Google does not confirm the revocation. You can also remove AdsAI's access from your Google account settings at any time.
AdsAI's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data, use it for advertising, or share it beyond the providers listed below.
Optional AI review
AdsAI contains an optional step that asks an AI model (Anthropic's Claude) to classify search terms. It is off by default and runs only when BWS switches it on for the AdsAI deployment. When it runs, AdsAI sends selected search terms, their performance metrics and advertiser context (such as the business profile and triggering keywords) to Anthropic to suggest negative keywords for that advertiser. Staff review every suggestion before export, whether it came from the rules or the AI review.
Free waste audit
Anyone can use the free waste audit at /waste-audit without signing in. The search terms report you choose is read by your browser. It is not uploaded to AdsAI, and AdsAI does not store it or the audit.
The audit has an optional AI explanation. It runs only when BWS has switched it on and you tick its box. Your browser then sends the top suggested negative keywords, up to five example searches for each, the brand names you typed and the line you wrote about your business to AdsAI's server, which passes them to Anthropic (Claude) and returns the explanation. Long numbers and email addresses are hidden before sending. No amounts, campaign names or the file itself are sent. AdsAI does not store what is sent or returned.
To limit use of the AI explanation, AdsAI keeps counters keyed by a one-way code made from your IP address, never the address itself. They are deleted within a day. A monthly spending total that names no visitor is deleted when the month ends.
Where the data is kept
- Convex runs AdsAI's database, server functions and file storage.
- Vercel serves the web pages.
- Google, as the source of the reporting data and of the authorization described above.
- Anthropic, only while the optional AI review is switched on.
AdsAI does not make its own backup copies. These providers keep operational logs and backups under their own policies.
How long we keep it
AdsAI deletes very little automatically. What happens to each kind of data:
- Search terms from an account's latest report stay in the database for as long as that report is the account's latest data.
- Search terms from older reports move out of the database at the first nightly clean-up after the report is no longer the account's latest and was imported at least 30 days earlier, or after its report window ended more than 13 months earlier. They move into an archive file in AdsAI's storage, and archive files are kept; they are not deleted automatically.
- Uploaded report files are deleted when their rows move to an archive file, as above. An upload refused before its import starts (a file identical to one already imported, a file over 50 MB, or another import for the account still running) is deleted at once. An import that fails before storing any rows (for example, the file is not a search terms report, or its totals do not add up) keeps its upload until the first nightly clean-up at least 30 days later. An import that fails after it has started storing rows, or never finishes, has those rows moved to an archive file, and its upload and that file are kept so the failure can be diagnosed; they are not deleted automatically. A file that finished uploading but was never submitted for import (for example, the page was closed first) stays in storage; it is not deleted automatically. A file submitted for import whose import never started is deleted by the first nightly clean-up a day later.
- Recommendations and staff decisions, including rejected and expired recommendations, are kept for as long as AdsAI is in use. A recommendation can include the text of a search term.
- Export files are kept in storage so they can be downloaded again. They are not deleted automatically.
- Alert rules and alerts are kept for as long as AdsAI is in use. A rule that is no longer wanted is archived, not deleted, and an alert that has cleared stays as the record of what was flagged. A muted rule that is unmuted keeps its record. On a deletion request, an advertiser's alerts and rule mutes are deleted with the rest of their data, and so are rules that cover only their account.
- Portfolio reports are kept for as long as AdsAI is in use. They are not deleted automatically; an advertiser's rows are removed from them on a deletion request.
- Keyword lists, business profiles and account settings are kept for as long as the account is in AdsAI. Switching an account off does not delete them.
- Staff records are kept when someone is deactivated, so their past decisions stay attributed to them.
- The record of actions is kept for as long as AdsAI is in use, and entries are never deleted. The one change ever made to it is for an advertiser's deletion request: an administrator switches the advertiser's account off and removes their details from its entries and from any Google connection entry that carries the account's customer ID, which keep who acted, the kind of action and when. AdsAI checks again until no entry is left, and records the removal and its result. While the account stays switched off, AdsAI's automatic jobs add only housekeeping entries about it, such as rows archived on schedule, which do not name it or its files. Entries about staff are kept as the record of who made each decision.
- The Google refresh token is deleted when the connection is removed; the connection record described above is kept. Temporary state used while connecting Google is deleted by a nightly clean-up once it is a day old.
- AI review results, if the optional AI review has been used, are kept with the account's data. So is the request file listing the search terms sent for each review, which is kept in storage and not deleted automatically.
Your choices and requests
To ask what AdsAI holds about you or an advertiser, to correct it, or to ask for it to be deleted, email brandwisdom01@gmail.com. AdsAI has no self-service deletion: BWS staff carry out deletion requests by hand within 30 days of the request, including archive, uploaded and AI review request files and, for an advertiser, their details in the record of actions, and reply when it is done. Advertisers can also ask their BWS account manager to switch their account off in AdsAI, which stops its syncs, imports and waste searches and removes it from review.
Changes
We update this policy when AdsAI changes how it handles data, and change the date at the top. See also the terms of use.