Contents
In one sentence: WhatsWrong reads your site the way Google reads it, plus the data you connect to it. Nothing is installed on your site, none of your visitors is tracked, and the access you grant is encrypted and can be revoked at any time. This policy is a translation of the French version, which prevails in the event of any discrepancy.
1. Who processes your data, and in what capacity
For account and billing data, the publisher — Mathieu Ceran (EI), a sole trader (entrepreneur individuel) trading under the name AJD Studio, 2 rue des Cartellets, 01000 Bourg-en-Bresse, France (SIREN 532 735 990) — acts as data controller.
For the data of the sites declared by our customers (crawled public pages, Google Search Console data, written articles), the publisher acts as processor: the customer, who owns the site, decides what is connected and is its data controller.
Contact: hello@whatswrong.io.
2. What the Service processes
- The public pages of the declared site: the Service reads them as a search engine would (titles, text, links, images, response times) to infer the brand, article topics and technical health. Nothing is installed on the site.
- The site's Google Search Console data, if the customer connects their Google account: queries, pages, clicks, impressions, positions, sitemaps. Access is read-only (plus sitemap submission) and can be revoked at any time from the Connections page or from the Google account.
- The publishing credentials entrusted by the customer: Google refresh token, WordPress application password. They are encrypted (AES-256-GCM) before being stored and are never displayed again. API keys created by the customer are stored hashed.
- The content produced: briefs, articles, audit reports, competitor and link analyses, visibility probe results — attached to the site and readable only by the account that owns it.
- The account data described in section 5.
3. What the Service never processes
This section binds the publisher. Each point is a property of the code, not an intention.
- No visitors of our customers' sites. The Service places no script, cookie or identifier on the declared sites: it does not know their visitors, their IP addresses or their browsing paths.
- No private pages. Only publicly accessible pages are read; pages excluded by
robots.txtor protected by a password are not. - No writing to Search Console other than submitting a sitemap explicitly requested by the customer.
- No publication without confirmation.An article is sent to WordPress only after a confirmation click; through the API, it is the customer's site that comes to fetch it.
- No resale, no advertising sharing.A site's data serves only its owner.
4. Google connection and revocation
The Search Console connection goes through Google's OAuth consent: the customer chooses the account, sees the scope requested (reading Search Console data) and can withdraw it at any time. Removing the connection from WhatsWrong deletes the encrypted token; removing it from the Google account makes it unusable, and the Connections page reports it.
WhatsWrong's use of Google data complies with the Google API Services User Data Policy, including its Limited Use requirements: this data is used only to display and analyse the visibility of the connected site, is never passed on for advertising purposes and is read by a human only with the customer's agreement, for support.
5. Our customers’ account data
For people who open an account: name, email address, password (stored hashed, never in plain text), plan subscribed to, usage counters, Stripe customer ID and subscription status. Bank card data never passes through our servers and is never stored: it is processed directly by Stripe.
A session cookie strictly necessary to keep you signed in is set. It is not used for any measurement and is therefore exempt from consent.
6. Legal bases
- Performance of the contract (art. 6.1.b GDPR): account management, provision of the Service, billing.
- Consent (art. 6.1.a): connecting the Google account, which can be withdrawn at any time (section 4).
- Legitimate interest (art. 6.1.f): reading the public pages of the declared site, within the limits of section 3.
- Legal obligation (art. 6.1.c): keeping accounting records.
7. Recipients and sub-processors
The publisher neither sells nor shares your data. It uses the following providers, each bound by a data processing agreement:
- Vercel Inc. — application hosting and request routing.
- Neon, LLC (an affiliate of Databricks, Inc.) — database, AWS eu-west-2 (London, United Kingdom) region.
- Stripe Payments Europe, Ltd. — payment and billing (Ireland).
- Providers of artificial intelligence models — writing, analyses and visibility probes in conversational assistants (United States).
- A search data provider— keyword, competitor and inbound link metrics, and reading of search engines' AI answers; receives domain names, the keywords studied and the queries whose visibility is probed.
- An image generation service — article images (United States), from a description of the image to produce.
- A network of partner sites— publication of the links ordered individually (article 17 of the Terms); receives, for each order, the address of the page to promote, the target keyword, the name and description of the business and, for an AI Citation, the business's Google Maps listing.
- An email delivery provider — sending transactional emails.
What is sent to AI model providers, precisely: the public content of the analysed pages, the brand context inferred or corrected by the customer, Search Console aggregates (queries, positions, clicks) and the queries whose visibility is probed. No account data and no login credentials are sent to them.
The list of these providers by name is available on request at hello@whatswrong.io.
8. Transfers outside the European Union
Several providers involve a transfer of data outside the European Union:
- United Kingdom — database (Neon, AWS eu-west-2 region, London).
- United States— writing, analyses and visibility probes (AI model providers), which receive the public content of the analysed pages, Search Console aggregates and the probed queries; search metrics and reading of search engines' AI answers, which receive domain names, the keywords studied and the probed queries; image generation, which receives the description of the image to produce.
For any question about these transfers, write to hello@whatswrong.io.
9. Retention periods
| Data | Retention |
|---|---|
| Crawled pages, audits, articles, Search Console data | As long as the site is in the account, then deleted |
| Article images, already public on the sites displaying them | Kept after the site or account is deleted, with no link to it, so online articles do not lose them; removed on request |
| AI visibility probes and their results | 730 days |
| Google tokens and application passwords (encrypted) | Until the service is disconnected |
| Account, email, password (hashed) | As long as the account exists, then deleted |
| Invoices and accounting records | 10 years (legal obligation) |
Removing a site from the account deletes everything attached to it (pages, audits, articles, Search Console data, connections) in a single operation.
10. Your rights
You have the rights of access, rectification, erasure, restriction, objection and portability provided for in articles 15 to 22 of the GDPR. They can be exercised by writing to hello@whatswrong.io.
If you own a connected site: disconnecting Google or WordPress, or deleting an API key, takes effect immediately from the Connections and API pages; deleting the site deletes its data.
You may lodge a complaint with the French data protection authority, the Commission nationale de l'informatique et des libertés (CNIL), 3 place de Fontenoy, 75007 Paris, France — cnil.fr.
11. Security
Exchanges are encrypted in transit (HTTPS). Passwords are hashed. Access to a site's data is isolated per account and checked on every request. Google tokens and application passwords are encrypted at rest; API keys are hashed and shown only once.
13. Changes to this policy
Any substantial change is brought to the attention of account holders at least thirty (30) days before it takes effect. The version date appears at the top of the page.
The contractual terms of the Service are set out in the Terms of Use and Sale.
Last updated: 14 September 2026.