Required access: All roles can read this guide · Export and delete actions follow role and plan rules
Use this article when a client, security review, or procurement questionnaire asks what Apogee Watcher stores, how long history lasts, and whether client data is isolated. Legal terms and the Data Processing Agreement remain authoritative for contract language — see Legal and the DPA.
What Watcher stores
Watcher stores configuration and monitoring artefacts for your organisation. It does not keep a full copy of every HTML page it discovers.
| Source | What is retained | What is not retained |
|---|---|---|
| Page discovery (sitemap / crawl) | Site page rows: URL, priority, strategy flags, auto-discovered marker, include-in-schedule settings | Full HTML bodies, asset files, or a lasting copy of the crawl tree |
| PageSpeed Insights (lab) | Per-run scores and Core Web Vitals (and supporting metrics), status, timestamps, strategy (mobile / desktop), plus a sanitised copy of the PSI response used to reopen result detail | Unused bulk screenshot payloads stripped on write; Google still processes the URL under Google’s terms when a test runs |
| CrUX (field data) | Field percentiles and related field metrics when Google returns them for that URL or origin and strategy, stored with the matching test result | A separate CrUX history feed — if Google has no data, Watcher shows an empty field section |
| Budgets, alerts, reports | Budget rules, alert / digest records, organisation and domain report metadata and PDF files when generated | Client CRM notes outside Watcher |
| Account and team | Organisation name and settings, site records, team memberships and roles, usage / billing context needed to run the Service | Payment card details (handled by the merchant of record at checkout) |
For how lab and field sections appear in the UI, see Run a test and read results and Lab data vs field data. Discovery behaviour: How page discovery works.
Hosting
Production hosting for Apogee Watcher is in European Union data centres. Subprocessors and transfers are described in the privacy policy and DPA.
Organisation isolation
Each organisation is a logical workspace boundary: sites, pages, test history, budgets, alerts, and reports belong to that organisation. Other customers’ organisations cannot open your data through the product. Access inside an organisation is role-based (Admin / Manager / Viewer).
Agencies often use one organisation per client so portfolios stay separate — Manage multiple organisations.
How long historical results last
Plan data_retention_days controls how long historical Site Test Results (and their stored raw payload) remain available before cleanup. Configuration (sites, pages, budgets) stays for the life of the account unless you delete it.
| Plan | Result history retention (default seed) |
|---|---|
| Free | 14 days |
| Personal | 30 days |
| Starter | 30 days |
| Professional | 180 days |
| Agency | 365 days |
| Enterprise | 365 days (custom agreements may differ) |
Confirm the live value on My Account and Understand plan limits. Export important history before it ages out — Export and delete your data.
Related plan features
Alert channels (email / Slack / webhook), PDF reports, white-label, and API access differ by tier. See Plan features by tier.