data & privacy

A web page is not allowed to read another site’s HTML, so the fetching cannot happen in your browser. Every page of the sites you enter is fetched by our server, parsed for title, headline, canonical and links, and the result is handed back to your browser.

Everything after that stays in your browser: the matching, the results table, your manual re-mappings, directory rules, imported traffic data and the generated CSV files. They are never sent to us. The autosave that restores your session writes to your browser’s local storage on your own machine.

The marketing pages carry analytics and, if you allow it, session recording, so we can see which parts get read. The tool does not. Nothing under /app is recorded — the two urls you type and the redirect map you build are never watched.

The URLs of the two sites you enter, and the URLs of the pages found on them while crawling. It does not see, and does not store, the redirect map you build from them.

The application writes no logs of its own. Our hosting provider, Vercel, records one line per request — time, path, status, duration and the IP address of the caller. Functions run in Vercel’s Frankfurt region.

Payments are handled by Polar as merchant of record. We never see your card details. When you redeem a license key we ask Polar whether it is valid and register that it now belongs to your project — the two domains you entered — so that one purchase covers one relaunch.

The unlock itself is stored in your browser. We keep no user account and no customer database; Polar is the record of who bought what.

The Webflow app is the same tool in a panel. Two things differ. Your new site is not crawled: the panel reads its pages and CMS items through the Webflow API and hands the list to your browser. And to do that, our server keeps one thing it otherwise never would — the access token Webflow issues when you connect the app, encrypted, together with the site id and the time of the installation. It is used only to read that site and to write the redirects you ask for, and it never reaches your browser.

Every time the panel opens, Webflow confirms to our server who you are; we keep the user id for a 30-minute session and drop the rest. Your results are saved in the browser, per site. Uninstalling the app in your Webflow site settings makes the token useless at once, and we delete our copy the next time it is refused.

Silentfrog also runs on your own machine, in which case nothing reaches our servers at all: the pages are fetched directly from your computer to the sites you are crawling. Useful when a relaunch is under NDA, or when the old site is only reachable from your network.

Responsible for this service: Goodaim, Maximilian Lorenz, Zenettistraße 47, 80337 München, Germany — hi@silentfrog.dev. Full details in the imprint.

This page describes the technical reality. The formal document — legal bases, recipients, retention periods and your rights — is the privacy policy.

The legal wording still needs a review by someone qualified to give it.