Contact BikeControl

Every way to reach the people who make BikeControl, and which one gets your question answered fastest.

BikeControl is published by OpenBikeControl UG (haftungsbeschränkt) in Germany. Support is not outsourced: messages sent through the channels below are read by the same small team that writes the app. There is no phone line and no promised response time — what follows is an honest description of each channel and what it is good for.

Last reviewed: 2026-08-22

Ways to get in touch

Support chat

bikecontrol.app/support

The best option for anything specific to your own setup. Sign in with Google, Apple, GitHub or Facebook, describe the problem, and attach screenshots or log files. Everything stays in one thread, so you never have to repeat yourself. A message started inside the app also carries your controller's Bluetooth name, its hardware manufacturer and firmware version, the app version and platform, and the trainer app you were using — which usually removes the first round of questions.

Email

support@bikecontrol.app

The same team reads support@bikecontrol.app. Use it if you would rather not sign in anywhere, if you are writing about a purchase or a privacy request, or if you want a written record of the exchange. This is also the contact address named in the privacy policy and in the terms of use.

Known issues

bikecontrol.app/issues

A public list of the problems currently being tracked and the ones already solved. Worth a look before you write: if your symptom is already on it, the entry says whether a fix exists, and often links a guide or a short video.

GitHub issue tracker

github.com/OpenBikeControl/bikecontrol/issues

Bug reports, feature requests, and requests for a controller or trainer that is not supported yet belong here, where they stay public and can be followed, commented on and tied to a release. The app's source code and its changelog live in the same repository.

Reddit — r/BikeControl

reddit.com/r/BikeControl

Rider-to-rider discussion: keymap ideas, gear-ratio setups, and what works with which trainer app. Often faster than support for questions other riders have already solved.

Facebook group

BikeControl Facebook group

The same kind of community discussion as the subreddit, for riders who are already on Facebook. Release announcements are posted in both places.

Which channel should I use?

If something is not working — a controller that will not pair, buttons that do nothing, a gear indicator that will not move, resistance that behaves strangely — check the known-issues list first, then open the support chat. The chat is the only channel where the device and version details needed to diagnose a problem arrive on their own.

If you are proposing a change rather than reporting a fault — support for a new controller, another action to bind to a button, different behaviour in a particular trainer app — GitHub is the better place, because the request stays visible and other riders can add to it.

Press, partnerships and the OpenBikeControl protocol

Trainer-app developers, hardware makers and journalists can use the same email address. BikeControl is part of OpenBikeControl, an open protocol for indoor-cycling controllers that MyWhoosh, Rouvy and TrainingPeaks Virtual have implemented natively; the project has its own site at openbikecontrol.org, and BikeControl's source code is public on GitHub.

What to include

Whichever channel you pick, three or four lines of detail save a round trip:

• the controller or smart trainer you are using, and its firmware version if you know it
• the trainer app you are controlling — Zwift, MyWhoosh, Rouvy, TrainingPeaks Virtual, Biketerra or another
• the device BikeControl runs on and its operating system: iPhone, iPad, Mac, Windows PC or Android phone
• what you expected to happen, and what happened instead
• a screenshot of the keymap screen, if the question is about a button or a gesture

Purchases, subscriptions and refunds

BikeControl is sold through the App Store, Google Play and the Microsoft Store, and every purchase is held by the store you bought it from. Refunds are therefore handled by that store under its own policy, not here. A purchase that will not restore, a trial that expired right after paying, or the wrong plan showing in the app are all things support can look into — mention the store account's email address and the approximate purchase date.

What each version costs, and what the free trial covers, is on the pricing page.

Privacy questions and data requests

Questions about what the app collects, and requests to have data removed, go to the same support address. The privacy policy names that address too, and sets out what is stored and what is not.

What the app collects, and what it deliberately does not, is set out in the privacy policy.

To have the data associated with your account deleted, use the data deletion page.

Who you are writing to

BikeControl — published under the name SwiftControl until early 2026 — is made by OpenBikeControl UG (haftungsbeschränkt), a limited-liability company registered in Germany and founded by Jonas Bark. The same company is named as the contact in both the privacy policy and the terms of use.

Support replies in English and German. Write in whichever language you prefer — it will be answered in one of those two.

Postal address

More about the app, the company and the rename is on the about page.