Privacy policy

Websites (we-amp.com, modpagespeed.com, iispeed.com, ngxpagespeed.com)

Our websites are static. To understand how visitors use them, all of our websites — we-amp.com, modpagespeed.com, iispeed.com, and ngxpagespeed.com — load a self-hosted instance of Umami from umami.we-amp.com. Umami sets no cookies, builds no profile across sites and shares nothing with third parties; it runs on the same Google Cloud server as the rest of our infrastructure. With each pageview our Umami server receives your IP address and user agent and derives from them a pseudonymous session identifier (a hash of the IP address, the user agent and a value that changes every month); it does not store the IP address. For each session it stores the browser, operating system, device type, screen size, language, and the country, region and city derived from your IP address. For each pageview or event it stores the page path and query string, the referrer, the page title and the name of a few click events (e.g. "download"). Within a month, visits from the same browser therefore share one session identifier. We use this only to see how the sites are used, never to identify individuals. Rows older than 13 months are deleted daily (backup copies are kept a week longer).

Our web servers (nginx, and the Apache server behind it) keep standard access logs: the IP address, the requested URL, a timestamp, the referrer and the user agent, and for the subscriber package repository the subscriber user name you sign in with. Your browser's requests to the analytics tracker appear in these logs like any other request. The logs are rotated daily and kept for at most 15 days, then deleted. We use them for security and operations.

Our server also looks up the connecting IP address in two DB-IP Lite databases held on the server itself (country, and network operator), refreshed monthly; the address is not sent to DB-IP or anyone else for this. We use the network operator to leave visits from datacenter and cloud-provider networks out of the analytics (such visits are simply not counted), and the country to limit the administrative interface of our analytics to the Netherlands (no effect for visitors). The IP-location data is provided by DB-IP.com under the Creative Commons Attribution 4.0 International License.

Our websites load no third-party scripts. Purchases happen on FastSpring's own pages, which you reach through a link (see below).

License service (api.modpagespeed.com) — historical

The license model was retired with the move to Apache-2.0 on 2026-09-17; the current software activates no license. While the license service operated, activating a license processed: your license key, and the product and version identifier. License tokens were Ed25519-signed and cached locally on your server; routine validation was offline. Tokens included a products field (listing which products the license covers) and a max_instances field (your contractual instance limit). These fields were token metadata delivered to your server — they did not constitute additional data collection.

IP addresses were held in memory only for rate limiting and abuse prevention; they were not persisted to disk.

We also stored a terms-acceptance timestamp (retained for 5 years under the Dutch limitation period) and, for paid subscriptions, the FastSpring subscription ID (retained for the duration of the subscription plus 1 year).

Instance telemetry

mod_pagespeed is open source and does not check a license (see above). The software does not contact our servers and sends us no telemetry.

Earlier ModPageSpeed 2.0 releases renewed a license token every 12 hours and, with that request, sent a hashed machine identifier, the product name and the version. Those heartbeat records contained no personal data and were automatically and permanently deleted after 30 days.

Installs of earlier releases that were sold a production license may still contact our retired license-renewal endpoint. It keeps no license or heartbeat record any more; such a request appears only in Google Cloud's standard request log (IP address, time, requested URL), kept for 30 days. The endpoint is being switched off as the last legacy terms expire.

Until it is switched off, that retired service still acts on a chargeback or fraud report from FastSpring for a purchase from the license era: it stores a one-way SHA-256 hash of the purchaser's email address in a deny list, never the address itself, to prevent repeat abuse (legitimate interest: fraud prevention). The list currently holds no entries.

ModPageSpeed software

ModPageSpeed runs entirely on your servers. It optimises and caches your web content locally; it does not send traffic data, page content, or visitor information to us.

The admin console (a web interface served from your server) uses sessionStorage for authentication tokens — no cookies are set by the console.

Purchases and subscriptions (via FastSpring)

When you buy a support subscription or another service, we process your name, email address, organisation and order details to provide it, to give you access to the subscriber repository where it applies, and to invoice (legal basis: performance of a contract, Art. 6(1)(b), and our bookkeeping and tax obligations, Art. 6(1)(c)).

Payment processing is handled by FastSpring (Bright Market LLC), our Merchant of Record. FastSpring collects the personal and payment data necessary to process your order (name, email, billing address, payment details). We receive your name, email address, and order details — but not your full payment information.

FastSpring acts as an independent data controller for payment processing. See FastSpring's privacy policy for details on their data handling.

Email communication

When you contact us via email, we process your email address and message content to respond to your inquiry. We do not add you to marketing lists without explicit consent.

Support mail

We give support subscribers our support address when their subscription starts. When you write to it, we process your message and any attachments, your name and email address, and the history of the ticket: your messages, our replies and their dates. We link the ticket to your customer record, which holds your organisation's name, your support tier and subscription term, the contacts you gave us (name, email address and role), and the FastSpring subscription or invoice reference. We use this to answer you, to keep to the response targets of your tier, and to send the security notices your subscription includes. We collect nothing else for support (legal basis: performance of a contract, Art. 6(1)(b)).

Support mail, including our replies, is stored in Google Workspace, in our support archive and in the mailboxes of the people who handle support. Ticket records and attachments are kept on an encrypted disk on equipment we operate ourselves, not with a hosting provider.

Triage (the severity and kind of question) and a first draft of each reply are prepared with software assistance. Every reply to you is read and approved by a person at We-Amp before it is sent. The models used for triage and drafting run on equipment we operate ourselves. Before we use an external model provider for drafting, we will update this notice; such use will be under terms that forbid training on your data.

We approve each reply in a private Telegram chat. The approval message contains the draft reply and basic ticket details (ticket number, your organisation's short name, tier, severity, status, due time and your mail domain); it never shows your email address or the subject, and shows your own words only where the draft quotes them.

A ticket's text and attachments are deleted 12 months after the ticket is closed, including the copies in the support group archive and in the mailboxes of the people who handled it. We keep only its dates, severity and category, without personal data, for our response-time records. Twelve months after your subscription ends, we delete your contacts from your customer record; the billing reference stays with our purchase records. Our backups are encrypted before upload and stored in a private Google Cloud bucket; they expire after about 97 days, so deleted data is gone from the backups within about 97 days of its deletion.

Web forms

When you submit a contact, quote or consulting form on our websites, we receive what you fill in: your name and email address, your message, the topic you pick, and the form's own fields — on the contact form your organisation, role and number of servers; on the consulting form your organisation, the area and the timeframe; on the platform-interest form your site and number of sites. We also receive the page you sent it from. The form posts to our contact service on Google Cloud, which does three things with it: it sends it to our mailbox as an email through Google Workspace; it writes it to Google Cloud's application log, kept for 30 days; and it stores it as a lead record in our database on Google Cloud, kept for 24 months and then deleted automatically. Copies in our mailbox are kept for 2 years after last contact. None of these contains your IP address; it appears only in the web server access logs described above. Google Cloud's request log of the submission carries your browser's user agent and referrer, not your IP address, and is kept for 30 days. We use this to answer your inquiry and to keep a record of it (legal basis: legitimate interest, Art. 6(1)(f), or steps toward a contract, Art. 6(1)(b), where relevant). We do not use form submissions for marketing.

Newsletter and product updates

With the newsletter sign-up on modpagespeed.com (in the footer and at the foot of blog posts) you can opt in to product and web-performance updates by email. Opting in is always a separate, un-ticked choice. We store your email address, where you signed up, and the consent in our database on Google Cloud, for 24 months from your most recent sign-up, and handle the sign-up like a form submission above (email to us, 30-day log, lead record). We only send updates to people who opted in, every message will include an unsubscribe link, and we do not sell or share your address (legal basis: consent, Art. 6(1)(a)). You can withdraw consent at any time by emailing privacy@we-amp.com, without affecting the lawfulness of what we did before. We then delete your subscription record; the lead record of your sign-up stays until its 24 months end, as the record that you consented.

modpagespeed.com

Everything above applies to modpagespeed.com. In addition, that site offers:

Quick-message widget

A short “quick message” form on every page. We process the message text and the page path you sent it from, plus — only if you choose to give it — your email address, exactly as for the web forms above (email to us, 30-day log, 24-month lead record; your IP address only in the access logs). Email is optional; without it we have no way to reply or to link the message back to you. An unsent draft is kept only in your own browser for the current tab (sessionStorage). We do not use these messages for marketing (legal basis: legitimate interest, Art. 6(1)(f)).

Page checks (/analyze and /ai-readability)

One check of a URL on /analyze or /ai-readability runs two things: Google's PageSpeed Insights and our AI-readability scanner. The URL you submit also appears in our access logs (at most 15 days). It may itself contain personal data if you choose to enter such a URL — please don't. We rate-limit requests per IP address to prevent abuse (legal basis: legitimate interest, Art. 6(1)(f)).

PageSpeed Insights. Our server forwards the URL to Google's PageSpeed Insights API (Google LLC, United States) in two requests (mobile and desktop) and returns the result. The forwarded requests carry your browser's user agent and referrer, not your IP address. Google processes them under its own Google APIs terms and privacy policy, not under our data processing agreement with Google Cloud. Results are cached on our server, keyed by the URL, and removed after 24 hours without a new request for that URL.

AI-readability scanner. The scanner fetches the URL so we can report how it looks to automated agents: once in a headless browser and with several plain requests (one without JavaScript, and agent requests with valid and deliberately invalid signatures). It runs on Google Cloud Run (United States). Your IP address is used in memory to rate-limit requests and is not stored by the scanner; it appears only in our access logs. Google Cloud's request log of the scan carries your browser's user agent and referrer, not your IP address, and is kept for 30 days. The result is kept for up to 24 hours behind a link that is derived from the scanned address, so anyone who knows that address can open the result during that time. We do not otherwise keep the page content. If you use a form on a scan result to ask us about a finding, it is handled as a web form above and also carries the scanned URL and a short summary of the findings.

The software you run

As described under “Instance telemetry” and “ModPageSpeed software” above, the software you download from modpagespeed.com sends us nothing, and your visitors' data never reaches us. Where we do act as a processor for a business customer — for example during a support engagement in which you share logs or configuration — a Data Processing Agreement is available on request at privacy@we-amp.com.