Privacy policy

Goodaim, Maximilian Lorenz, Zenettistraße 47, 80337 München, Germany.
Email: hi@silentfrog.dev

We have not appointed a data protection officer; we are not required to. Write to the address above with any data protection question.

Silentfrog maps redirects for website relaunches. You give it the address of an old site and a new one; on your instruction our server fetches the pages of those sites and reads their HTML — title, headline, canonical link and outgoing links. A browser is not allowed to read another site’s HTML, which is why this one step happens on our server and not on your machine.

Everything after that happens in your browser: the matching, the results table, your manual corrections, directory rules, imported traffic data and the CSV files you download. None of it is sent to us. We never see the redirect map you build.

Legal basis: Art. 6 (1) (b) GDPR, since the crawl is the service you asked for.

Your session — results, edits and, if you bought one, your licence token — is saved in your browser’s local storage on your own device, so the work survives a reload. We cannot read it. Clearing your browser storage deletes it.

This storage is required for the function you requested, so it does not depend on consent (§ 25 (2) no. 2 TDDDG). Legal basis: Art. 6 (1) (b) GDPR.

The site is hosted by Vercel Inc., 340 S Lemon Ave #4133, Walnut, CA 91789, USA. Functions run in Vercel’s Frankfurt region. Vercel processes data on our behalf under a data processing agreement, and transfers to the USA are covered by the EU standard contractual clauses.

The application writes no logs of its own. Vercel records one line per request: time, path, status code, duration and the IP address of the caller. These logs are kept for a short retention period at the provider and are used to keep the service running and to investigate faults.

Legal basis: Art. 6 (1) (f) GDPR — our interest in a service that works.

Purchases run through Polar Software Inc. as merchant of record. Polar handles the checkout, the payment and the licence key, and is the seller on the invoice. We never see your card details. When you redeem a licence key, we ask Polar whether it is valid and register that it now belongs to your project, so that one purchase covers one relaunch.

There are no user accounts here and no customer database. Polar is the record of who bought what. Data may be transferred to the USA under the standard contractual clauses. The terms of the purchase are on the terms of service page.

Legal basis: Art. 6 (1) (b) GDPR.

Silentfrog also runs as an app inside the Webflow Designer. Webflow, Inc., 398 11th Street, San Francisco, CA 94103, USA, operates the Designer and the API the app uses; your relationship with Webflow is governed by Webflow’s own privacy policy. Data may be transferred to the USA under the EU standard contractual clauses.

Connecting the app. When you install it, Webflow asks you to authorise access to your site and then hands our server an access token for it. We store that token, encrypted, together with the site id, the workspace id and the time of the installation — one record per site, nothing else. It is the one piece of data we keep on a server, because a token has to outlive the request that obtained it. It lives in a Redis database provided by Upstash, Inc. (USA) through our hosting provider Vercel, under the standard contractual clauses. The token is used only to read the pages of the site you opened the app in and to write the redirects you asked for; it never reaches your browser.

Opening the app. Each time the panel opens, the Designer gives it a short-lived id token, which our server verifies with Webflow. Webflow’s answer includes your Webflow user id, and can include your name and email address; we use the user id and the site id to issue a session token that is valid for 30 minutes and is kept in the panel’s memory only. The name and email address are neither stored nor logged.

Your site. The panel reads the URLs of your site’s pages and CMS items through the Webflow API and hands them to your browser for matching; we store none of them. The old site is crawled exactly as described above. A redirect is written to your site only when you press the button that does so, one redirect at a time. Your results and edits are saved in the browser’s local storage, separately for each Webflow site.

Licence keys. If you redeem a key in the panel, the licence additionally records which Webflow site it was redeemed in, so that one purchase covers one relaunch there just as on the web.

Ending it. Uninstalling the app in your Webflow site settings revokes the token at Webflow at once. Webflow does not notify us of that, so the record stays until the next time the app tries to use the token, is refused, and deletes it — the next time the panel is opened, at the latest. If you want it gone sooner, write to us.

Legal basis: Art. 6 (1) (b) GDPR — connecting the app is the service you asked for.

The consent banner is CCM19, operated by Papoo Software & Media GmbH, Auguststraße 4, 53229 Bonn, Germany. It records which categories you allowed or refused and when, together with technical data needed to prove it. It runs before you decide anything, because without it we could not ask you at all and could not document your answer.

Legal basis: Art. 6 (1) (c) GDPR in conjunction with Art. 7 (1) GDPR — we are required to be able to demonstrate consent.

We use Google Tag Manager to load Google Analytics. Both are provided by Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland, with Google LLC in the USA as a further recipient. Google is certified under the EU-US Data Privacy Framework; the standard contractual clauses apply in addition.

Tag Manager is loaded for every visitor, but it is started with every consent signal set to denied. In that state no analytics cookie is written, no identifier is stored and no measurement hit is sent. Only when you accept the analytics category does the consent manager lift the restriction and Analytics begin to work. Analytics then processes your IP address (shortened by Google before storage), pages viewed, approximate location, device and browser, so that we can see which pages are used.

Legal basis: your consent, Art. 6 (1) (a) GDPR and § 25 (1) TDDDG. You may withdraw it at any time with effect for the future, and withdrawing is as easy as giving it: use the cookie settings link at the bottom of this page. Withdrawal does not affect processing that already happened.

On our marketing pages we use Microsoft Clarity, provided by Microsoft Ireland Operations Ltd, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland, with Microsoft Corporation in the USA as a further recipient. Clarity records how a page is used — mouse movement, scrolling, clicks, the pages visited, and technical data such as browser, operating system, approximate location and a shortened IP address — and replays it as an anonymised session recording and as heatmaps. We use it to see which parts of the page are read and where people give up.

Clarity does not run on the tool itself. The pages under /app, where you enter the sites you want to crawl and where your redirect map is built, are excluded from any recording. What you do in the tool stays in your browser, and that stays true with Clarity switched on.

Clarity is loaded through Tag Manager and, like everything else there, only after you accept the corresponding category. Legal basis: your consent, Art. 6 (1) (a) GDPR and § 25 (1) TDDDG, withdrawable at any time through the cookie settings link at the bottom of this page. Data may be transferred to the USA; Microsoft is certified under the EU-US Data Privacy Framework and the standard contractual clauses apply in addition.

The typefaces are served from our own domain. No request is made to Google Fonts or any other external font service, so no data reaches a third party for the sake of a font.

The pages we crawl for you are processed in memory to answer that one request and are not stored afterwards. Your session data stays in your browser until you clear it. A Webflow access token is kept until Webflow refuses it after you uninstall the app, or until you ask us to delete it. Server logs are retained by Vercel for its standard, short retention period. Consent records are kept for as long as we may need to prove consent. Purchase and invoice data is kept by Polar for the periods commercial and tax law require. Analytics and Clarity data is retained by Google and Microsoft under their own published retention periods for the respective product.

You have the right to access your data (Art. 15), to have it corrected (Art. 16), erased (Art. 17) or restricted (Art. 18), the right to data portability (Art. 20), the right to object to processing based on legitimate interests (Art. 21) and the right to withdraw consent at any time (Art. 7 (3)). Write to hi@silentfrog.dev.

You can also complain to a supervisory authority. The one responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht, Promenade 27, 91522 Ansbach, Germany.

Providing data is neither legally nor contractually required beyond what the service technically needs. There is no automated decision-making and no profiling.

Silentfrog also runs on your own machine, in which case nothing reaches our servers at all — the pages are fetched directly from your computer. What is processed describes that in plain language.

Switching on a new tool inside Tag Manager needs no change to this site’s code, but it does need a paragraph here. If this policy does not name a service, we are not running it.

This policy describes our processing accurately. The legal wording has not yet been reviewed by a qualified lawyer.