Storage limitation
Data retention
Version V0.4.0 · Updated 18 August 2026
Principle
FindOne is designed around purpose limitation, data minimisation and storage limitation. Personal data should not be retained longer than needed for the purpose for which it is processed.
Current V0.4.0 matrix
| Data | Purpose | Current retention |
|---|---|---|
| Theme preference | Remember a user-requested light/dark presentation. | In the user’s browser until changed or browser storage is cleared. |
| Privacy choice | Remember analytics/marketing preference and version. | In the user’s browser until changed or browser storage is cleared. The record includes a timestamp and policy version. |
| Search text | Run a user-requested search. | Not persisted by the V0.4.0 public interface. |
| Marketing identifiers | Advertising measurement/personalisation. | Not active in V0.4.0. |
| Analytics identifiers | Audience/product measurement. | Not active in V0.4.0. |
| Infrastructure/security telemetry | Delivery, abuse prevention, debugging and service protection. | Subject to the active Cloudflare account/product configuration; exact provider retention must be recorded before the final privacy register is approved. |
Before search analytics is enabled
FindOne must define whether raw queries are stored at all, whether they can contain personal data, how queries are normalised or aggregated, the lawful basis, retention period, access controls and deletion procedure. Aggregate metrics should be preferred when raw event data is unnecessary.
Review cycle
This matrix must be reviewed whenever a new data source, analytics provider, advertising platform, search-event store, account system or partner integration is activated.