privacy policy

Last updated: 2026-11-15

Who we are

fleets.run ("fleets", "we") is operated by Yoann Defay (contact@yoanndefay.com). We provide a multi-site analytics terminal for operators of websites.

What we collect

From you (account holders)

Via connected analytics sources

When you connect Google Analytics, Search Console, or Cloudflare, fleets reads aggregated traffic data for the properties you authorize. We do not store raw event-level GA4/GSC data; we cache aggregates for up to 10 minutes (public boards) or 1 hour (private dashboards) to stay within upstream API quotas.

Google user data (Google Analytics and Search Console)

When you click Connect with Google, you grant fleets read-only access with these Google OAuth scopes:

| scope | what fleets does with it | |---|---| | analytics.readonly | Lists the GA4 properties you can access so fleets can match one to your site, then reads aggregated reports (visitors, sessions, pages, sources, countries, devices, events) for the property you connect. | | webmasters.readonly | Lists your verified Search Console sites so fleets can match one to your site, then reads search performance (queries, pages, clicks, impressions, CTR, position) for that site. |

We use this data only to show you your own dashboards, insights, alerts, audits and weekly email inside fleets, and to answer questions you or your AI agent ask fleets about your sites. We never write to your Google accounts.

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

Via AI assistants (ChatGPT, Claude and other MCP clients)

You can connect fleets to an AI assistant through our MCP server (https://fleets.run/mcp). You sign in to fleets and approve the connection on a consent screen; the assistant then holds an access token for your account.

Via the fleets pixel (PRO, optional)

If a customer installs the fleets pixel on their site, we collect signals from each page view:

We do not drop cookies and do not read existing cookies via the pixel. We treat the data as legitimate-interest analytics under GDPR; the customer who installs the pixel is responsible for surfacing its presence to their own visitors.

Retention

| data | retention | |---|---| | Account email, workspace, site metadata | until account deletion | | Encrypted connector tokens (Google, Cloudflare) | until you disconnect or delete your account | | Cached GA4/GSC/CF aggregates | rolling 24 h | | Pixel raw events | 90 days | | Pixel hourly aggregates (pixel_aggregates) | 18 months | | Stripe records | per Stripe retention policy | | Audit log (events) | 90 days | | AI assistant connections (OAuth clients, hashed tokens) | until revoked, or 30 days after last use | | Changes you log (change_logs) | until you delete them or your account |

Where data lives

Your rights

Email contact@yoanndefay.com for any of the above. We respond within 30 days.

Sub-processors

| processor | purpose | data | |---|---|---| | Google | sign-in with Google (only if you choose it) | email, name, profile picture | | AgentMail | sends the sign-in code email | email | | Cloudflare | hosting, database, DNS, pixel ingest, edge cache | all app data | | Stripe | payments | name, email, billing | | Cloudflare Email Worker | transactional + digest email | email, message content | | Anthropic (via the bourse.run gateway) | AI answers, audits, SEO advisor | the aggregates needed for the answer; not used for training | | DataForSEO | SEO snapshots (PRO) | your site's domain |

Changes

We will post an updated version of this policy on this URL and update the "Last updated" line. Material changes will be emailed to all account holders.