Privacy policy

Due to the use of advertisements, cookies and file uploads on this website, the following privacy policy applies.


Third party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to our users based on their visit to our sites and/or other sites on the Internet. Users may opt out of personalized advertising by visiting Ads Settings. Alternatively, users can opt out of third-party vendor's use of cookies for personalized advertising by visiting

Cookies with personal FTP and GPX converter settings

On the workout pages, the user can enter his/her FTP in order to personalize the workouts, showing personalized wattages instead of % of FTP. The FTP value of the user is stored on the user's device, in a so-called cookie. This means that the FTP value is just available to the user. It is not stored centrally on our servers. (Since the FTP is stored on the user's device only, this also means that the user will have to re-enter his/her FTP on each device that is used to visit the website with.)

On the GPX to Zwift workout converter page, the same FTP cookie is used to read and store the user's FTP. Besides that, a separate cookie is used to read and store the other GPX converter settings. This makes sure that the entered settings are remembered for the next time the user uses the GPX converter. The data is only stored on the user's device.

GPX file uploads

On the GPX to Zwift workout converter page, a GPX file can be uploaded to create a Zwift workout. The GPX file is temporarily stored on our servers in order to read the route and elevation data from the file. Besides this, the filename is used to give a similar filename to the created workout. After reading this data (latitude, longitude, elevation and filename), the GPX file is deleted from the server.