Relaunch CheckService scope · test payments are not real purchases

The package

Know what you’re buying.

One map. Four dated checks. A private record of where the old links actually lead.

Revision relaunch-terms-2026-09-29-v1. Test checkout does not charge real money. Live ordering is available only when the service explicitly enables it.

$49 USD · one payment

Up to 250 mappings · up to two exact hostnames · checks on days 0, 1, 7 and 30

Review the amount and currency displayed by Stripe before confirming payment. This notice does not claim that tax collection or merchant-of-record service has been enabled.

Service and payment

Relaunch Check is offered by CGV North America, 160 E 84th St., New York, NY 10028, United States. Questions about an order: hello@cgvnorthamerica.com.

The package has a one-time configured charge of $49 USD, not a subscription. Stripe processes checkout. If Stripe offers payment in a local currency, review the converted amount or select USD before paying. A checkout return page is not confirmation of payment; work is queued after the server verifies the payment with Stripe.

What the check covers

You supply a CSV with an old URL and its expected final URL on each row. One package covers at most 250 mappings, a 256 KB file and two exact public hostnames. Only public HTTPS URLs are supported. URLs with credentials, query strings, fragments or custom ports are excluded.

We observe HTTP responses and redirects with HEAD requests, compare the final URL with your mapping and record the time and route. The checks do not inspect page content, run JavaScript, follow browser or meta-refresh redirects, log into websites, submit forms or change a website. They do not guarantee search rankings, traffic, content correctness or revenue.

A wrong destination, missing page or redirect chain is a finding, not evidence that the service failed to deliver. Blocked or otherwise unresolved checks are marked unverified, never reported as a pass.

Your authority and the saved map

You must be authorized to test every submitted hostname and to provide the URL map. Add the job-specific DNS TXT record shown in your workspace. Both endpoints and redirect steps must stay within the verified hostnames.

Keep the required TXT records in place through the last scheduled check. Verification is repeated before checkout and each run. Its authorization expires 40 days after the map is saved. The saved mapping is used for all four checks; changing it requires a separate job.

Save the recovery code before checkout. It is the way to regain access if the browser session is lost. A fresh saved map is eligible to start checkout for up to 24 hours; an existing unpaid checkout can expire earlier. Follow the expiry shown in your workspace and by the payment provider. An expired unpaid job cannot be treated as a paid order.

Schedule and delivery

Days 0, 1, 7 and 30 are measured from the server’s confirmation of payment. Day 0 is queued at that point; it is not a promise of an immediate result. The workspace shows the due time and status of each check.

Each completed check is published as a private ZIP containing an HTML report, CSV findings and observation evidence. Delivery means that the bundle is available in your workspace. We do not promise an email notification or track whether you have read it.

Portal access ends 45 days after you save the map, not 45 days after payment. The expiry shown in your workspace does not move when you restore access. Download your reports before that date. The privacy notice explains the distinction between access expiry and deletion.

Failed required checks and refunds

If a required check cannot be fulfilled, the service stops the remaining checks and automatically initiates a full refund of the package. This applies even if an earlier report was already available. A check that is more than 24 hours overdue without being started is also treated as a failed required check when the worker reconciles the schedule.

A report cannot count as fulfilled if more than 10% of its mappings remain unverified. Technical build, storage or publication failures can also prevent fulfilment. A report that reliably identifies wrong redirects or missing pages is still a completed report.

A refund request or pending status is not a completed refund. Completion requires confirmation from Stripe; payment-provider and bank processing can take additional time. If a refund remains unresolved, contact us with your order reference, never your recovery code or card details.

A confirmed refund stops future checks. Reports already published before the refund remain readable until the original portal expiry. General cancellation or discretionary refund requests can be sent to the contact address; no instant self-service refund is promised.

Privacy and questions

The service keeps the saved map, proof records, observations and order history as described in the privacy notice. Expiry, workspace switching and refunds do not automatically erase these records.

These product terms describe the agreed service and do not exclude rights that cannot be excluded under applicable law.