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)
- Email address (you sign in with an emailed code or with Google)
- Workspace name and site metadata you enter (domain, GA4 property ID, etc.)
- API tokens, encrypted with AES-256-GCM at rest
- Stripe billing identifiers if you upgrade to PRO
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.
- Storage: we store the OAuth refresh token encrypted (AES-256-GCM). Report data is cached as aggregates for at most 24 hours; we do not keep a copy of your Google data beyond that cache.
- Sharing: we do not sell Google user data and do not share it with third parties, except (a) the sub-processors listed below that run the service, (b) when you turn on a public board or share link, which shows the aggregates you chose to publish, and (c) when the law requires it.
- AI features: when you ask fleets a question or run an audit, the relevant aggregates are sent to our AI model provider to produce the answer for you. They are not used to train any AI model.
- No advertising: we do not use Google user data for advertising, and humans at fleets do not read it unless you ask us for support, it is needed for security, or the law requires it.
- Revoking access: disconnect Google in Settings → Sources, or remove fleets at https://myaccount.google.com/permissions. We then delete the stored token.
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.
- What the assistant can do: read your sites and their aggregated analytics (Google Analytics, Search Console, Cloudflare, PageSpeed), read your change log, add a site, and log a change. It cannot delete data, change billing, or read another account.
- What we receive from the assistant: only the arguments of each tool call (for example a site slug, a date range, the text of a change you log, or the question passed to the
asktool). We do not receive the rest of your conversation. - What we store: the connection (client name, redirect address, hashed tokens), the changes you log, and standard request logs. We do not store tool-call arguments or results beyond those logs and the caches listed under Retention.
- The
asktool: it sends your question and the aggregates needed to answer it to our AI sub-processor (see Sub-processors). The other tools call no AI model. - What the assistant's provider does: the results we return enter your conversation with that provider (OpenAI, Anthropic, or another), under its own privacy policy.
- Ending access: disconnect fleets in the assistant's settings, or email us and we revoke the tokens. Access tokens expire after 1 hour and refresh tokens after 30 days without use.
Via the fleets pixel (PRO, optional)
If a customer installs the fleets pixel on their site, we collect signals from each page view:
- IP address, ASN, country (Cloudflare edge)
- TLS fingerprint (JA3 / JA4 via Cloudflare bot management headers)
- HTTP headers: User-Agent, Accept-Language, Referer
- Page path
- Browser challenge results (canvas hash, WebGL renderer hash,
navigator.webdriverflag, hardware concurrency, paint timing) - Classification verdict (
human/suspicious/bot)
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
- Application, database (Cloudflare D1) and job queue: Cloudflare
- Pixel edge collection: Cloudflare global edge
Your rights
- Access — request a copy of the data we hold for you
- Deletion — request full account deletion
- Portability — request export in JSON
- Correction — fix any inaccurate data via the app UI
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.