Privacy policy

Last updated October 1, 2026

Trendwise KPI is a connector portal run by Trendwise Consulting ("Trendwise", "we", "us"). Businesses connect their own Google Ads, Google Analytics, Google Search Console and Meta (Facebook) ad accounts to it, so they can ask Claude, the AI assistant from Anthropic, to read and manage their advertising. This policy says what we collect, why, where it goes, how long we keep it and how to have it deleted. It covers the portal at kpi.trendwiseco.com and the connection Claude uses to reach it. The service is a paid subscription, so it also covers payments.

Who we are

Trendwise Consulting. Contact: marvin@trendwiseco.com.

What we collect

Your account. Your name, your email address and a one-way hash of your password (we never store the password itself). We keep a record of sign-ins, failed sign-ins and sign-outs with your email, IP address and browser details. Signing in sets a session cookie that keeps you signed in and expires after seven days without use.

Your workspace. The workspace name, the businesses (clients) you add, the team members you invite and their roles, and the mapping of ad accounts and Pages to those businesses.

Billing. Payments are handled by Stripe. When you start a trial or choose a plan, you enter your card on a page run by Stripe. We pass Stripe your email address and a workspace number, and Stripe tells us the state of your subscription. We never see or store your full card number. We store the Stripe customer and subscription ids, your plan, your billing status, the trial and renewal dates, and the date a payment first failed. Stripe keeps the payment and invoice records. We also keep a ledger of your research credits: the credits your plan adds each month, the credits you buy, and the credits each lookup uses.

Google connections. When you connect Google Ads we ask Google for permission to use Google Ads on your behalf and to see the email address of the Google login, which we use to label it. We store that email, an encrypted refresh token, and the list of Google Ads accounts the login can reach (account id, name, currency, time zone, and whether it is a manager account). When you connect Google Analytics and Search Console, we ask for read-only access. We copy Search Console and Analytics reporting rows into our database for that business: search queries, pages, clicks, impressions, landing-page and traffic-source performance, and the Analytics property or Search Console site you chose. Campaign, keyword, search-term and performance data from Google Ads is fetched from Google when you open a page, run a report or ask Claude. See "Ad campaign data" below for the few places some of it is kept.

Meta connections. When you connect Facebook we ask for these permissions: ads_read, ads_management, leads_retrieval, pages_show_list, pages_read_engagement, pages_manage_ads, pages_manage_metadata and business_management. We use them to list your business portfolios, ad accounts and Pages, read campaign and ad performance, read leads, lead forms and recent posts from your Facebook Pages, and turn on new-lead notifications for a Page you map to a business (pages_manage_metadata is used only for that). We change ads, budgets, campaign status and lead forms only when you ask: through Claude, if you have given it write access, or with the Pause, Resume, Archive and Activate buttons on the Meta ads page of the portal, which only an owner or admin can use. We store an encrypted long-lived access token, your Facebook user id and name, the business portfolios your login can reach, and the ad accounts and Pages it can reach (ids, names, status, currency, time zone). Page access tokens are requested from Meta when needed and are not stored.

Ad campaign data. Campaign, ad set, ad, keyword and performance numbers from Google Ads and Meta are fetched from the platform when you open a page, run a report or ask Claude. We do not keep a running copy of them in a database of their own, but four things keep some of it. First, a large answer to Claude is saved as a file so Claude can page through it, and that file is deleted after 24 hours. Second, when a change is made to an ad account or lead form, we save the settings as they were before the change, plus the request and its result, so the change can be undone. These undo copies hold names, statuses and budgets of the campaigns, ad sets, ads or lead forms that were changed, and they are deleted after 90 days. Third, a nightly check looks for unusual results, such as a campaign that spent money for a week with no conversions. When it finds one we keep a short note of up to 500 characters (the campaign name, the account id, amounts and dates) so the same warning is not repeated, and we record an alert for the business. These notes are kept while the workspace exists. Fourth, a weekly report, if you switch it on, is built when it is sent and emailed to the addresses you set. It is not stored.

Leads. When a Facebook Page is mapped to one of your businesses and is subscribed to new-lead notifications, each new lead from your Facebook lead forms is sent to us by Meta. We store the name, email address, phone number and other answers the person gave, plus the form, the campaign name and the time, so your business can see the lead and follow up. Your business sees stored leads through Trendwise and, when you ask, through Claude. The Meta ads page in the portal reads recent leads from Meta itself and shows them with most details hidden. This is information about the people who filled in your form, and it belongs to your business.

The Claude connection. When you approve Claude, we store the app's registration (its name and redirect addresses), the access you granted (read only, or read and write) and the businesses it may see. Codes and tokens for that connection are stored only as one-way hashes. For each request Claude makes we keep a usage record: the tool used, the time, how long it took, whether it worked, the account or business it touched, how many rows came back, and the first 200 characters of any error message.

Changes to ads. When Claude or the Meta ads page changes something in an ad account or lead form, we keep an audit entry (who, what, when, IP address and browser) and a copy of the settings before and after the change so it can be undone.

Reports and alerts. If a weekly report is switched on for a business, we email a summary of its results to the address set for it. When a new Facebook lead arrives, we also record an alert and an entry in the business's activity, and send a lead alert. The email alert goes to an address Trendwise sets in its own server configuration, so that our team can follow up, and it carries the person's name, phone number and email address. A text alert goes only to a mobile number Trendwise has set for that business, and is sent through Twilio, our text message provider. If a business has switched on a reply text and the person ticked the box agreeing to texts on the form, that person also gets one text back through Twilio. Lead alerts go to the contact the business gives Trendwise. To change where they go, or to turn them off, email us.

Market research. When you or Claude run a market research lookup, such as competitor ads or keyword data, we send what the lookup needs, for example keywords, websites, business names and places, to a third-party search data provider and pass the answer back to you. We keep a usage record of each lookup: the workspace, the business, the kind of lookup, the credits it used and the time.

Cookies and fonts. We use the session cookie and a security token that protects forms. We do not use advertising or analytics cookies. Pages load fonts from Google Fonts, so Google sees your IP address when a page loads. The payment and billing pages are run by Stripe, so Stripe's own cookie rules apply there.

Why we use it

We use your information to run the service for you: to connect your accounts, show them to you, answer Claude's requests, make the changes you ask for, send the reports you turn on, take payment, apply the limits of your plan and count your research credits, keep your workspace separate from every other workspace, provide support, and keep the service secure and working. Data we receive from Google and Meta is used only to provide these features to the customer whose account it is. We do not sell it and we do not use it for advertising. We do not use your data to train AI models.

Where it goes

  • Anthropic's Claude. Data leaves our system for Claude only through your own Claude connection, and only what a request needs. When you ask Claude a question about your ads, our server returns the relevant results to your Claude session. Anthropic handles that data under your agreement with Anthropic. We do not send your data to Anthropic on our own.
  • Google and Meta. We call the Google Ads, Google Analytics, Search Console and Meta APIs with your login to read your data and, when you ask, to change it.
  • Stripe. Stripe takes your payments and holds your card details. We send it your email address, the plan you chose and a workspace number, and it tells us your subscription status. Stripe's own privacy policy covers what it does with that information.
  • A third-party search data provider. Market research lookups are answered by a third-party search data provider. We send it only what the lookup needs, such as keywords, websites, business names and places.
  • Email and text messages. Reports, billing notices and other messages are sent by email from our own sending service. Text lead alerts, where a business has a number set, are sent through Twilio.
  • Trendwise staff. Our staff can open a workspace to give you support, and that access is logged. We look at platform data only for support you ask for, to keep the service secure, or to meet a legal duty.
  • The law. We disclose information if the law requires it.

We do not sell your information, and we do not share it with data brokers or advertising networks.

How long we keep it

  • Google Ads and Meta logins. When you disconnect a login, its stored token is deleted at once. For a Google login you can also remove Trendwise KPI's access from your Google Account permissions page (myaccount.google.com/permissions). What we keep depends on what remains. If it was the last login for that platform, the lists of ad accounts, Pages and their mapping to your businesses stay in the workspace, hidden, so that reconnecting restores them. If other logins stay connected, the accounts and Pages that only the disconnected login could reach are released from the workspace.
  • Google Analytics and Search Console. When you disconnect them, the stored login and all the reporting rows we copied are deleted at that moment. You can also remove Trendwise KPI's access from your Google Account permissions page.
  • Leads. Kept until they are deleted, or until we delete the workspace after you cancel. Email us to have them removed sooner.
  • Usage records and undo copies. Deleted automatically after 90 days.
  • Saved answers, nightly check notes and lead alerts. Saved answers to Claude are deleted after 24 hours. Nightly check notes and the alerts recorded for a business are not deleted automatically. We remove them on request.
  • Audit entries and sign-in records. We do not delete these automatically. We remove them on request where the law and security allow.
  • Billing and research records. Our billing records for your workspace (the Stripe ids, plan, status and dates) and its research credit ledger and lookup records are kept while the workspace exists. Stripe keeps its own payment and invoice records under its own policies.
  • After you cancel. You keep access to the end of the period you paid for. When your plan ends, we disconnect your Google and Meta logins and delete their stored tokens. That includes the Google login for Analytics and Search Console; the reporting rows we copied stay until the workspace is deleted. The workspace stays read only for 90 days so you can come back or download your data from the Account page. After the 90 days we delete the workspace and the data we hold for it, apart from the audit entries and sign-in records above. We keep a short note that the workspace was deleted (its name and number, how many records were removed, and when). If the workspace used its free trial, we also keep a keyed one-way hash of its owner's email address, never the address itself, so the free trial stays once per customer.
  • Your account and workspace. Kept while your subscription runs and for the 90 days after you cancel. After your plan has ended, the workspace owner can choose Delete my workspace on the Account page, and we delete the workspace 7 days later. You can also email us to have them deleted sooner.

Security

Google and Meta tokens are encrypted before they are stored, with a key that is kept in the server configuration and not in the database. Passwords, Claude codes and Claude tokens are stored as one-way hashes. The site is served over HTTPS, and session cookies are marked secure and HTTP-only. Every workspace can see only its own data. No system is perfectly secure, and we cannot promise that yours will never be breached. If you think your account is at risk, disconnect your logins and email us.

Your choices and how to delete your data

  • Download your workspace's data at any time from the Account page, with Download my data. Only the workspace owner can do this.
  • Cancel your subscription from Manage billing on the Plan page. What happens next is under "How long we keep it".
  • Disconnect a Google or Meta login on the Ad accounts page of the portal, or Analytics and Search Console on the Analytics page. Disconnect Claude on the Claude page.
  • Remove Trendwise KPI in Facebook under Settings and privacy, Settings, Business integrations. Facebook then tells us, and we disconnect that Facebook login and delete its stored token and name.
  • Remove the app's access in your Google Account, in the security settings for third-party apps and services.
  • After your plan has ended, choose Delete my workspace on the Account page. Or ask for deletion on our data deletion page, or email marvin@trendwiseco.com and we will delete your account and what we hold for your workspace. You can also ask to see or correct what we hold.

Google API Services User Data Policy

Trendwise KPI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide and improve the features you see in the portal and in Claude. We do not transfer it to others except to provide those features to you (for example, returning it to your own Claude session), to follow the law, or as part of a merger or sale of the business. We do not use it for advertising. No person reads it except with your permission, for security, or to follow the law.

Meta Platform Terms

Our use of information we receive from Meta follows the Meta Platform Terms and Developer Policies. We use it only to give the customer who connected the account the features they asked for. We do not sell it, we do not share it with data brokers, and we delete it when you disconnect or ask us to, as described above.

Children

The service is for businesses and is not meant for anyone under 18. We do not knowingly collect information from children. If you think we have, email us and we will delete it.

Changes

We will change this policy when the service changes. The date at the top shows the last update.

Contact

Trendwise Consulting, marvin@trendwiseco.com.