---
title: "Data and privacy — Egenverk Lagom"
description: "What Lagom stores, where and for how long, what leaves the site and to whom, and what is removed when you deactivate or uninstall the plugin."
canonical: https://egenverk.se/en/plugins/lagom/docs/data-and-privacy
lang: en
updated: 2026-10-14
alternate: https://egenverk.se/plugins/lagom/docs/data-och-integritet.md
---
# Data and privacy

Egenverk Lagom · v0.33.2 · WordPress 6.5+, PHP 7.4+ · Updated 2026-10-14

## What leaves the site

By default, nothing. The skin's fonts ship with the plugin.

- **PageSpeed Insights:** when you click **Run PageSpeed**, the server sends the address of a scanned public page of your site to Google, together with the API key if you have set one. Google opens the page logged out, as an ordinary visitor.
- **Request watch alerts:** the emails are sent with the site's own mail (`wp_mail`) to the address in **Email alerts to**, or to the site's admin email. They contain the endpoint's name, the number of calls in the minute, the limit and a link to Lagom.

A coverage run fetches its plan from the site and uploads its result to the site, with a run key. It sends nothing to anyone else, and it blocks tracking.

## Visitors

The request watch stores nothing about the visitor: no IP address, user, cookie, query string or request body. It stores only the type, the endpoint and the minute. The folder for the minute files is protected with an `.htaccess` and an empty `index.php`.

## What is stored

Everything sits in the site's own database and in the uploads folder.

| Where | Holds | How long |
| --- | --- | --- |
| `egenverk_lagom_settings` | The settings for every module | Until the plugin is uninstalled |
| `egenverk_lagom_seen_widgets` | Id and title of widgets seen on the dashboard | The list grows when an administrator opens the dashboard |
| The `egenverk_lagom_stats` transient | The figures on the overview | Ten minutes |
| User meta `egenverk_lagom_skin_off` and `egenverk_lagom_scheme` | Each user's skin and colour scheme choice | Until the user changes it |
| User meta `egenverk_lagom_advanced` | Whether the Advanced tab is on for the user | Until the user turns it off |
| `egenverk_lagom_scheduler_log` | Removed scheduler jobs per day and source, and which jobs failed ones came from | The last 200 rows |
| `egenverk_lagom_housekeeping_log` | The nightly housekeeping runs: counts and time taken | The last 60 rows |
| `egenverk_lagom_database_log` | Optimized tables and autoload changes, with user and time | The last 100 rows |
| Transients for dry runs and notifications | The latest count and pending notifications per user | A few minutes |
| `uploads/egenverk-lagom/watch/` | One file per minute with the type and endpoint of each call | Until summed, normally within a minute. Files older than a day are deleted. |
| `egenverk_lagom_watch` | Figures per endpoint for the last hour and peaks for the last day | Overwritten as it goes |
| `egenverk_lagom_watch_alerts` | Current alerts, at most 20 | Until someone clicks **Dismiss** or the module is switched off |
| `egenverk_lagom_asset_scan`, `_asset_rules`, `_asset_checks` | Scans, rules, the never-list addresses and verifications | Until the plugin is uninstalled |
| `egenverk_lagom_asset_log` | The rule change log, with user and time | The last 200 changes |
| `egenverk_lagom_plugin_never` | Your never-list for plugin rules | Until you change it |
| `egenverk_lagom_coverage_plan`, `_runs`, `_results`, `_log` | Coverage plan, runs, results and run log. Keys are stored only as a hash. | The last 20 runs and 200 log rows |
| `egenverk_lagom_psi_key` and `egenverk_lagom_psi_results` | The PageSpeed API key, not autoloaded, and the results | Until the plugin is uninstalled |
| The table `{prefix}egvl_order_index` and `egenverk_lagom_order_index_*` | The order search index and the state of its fill | See below |
| `wp-content/mu-plugins/egenverk-lagom-plugin-filter.php` | The must-use plugin for plugin rules, only if you installed it | Until the module is switched off or Lagom is deactivated or uninstalled |

The logs record which user made a change.

## Personal data in the order search index

When you switch on **Build Lagom's own search index**, Lagom keeps a copy of each order's billing email, phone number, postcode, first name, last name and company and the payment transaction id in the table `{prefix}egvl_order_index`, so the order list can be searched quickly.

- A row is removed when its order is deleted or anonymised with WooCommerce's personal data eraser, also while the fill is paused.
- The whole table is removed when the plugin is uninstalled.

## Scheduled jobs

Lagom schedules jobs only for modules that are on:

| Job | Runs through | When |
| --- | --- | --- |
| `egenverk_lagom_watch_sum` | WP-Cron | Every minute, while the request watch is on |
| `egenverk_lagom_watch_purge` | WP-Cron | Once, ten minutes after the request watch is switched off |
| `egenverk_lagom_housekeeping` | WP-Cron | At 03:00, while the nightly housekeeping is on |
| `egenverk_lagom_scheduler_failed` | Action Scheduler | Daily, only with Action Scheduler older than 4.0 |
| `egenverk_lagom_order_index_batch` | Action Scheduler | While the search index fills |

## Deactivate

When you deactivate Lagom, the must-use plugin is removed, the page cache is emptied and the request watch's scheduled jobs are cleared. Settings, rules and figures stay.

## Uninstall

The uninstall runs when you delete the plugin under **Plugins**. It removes:

- Lagom's settings, transients and the user meta for the skin and colour scheme. Keys from versions before 0.7.0, when the plugin was called Lagom, are removed when their content looks like Lagom's.
- the logs, scans, rules, verifications, coverage data, and the PageSpeed key and results
- the request watch's figures, alerts and the `uploads/egenverk-lagom/watch/` folder. The `uploads/egenverk-lagom/` folder is removed if it is empty.
- the table `{prefix}egvl_order_index`
- the scheduled jobs
- the must-use plugin, if it exists

This stays:

- **Autoload changes** made by the Database module. The log was their only record and is removed on uninstall, so undo the changes you want undone before you uninstall.
- The `egenverk_lagom_advanced` user meta, the choice to show the Advanced tab.
- What the modules have already cleaned up, such as old jobs, expired transients and sessions. It does not come back.
- Optimized tables stay optimized.

## Resources

- [Product page](https://egenverk.se/en/plugins/lagom)
- [Changelog](https://egenverk.se/en/plugins/lagom/changelog)
- [Docs](https://egenverk.se/en/plugins/lagom/docs)
- Previous: [CSS and JS](https://egenverk.se/en/plugins/lagom/docs/css-and-js)
- Next: [Troubleshooting](https://egenverk.se/en/plugins/lagom/docs/troubleshooting)