Data retention

Data Handling & Retention

Gnomeo keeps analytical memory and reports so recurring reviews work, but raw uploads should stay temporary and minimized.

Temporary data

  • Raw CSV uploads.
  • Parsed processing files.
  • Temporary report generation artifacts.

Raw CSV uploads are retained only temporarily for processing, support, and limited reruns. A practical paid-tier target is up to 7 days unless deleted earlier.

Persistent data

  • Generated reports.
  • Workspace memory and preferences.
  • Trend snapshots and recommendation history.
  • Usage and billing metadata where applicable.

Why keep analytical memory

Recurring reviews are more useful when Gnomeo can remember prior findings, compare trends, and avoid treating every upload as a brand-new problem.

Why this lowers risk

Keeping memory instead of raw exports reduces security exposure, limits sensitive file retention, and better fits GDPR-aware data minimization.

User deletion requests

Users should be able to request deletion of workspace data and raw uploads. Backups and logs may have limited operational retention, but the principle is minimization.

Suggested retention model

  • Temporary parsed files: delete within 24 hours where possible.
  • Generated reports and workspace memory: retain until deleted or account closure.
  • Backups/logs: limited operational retention only.
  • Exact retention may evolve, but the principle stays the same: keep less raw data.