Run a check

Privacy notice

Privacy

Last updated 21 September 2026. This notice explains what Good To Go Live processes when you scan a website, view a report, request an email offer or unlock one through Stripe.

Controller and contact

Good To Go Live is operated by Wilbert Kramer | Marketing + AI, contact person Wilbert Kramer, Notarisappel 4, 8266 MA Kampen, the Netherlands. Privacy questions and requests can be sent to support@goodtogolive.com or info@wilbertkramer.nl. Telephone: +31 6 42 35 82 57.

Only what the launch check needs

When you start a scan, we process up to three page URLs, selected website goal, public HTTP response, a screenshot of the publicly reachable page, short text excerpts and references to up to three public images per audited page, derived findings, score, timestamps and limited technical logs. Short-lived abuse counters use cryptographic hashes of the requesting IP address and scanned domain; raw addresses are not stored in those counters. We do not ask for website credentials and do not intentionally retain a full copy of the scanned HTML.

If you explicitly request the report-and-offer email, we store the email address, report reference, exact consent version and timestamp, delivery status and provider message identifier. The email contains the saved report link and one promotional offer; it does not subscribe you to a newsletter.

If you pay, Stripe processes checkout, card information and your email address. Good To Go Live stores the Stripe session identifier, payment status, amount, currency and unlock time. If report email delivery is enabled, the checkout email is used to send the link to the unlocked report. Stripe, not Good To Go Live, handles full card details.

Purpose, legal basis and retention

Scan data is processed to provide the service you request. The optional report-and-offer email is sent only after your explicit request. Security logs may be processed for the legitimate interest of protecting the service. Payment records may be kept where required for accounting and legal obligations.

Detailed findings for unpaid reports are scheduled to expire after 30 days. Report-offer opt-in records are kept for up to 90 days for delivery, consent evidence and troubleshooting. Purchased report findings are retained so the saved report remains available while the service operates, unless deletion is requested or retention is no longer reasonably required to provide the purchase. Payment records may be retained for the legally required accounting period. A report URL is public by design, so do not scan a URL you are not comfortable placing in a shareable report.

A secure, pseudonymous browser token limits the included rescan to the purchaser. The token expires after 30 days and is stored in an HttpOnly cookie; the database stores only its cryptographic hash.

Who helps deliver the service

The service may use OpenAI Sites and Cloudflare for hosting, database, image storage, traffic filtering and rate limits; Webshot to render public website screenshots; Stripe for payment; Resend for paid-report email delivery; and cookieless Umami analytics for funnel events. The scanned public URL is sent to the screenshot provider. When a report is generated, its report URL and the scanned public URL are recorded as Umami event properties so we can measure the scan-to-report flow. These providers process data under their own terms and applicable agreements.

Access, correction and deletion

Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to processing. You may also complain to your local supervisory authority. We will verify requests before acting to protect report and payment data.

EU privacy principles require transparency, purpose limitation, data minimisation and storage limitation. The final public release should be reviewed against the operator’s actual business details, providers and data flows.