Privacy Policy

Last updated: October 19, 2026. Version française.

1. Who we are

Ads Clear View (“the Service”) is published by Frank Jost, sole proprietor, 67 rue de Bayard, 31000 Toulouse, France, company number (SIREN) 478 306 541. Contact: [email protected]. We are the data controller for the personal data described below.

2. What data we process

• Account data: email address, name, hashed password, Google account identifier if you sign in with Google, language, plan and subscription history.
• Google Ads data you upload (CSV exports) or authorize through the Google Ads API: campaign structure, keywords, search terms, ads, performance statistics and costs. This data does not normally contain personal data about your end customers, except search terms typed by internet users.
• Client information you enter about your own clients (name, contact name and email, logo) to organise accounts and reports.
• Billing data, processed by Stripe: customer identifier, subscription status, invoices. We never store card numbers.
• Technical logs: IP address, timestamps, pages requested, kept for 90 days for security and debugging.
• Report views: when a client opens a shared report, we count the view; no personal data is collected about the viewer.

3. Why we process it and on what legal basis

• Providing the Service (audits, chat, reports, client portals): performance of the contract.
• Billing and accounting: legal obligation and performance of the contract.
• Security, abuse prevention, debugging: legitimate interest.
• Service emails (reports, quota alerts, important changes): performance of the contract. No marketing emails without your consent.

4. Google user data

Ads Clear View accesses the Google APIs below only if you authorize it, with one authorization per service, from the “Data sources” page or from a client’s page. Each authorization requests only the scope of the service concerned. Access tokens are stored encrypted on our servers.

Limited Use disclosure. Ads Clear View’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 practice, Google user data is used only to provide the user-facing features you see in the application (analyses, assistant chat, reports). We do not sell it, do not use it for advertising, do not transfer it to anyone other than the sub-processors needed to run the Service (section 5), and do not use it to train, develop or improve artificial-intelligence models, ours or anyone else’s. No human reads it, except with your explicit consent, for security purposes (investigating abuse) or to comply with the law.

4.1 Sign in with Google (openid, email, profile)

• Data accessed: your email address, name, profile picture and Google account identifier.
• Why: to create your Ads Clear View account, sign you in, and record which Google account granted each authorization.
• Storage: in your Ads Clear View account, until you delete it.

4.2 Google Ads (Google Ads API, adwords scope)

• Data accessed: the list of Google Ads accounts your Google account can access (ID, name, currency), then, for each account you attach to a client: the structure of campaigns, ad groups, keywords, search terms, ads and assets, targeting criteria, conversion actions, recommendations, the account’s Shopping products, and their statistics (impressions, clicks, costs, conversions).
• Read-only: Google does not offer a read-only Google Ads scope; the adwords scope would allow changes to your campaigns, but Ads Clear View never writes to your account: no campaign, bid, ad or budget is ever created, changed or deleted. The application’s recommendations are advice that you apply yourself in Google Ads.
• Why: audits, dashboards, assistant answers, client reports.
• Storage: on our servers. Attached accounts are refreshed daily; each sync replaces the previous data. It is kept while the Google Ads account remains attached in your workspace.

4.3 Google Analytics (Google Analytics Admin and Data APIs, analytics.readonly scope)

• Data accessed: the list of GA4 properties visible to your Google account (property and account ID and name), then, for the property you attach to a client, aggregated statistics: sessions, users, engaged sessions, events and key events, revenue, by channel, source/medium, campaign, page, device, country, city or date. No individual visitor-level data is requested from the API.
• Read-only by nature of the scope: nothing is ever changed in Google Analytics.
• Why: to relate website traffic and conversions to the ad campaigns, on the client’s page, in the assistant chat and in the Analytics blocks of reports.
• Storage: the property list and the latest reading of the chosen property (28 days by channel, refreshed at most every 6 hours) are stored; other readings are cached in memory for 10 minutes. Figures included in a report you generate are stored with that report.

4.4 Google Search Console (Search Console API, webmasters.readonly scope)

• Data accessed: the list of verified Search Console properties of your Google account, then, for the property attached to a client, clicks, impressions, click-through rate and average position, in total and by query, page and day.
• Read-only by nature of the scope: nothing is changed in Search Console (no sitemap, no property).
• Why: the Search Console blocks of reports (organic traffic next to paid traffic).
• Storage: only the property list is stored; statistics are read on demand and cached in memory for 10 minutes, except those included in a report you generate, which are stored with that report.

4.5 Google Merchant Center (Merchant API, content scope)

• Data accessed: the list of Merchant Center accounts your Google account can access (ID and name), to attach the right merchant account to a client. Then, for the attached account, the client’s “Merchant diagnostic” screen reads: the account name and its account-level issues (accounts.issues); the product list (products.list), to count product statuses (approved, limited, pending, disapproved) by destination (Shopping ads, free listings…) and country, group product issues and list disapproved or limited products; for catalogs of more than 10,000 products, the aggregated statuses computed by Google (aggregateProductStatuses); and product clicks, impressions and click-through rate over the last 28 days (reports.search, product_performance_view), in total, by marketing method (ads or organic) and for the ten most-clicked products.
• What is kept of a product: the API returns each product’s full data; Ads Clear View keeps only its title, identifier (offerId), statuses and issue labels. Prices, inventory, descriptions and images are neither stored nor displayed.
• Read-only for your products and feeds: all these operations are reads; no product, feed, price or account setting is ever created, changed or deleted.
• Only write, at your request: Google opens the Merchant API to an application only once it is registered with the merchant account. If you click “Register”, Ads Clear View calls developerRegistration.registerGcp once, which registers the Ads Clear View Google Cloud project with that account and gives your email address the developer-contact role. No other write is made. The content scope is the only scope Google offers for this API: there is no read-only version.
• Why: to show, on the client’s page, the state of their merchant account and the products to fix, next to their Shopping campaigns.
• Storage: the list of merchant accounts, and the latest diagnostic of the attached account (refreshed at most every 6 hours or on “Refresh”; at most 200 products to fix), until you detach the source or remove the authorization. This data is not sent to the AI assistant and is not included in reports.

4.6 Google Business Profile (Business Profile APIs, business.manage scope)

• Not offered yet: connecting a business profile appears in the application only once Google has opened Business Profile API access to the Ads Clear View project (request pending). Until then, no data is read.
• Data accessed, once access is open: the list of accounts and locations visible to your Google account (ID, name, city of the address), to attach the right location to a client; then, for the attached location, daily performance metrics (fetchMultiDailyMetricsTimeSeries): calls, direction requests, website clicks and profile views (Search and Maps).
• Read-only: the business.manage scope would allow editing the profile or replying to reviews, and Google offers no read-only scope for these APIs; Ads Clear View never writes: no business information, review, post or photo is ever created, changed or deleted.
• Why: the “Business Profile” blocks of reports (calls and direction requests next to the campaigns).
• Storage: only the list of locations is stored; statistics are read on demand and cached in memory for 10 minutes, except those included in a report you generate, which are stored with that report.

4.7 Use by artificial intelligence

To answer your questions, write an audit or the commentary of a report, Ads Clear View sends the necessary data extracts to the AI model: Google Ads data, Google Analytics statistics that the assistant queries during the chat, and the figures (Google Ads, Analytics, Search Console) of the blocks of a report for which you request a written commentary. The model is Anthropic’s Claude (through its API) or, if you saved your own API key, the provider you chose (Anthropic or OpenAI). The data is sent only to produce the answer you asked for, and never to train a model. The assistant’s answers, which may quote these figures, are kept in your chat history.

4.8 Sharing, revoking access and deletion

• Sharing: Google data is visible only to the members of your workspace and to the people you send a report to or open a client portal for.
• Removing an Analytics, Search Console or Merchant Center authorization (Data sources page → Remove): the token is revoked at Google and deleted, together with your clients’ sources that used it and their stored data.
• Disconnecting a Google Ads account (Data sources page): the token is revoked at Google and deleted; Google Ads accounts already synced keep their data until you detach them from the client, delete the client or delete your account.
• Detaching a source or a Google Ads account, deleting a client: the corresponding stored data is deleted.
• Deleting your account (Settings → Delete my account): all your Google authorizations are revoked at Google and deleted, along with stored Google data, conversations and reports (see Deleting your data).
• You can also revoke access at any time from your Google account permissions; the application then stops reading that data.

4a. Data received from Facebook / Meta

Ads Clear View can be linked to Facebook pages and Meta ad accounts to read, read-only, the leads submitted through instant forms (name, email, phone, answers to the form) and advertising statistics. This data is used solely to pass the person's request on to the recipient named in the form and to produce the advertiser's analyses and reports. It is never sold, never used for other advertising purposes, and never used to train artificial-intelligence models. It is kept for at most 36 months, or until you ask for its deletion: see Deleting your data. You can also remove the app from your Facebook account settings (Apps and websites).

5. Sub-processors and international transfers

• Hosting: Hostinger International Ltd (servers located in the European Union).
• Payments: Stripe Payments Europe Ltd.
• AI models: Anthropic PBC (Claude); OpenAI only if you chose it with your own API key. Only the data extracts needed to answer are transmitted (see 4.6). These providers are located in the United States; transfers are covered by Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
• DNS and network protection: Cloudflare, Inc.
• Email delivery: SMTP operated by the publisher.

6. Retention

Account data: until you delete your account, then 30 days. Google Ads data (uploaded or synced): replaced at each sync or upload, and kept while the Google Ads account remains in your workspace. Analytics, Search Console and Merchant Center data: see section 4. Conversations: until you delete them or your account. Published reports: until you delete them. Invoices: 10 years (legal requirement). Technical logs: 90 days.

7. Your rights

You may access, rectify, erase, restrict or port your data, and object to processing based on legitimate interest, by writing to [email protected]. You can delete your account and all associated data from Settings. Residents of the European Union may lodge a complaint with their supervisory authority (in France, the CNIL). Residents of California may exercise their rights under the CCPA using the same contact; we do not sell personal information.

8. Security

TLS encryption in transit, hashed passwords, API keys encrypted at rest, access limited to the publisher. No system is infallible; if a breach affects your data, you will be notified within the legal time limits.

9. Cookies

Only technical cookies: session and language preference. No advertising cookies, no third-party trackers.

10. Children

The Service is intended for professionals and is not directed at children under 16.

11. Changes

We may update this policy; the date at the top reflects the latest version. Material changes are announced by email or in the application.