Google API Services Disclosure

This page is a focused disclosure of how Clevertrek uses data obtained from Google APIs ("Google User Data"). It complements, and should be read together with, the Privacy Policy (in particular Section 11) and the Terms of Service. The texts on scopes, Limited Use, AI features, service providers, security, retention and revocation are the same, word for word, in both documents.

This page is designed to be self-contained for the purposes of the Google API Services verification process: any reviewer can read it on its own to assess our scopes, our use of Google User Data, our compliance with the Limited Use requirements, our retention practices, and how users can revoke access.

Clevertrek is operated by Fernando Beneitez Vela-Hidalgo, a sole proprietor under Spanish law, holder of NIF 75794423Q, with registered address at Avenida del Hotel, 1, 15º, 08860 Castelldefels, Barcelona, Spain.

1. Application Identity

• Application name (as shown on the OAuth consent screen): Clevertrek
• Operator: Fernando Beneitez Vela-Hidalgo (sole proprietor, NIF 75794423Q)
• Verified domain: clevertrek.com (the homepage, Privacy Policy URL and Terms of Service URL configured on the OAuth consent screen are on this domain)
• Privacy Policy: Privacy Policy
• Terms of Service: Terms of Service
• Support contact: support@clevertrek.com
• Privacy contact: privacy@clevertrek.com
• Security contact: security@clevertrek.com

2. Google APIs and OAuth Scopes Requested

Clevertrek requests only the following Google APIs and OAuth scopes, and only to the extent necessary to provide the user-facing features described below.

Clevertrek does not request the broad drive or drive.readonly scopes, the spreadsheets or spreadsheets.readonly scopes, the read-write webmasters, analytics or analytics.edit scopes, any Gmail or Google Calendar scope, or any scope that Google classifies as Restricted, and it does not request scopes it does not actively use. If new scopes are added, this document and the OAuth consent screen will be updated first, and any new Sensitive or Restricted scope will go through Google's verification before it is used in production.

Why each scope is needed, and why a narrower one is not enough:

3. How Each Scope Is Used

3.1 Google Sign-In (openid, profile, email)

Used to:

• create or look up a Clevertrek Account;
• authenticate the user on subsequent logins;
• display the user's name and avatar inside the Service.

No further use. This data is not used for advertising, profiling, or AI-model training.

3.2 Google Search Console (webmasters.readonly)

Used to show, inside the user's own Workspace, the search performance of the properties that the user has verified in Search Console: SEO Controller (with its reports and insights), Live Dashboards, Rank Tracker, Keyword Research, Content Ideas (reading the user's top pages when the user starts it), Persona Studio, Ideation, Talk to Report and the AI assistant of the user's projects, including the scheduled automations that the user sets up.

Specific operations performed:

• list the user's verified Search Console properties (sites.list);
• query search performance metrics (clicks, impressions, CTR, position) by query, page, country, device, and date (searchanalytics.query).

Read-only. Clevertrek does not use any write/modify endpoint of the Search Console API.

3.3 Google Analytics Data API and Admin API — GA4 (analytics.readonly)

Used to show, inside the user's own Workspace, traffic and engagement information for the GA4 properties that the user's Google account has access to, in the Google Analytics connector, Live Dashboards, Persona Studio and the AI assistant of the user's projects.

Specific operations performed:

• list the GA4 accounts and properties accessible by the user's Google account (accountSummaries, Admin API);
• query GA4 reports through the Google Analytics Data API (runReport, runRealtimeReport and getMetadata) for the dimensions, metrics and date ranges chosen by the user;
• display the results as charts and tables inside the user's authenticated Workspace.

Read-only. Clevertrek never requests the broader analytics or analytics.edit scopes, does not call write, configuration or user-management endpoints, and does not modify GA4 configurations. It does not access Universal Analytics data.

3.4 Google Ads API (adwords)

Used to show, inside the user's own Workspace, advertising performance information for the Google Ads accounts that the user's Google account already has access to, in the Google Ads connector, the Google Ads Controller, Live Dashboards and the AI assistant of the user's projects.

Specific operations performed:

• list the Google Ads accounts accessible by the user's Google account (customers:listAccessibleCustomers, and a GoogleAdsService.Search query on the customer_client resource);
• read reporting data with read-only GAQL queries through GoogleAdsService.Search (googleAds:search), mainly on the resources campaign, ad_group, ad_group_ad (ads), keyword_view (keywords and match types) and search_term_view (search terms); when the user asks the AI assistant a question that needs another report, the assistant can run another read-only GAQL query of the same kind;
• read the catalogue of available report fields (GoogleAdsFieldService, googleAdsFields:search), which contains no account data, so that the user can choose the columns of a dashboard;
• retrieve standard reporting metrics such as impressions, clicks, cost, conversions, all conversions, conversion value, CTR, average CPC and cost per conversion;
• display the results as cards, tables and charts inside the user's authenticated Workspace.

Read-only. Clevertrek issues no mutate operations of any kind against the Google Ads API. We do not create, edit, pause, remove or otherwise modify campaigns, ad groups, ads, keywords, budgets, bids, audiences or any other entity, and we do not automate bidding or spend decisions. Any optimisation suggestion produced by the Service is presented to the user as text, for the user to act on themselves inside the Google Ads interface.

No conversion tracking or remarketing. Clevertrek does not use the App Conversion Tracking and Remarketing API, does not upload conversions, and does not build or upload audience or remarketing lists.

3.5 Google Sheets and Clever Tables (drive.file)

Used to read the spreadsheets that the user picks in the Google Picker, to show their data in dashboards, to answer the user's questions about them with the AI assistant and, if the user chooses, to import a spreadsheet into Clever Tables.

Specific operations performed:

• launch the Google Picker so that the user chooses the spreadsheets;
• read the metadata of the chosen files through the Google Drive API;
• read the spreadsheet structure and cell values through the Google Sheets API (spreadsheets.get and spreadsheets.values.get) or, if the Sheets API cannot read the file, export it as CSV through the Google Drive API (files/{id}/export);
• for a Clever Tables import, these reads run in the user's browser with the short-lived access of the Google Picker, limited to the file the user picked.

Narrow scope. With drive.file, Clevertrek can open only the files the user has picked; it cannot list or read the rest of the user's Drive. A Clever Tables import is a copy that the user creates on purpose: it is no longer updated from Google and is kept with the project.

3.6 Google Drive — Picker, file-by-file (drive.file)

Used to let the user select files from their own Google Drive and attach them to a Workspace or project (for example in Ideation), or to an AI chat, via the Google Picker UI hosted by Google.

Specific operations performed:

• launch the Google Picker UI inside the Clevertrek interface, with a short-lived access token that stays in the user's browser;
• receive the metadata of the files actively selected by the user (file ID, file name, mime type, web view link);
• when the user attaches a file to an AI chat, the user's browser downloads that file (converted to PDF where needed) and sends its content with the user's question.

Narrow scope. The drive.file scope gives Clevertrek access only to the files the user has picked. Clevertrek cannot enumerate the user's Drive or access other folders or files.

3.7 Where the data flows

Where the data flows. Responses from Google go directly to the Clevertrek server that handles your request, are processed to show charts, tables and reports, and are returned to your browser inside your authenticated Workspace. They are also used by the AI features you use and by the report-rendering service when you generate a report, as described below. Each user's Google User Data is visible only inside their own Workspace, to the people they give access to it there. Clevertrek does not combine the Google User Data of different users, republish it or sell it.

Background use that you set up. Some features read your connected accounts while you are not using Clevertrek, only because you set them up: scheduled automations (for example SEO Controller reports, insights and project memory on a schedule) and the reading of your top Search Console pages that you start in Content Ideas. When you create an automation that sends data to the AI, Clevertrek asks for your permission first. You can pause or remove automations at any time on the Automations page. Automations that use Search Console pause on their own when that connection, or your access to that property in the project, is no longer available.

Not Google User Data: page speed. The PageSpeed reports of Clevertrek use Google's public PageSpeed Insights API with Clevertrek's own API key, on the public address of the page the user enters. This does not use the user's Google account or any OAuth scope.

4. Limited Use of Google User Data — Affirmative Statement

Clevertrek'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.

In plain terms, this means:

(a) Only for the features you use. Clevertrek uses Google User Data only to provide or improve user-facing features that are prominent in Clevertrek and that you use: Google Sign-In; the Search Console, Google Analytics, Google Ads and Google Sheets connectors and the features that show their data in your projects (SEO Controller with its reports and insights, Live Dashboards, Google Ads Controller, Rank Tracker, Keyword Research, Content Ideas, Persona Studio, Ideation, Talk to Report and Clever Tables imports); the Google Drive file picker; the automations you set up; and the AI features described below, when you use them.

(b) No transfer. Clevertrek does not transfer Google User Data to anyone, except: to provide or improve those features, through the service providers listed below; for security purposes (for example, investigating abuse); to comply with applicable law; or as part of a merger, acquisition or sale of assets of Clevertrek, and then only after obtaining your explicit prior consent. Clevertrek does not transfer or sell Google User Data to advertising platforms, data brokers or information resellers.

(c) No advertising. Clevertrek does not use or transfer Google User Data for serving advertisements, including retargeting, personalized or interest-based advertising, and does not sell it.

(d) No credit decisions. Clevertrek does not use or transfer Google User Data to determine credit-worthiness or for lending purposes.

(e) No training of AI models. Clevertrek does not use Google User Data to develop, improve, or train generalized AI or machine-learning models, whether its own or those of third parties.

(f) Nobody reads your data. No person at Clevertrek reads your Google User Data, unless: (i) you have given your explicit agreement for specific data (for example, when you ask for help with a specific report); (ii) it is necessary for security purposes, such as investigating a bug, abuse or a security incident; (iii) it is necessary to comply with applicable law; or (iv) the data has been aggregated and anonymized and is used for internal operations. The operator works with aggregated metrics, error counters and logs that exclude Google User Data payloads where reasonably possible.

5. AI Features and Google User Data

Clevertrek's AI features are powered by Anthropic's Claude API (Anthropic, PBC). Google User Data (from Search Console, Google Analytics, Google Ads, Google Sheets and the Google Drive files you attach) is sent to Anthropic only to produce the AI feature you use:

• When you ask the AI assistant a question. The assistant retrieves from your connected accounts only the report, date range and fields that the question needs, and sends them with the question. Google User Data is not added to a conversation when the question does not need it.
• When you use an AI tool that works with your connected data, such as SEO Controller reports and insights, Talk to Report, Persona Studio, Ideation or Content Ideas. The tool sends only the data it needs for the result you asked for (in Content Ideas, for example, the paths of up to 20 of your top pages, each with up to 3 of the searches that lead to it, so that new ideas do not repeat them).
• When you attach a Google Drive file to an AI chat. Your browser downloads the file you picked (converted to PDF where needed) and sends its content with your question.
• When an automation you set up sends data to the AI (scheduled SEO Controller reports, insights or project memory). Clevertrek asks for your permission when you create it, and you can pause or remove it at any time.

In every case, only data from the Google accounts you have connected and can use in that Workspace or project is sent, together with any spreadsheet that you or a member of that Workspace imported into Clever Tables there (Section 11.7 of the Privacy Policy), and only what the feature needs. Instructions and project context that Clevertrek adds to every AI request on its own do not include figures from Google. Data sent through Anthropic's commercial API is not used to train Anthropic's models. If you use your own API key (BYOK), the request is made under your key, and these commitments still apply to the Google User Data we send. Clevertrek does not send Google User Data to Anthropic, or to any other AI provider, for any other purpose, and does not use it to build a profile of you.

6. Service Providers That Receive Google User Data

Google User Data is processed only by the following service providers (sub-processors), and only as needed for the features described above:

Google User Data is not sent to payment processors, email-delivery providers, analytics or advertising providers, or any other third party. Google is the source of this data, not a sub-processor of Clevertrek. The full list of Clevertrek's sub-processors is published at /forms-privacy/#sub-processors.

7. Storage and Security of Google User Data

• TLS encryption for all communications between your browser, Clevertrek's servers and Google APIs.
• OAuth tokens encrypted at rest. The access and refresh tokens of the Search Console, Google Analytics, Google Ads and Google Sheets connectors are stored only on Clevertrek's servers, encrypted with authenticated encryption (XChaCha20-Poly1305). The key is kept in the server configuration, outside the database, so the tokens cannot be read from a database export.
• The Google Drive picker uses a short-lived access token that stays in your browser and is not stored on Clevertrek's servers.
• Access to the production environment is limited to the operator named in this document; the hosting provider can access it only to provide its service.
• Server and error logs are monitored for security events.
• When you disconnect, Clevertrek asks Google to revoke its access and deletes the stored tokens (see revocation below).
• If we become aware of unauthorized access to Google User Data, we will notify the affected users, the Spanish Data Protection Agency (AEPD) where required, and Google, as required by Google's API terms and policies.

8. Retention of Google User Data

9. How Users Revoke Access and Delete Their Google User Data

You can remove Clevertrek's access to your Google data at any time, in two ways:

1. Inside Clevertrek: go to Connectors (/connectors/), open the Search Console, Google Analytics, Google Ads or Google Sheets connector and click Disconnect. Clevertrek asks Google to revoke its access and deletes the tokens it stores. Clevertrek's Google connectors share one authorization with Google, so revoking it also disconnects your other Google connectors in Clevertrek (Search Console, Google Analytics, Google Ads and Google Sheets); the confirmation window warns you before you confirm. If Google cannot confirm the revocation, Clevertrek tells you, so that you can remove the access yourself as in step 2.
2. In your Google Account: at https://myaccount.google.com/permissions, remove Clevertrek from the list of connected applications. The next time Clevertrek tries to use the connection, Google rejects it and Clevertrek deletes the stored tokens.

Files picked with the Google Drive picker use a short-lived access that expires on its own after about one hour; to remove it earlier, use your Google Account as in step 2.

What happens to the data saved in your projects is set out in the retention rules above. You can ask us at any time to delete specific Google User Data saved in your projects, or all the data of your Account, by writing to privacy@clevertrek.com (Sections 20-21 of the Privacy Policy).

Closing your Account. When you close your Account (Close account in your account settings), it is deactivated at once: you can no longer sign in, your automations stop, your personal data slots are archived and your name is shown as "Former member" in member lists and comments. Before you can close it, you have to turn off the accounts you use in your connectors and, if you own or administer a company Workspace, transfer it to another member or step down as its admin. Your content is kept: what you shared in a Workspace, or what a Workspace accepted, stays there (in member lists and comments, your name is shown as "Former member"). Closing your Account does not by itself delete your Google tokens or the identity received through Google Sign-In: to remove Clevertrek's access to Google, click Disconnect on your Google connectors before closing (or use your Google Account as in step 2), and to have the tokens and the identity (email, Google account ID, profile picture) of a closed Account removed, write to support@clevertrek.com. When we remove that identity, your content is kept in pseudonymized form, not anonymized: your identity details are removed, but the content itself stays. A closed Account cannot be used to export data; if you need your data after closing, ask support to reopen the Account.

10. Reporting Security Issues

Security researchers and Google's security teams can report issues at security@clevertrek.com. Good-faith reports submitted in line with reasonable disclosure practices will not be subject to legal action by Clevertrek.

11. Updates to This Disclosure

When Clevertrek's use of Google APIs changes — new scopes, new features, new service providers that handle Google User Data — this page and the corresponding Section 11 of the Privacy Policy will be updated. The "Last updated" date at the top of this page reflects the most recent change.

12. Contact

Clevertrek (Fernando Beneitez Vela-Hidalgo, sole proprietor, NIF 75794423Q) Avenida del Hotel, 1, 15º 08860 Castelldefels, Barcelona, Spain

• Support contact: support@clevertrek.com
• Privacy contact: privacy@clevertrek.com
• Security contact: security@clevertrek.com
• General legal contact: legal@clevertrek.com