Privacy

Who operates this product

WP Life Saver is the product named on the WordPress plugin (plugin author: WP Life Saver; plugin URI: https://wplifesaver.com). This policy covers the plugin, the cloud control plane, the customer account site, the staff ops tools, and this marketing site.

Data we collect

When you activate a license from WordPress, the plugin sends the site's canonical production domain, install ID (a ULID created once at first activation and never changed), site URL, and home URL. Starting a trial also uses the email address you enter on the License & Billing screen so the license record can be created.

On a scheduled heartbeat the plugin sends home URL, site URL, host, install ID, a file-integrity digest of the plugin, the WordPress version, and the license access state at that moment. This is how the license service knows the install is still the same site.

After a site is registered, the plugin reports a fingerprint of WordPress, theme, and plugin versions plus hashes of critical assets. A fingerprint change is what triggers re-verification of the certified profile.

The cloud crawler fetches the public URLs it discovers (sitemap and internal links). For each URL it stores a raw snapshot (HTML, response headers, network and console output), a semantic snapshot (normalized content, links, images, canonical/robots/schema, form fields, DOM outline, script/style handles), and desktop/mobile screenshots. These are the evidence the Verification Engine compares. The crawler does not receive your WordPress admin password.

Payments are processed by Stripe. The plugin never holds a Stripe secret key and never collects card numbers. Stripe customer and subscription IDs are stored on the license record so Checkout, the Customer Portal, and webhooks can be correlated.

This marketing site chooses language from the URL (/en or /tr) and the Accept-Language header. It does not set its own analytics or advertising cookies.

Data we do not collect

The cloud never stores a WordPress admin password. State-changing admin tests are not run against production. The plugin does not treat a local "the key is valid" boolean as the authority of record — the signed entitlement from the license service is.

Why we process this data

We process it to issue and enforce a domain-scoped license, to discover and verify pages before an optimization reaches visitors, to promote or refuse a candidate profile, to re-verify after a fingerprint change, and to take payment through Stripe. Site HTML and screenshots are processed because verification cannot run without them.

Processors

Stripe processes checkout, subscriptions, invoices, tax (when configured), and the Customer Portal. The cloud services in this product (license, API, crawler, verifier, planner) process license and verification data. No other payment processor is wired.

How long we keep it

A license row and its activation, heartbeat, and domain-transfer history stay for as long as the license exists, including the 7-day warning window and after a genesis revert (the last certified archive is kept so a later payment can be re-verified rather than blindly restored). Snapshots and verification runs are kept as the evidence a certificate and a repair loop are built from. Stripe retains payment records under Stripe's own policy.

Your rights

You can cancel a subscription and download invoices in the Stripe Customer Portal, opened from License & Billing in WordPress. You can stop the plugin from sending heartbeats and fingerprints by deactivating it. Requests to access or delete license and snapshot data for a site you operate are made from that same License & Billing screen — that is the authenticated operator surface this product already ships.

How to reach us

Billing, cancellation, invoices, and Stripe refund requests go through the License & Billing screen in WordPress (Stripe Customer Portal). There is no card form inside the plugin.