Timeline for notices

Withings may, at its sole discretion, change, improve and correct the Service from time to time. Withings may also provide updates for the Service that are considered important or critical by Withings, and in such case you may not continue using the previous version of the Service; use of the previous version of the Service may be prevented if the update is not integrated.

Withings will use commercially reasonable efforts to notify you of any changes to the Service through notifications (refer to the Tracking Change section). Changes to the Service may have an adverse effect on partner applications using the Service. Withings will not be liable towards you or third parties for such changes or any adverse effects resulting from such changes.

As part of our change policy, we've also established a timeline for how we classify changes and when they will take effect.


Change CategoryDescriptionTime to deployment
Normal ChangesThese are “business as usual” changes which are expected to make up the majority of the changes. There is no impact on partner integration. No action required on partner integration of the ServiceNo notification
Major ChangesThere are either breaking changes that have an impact on partner integration of the service (e.g. changes to a web service response body), or changes to a business critical service. There is an action to be carried out on partner integration of the service. The change will be automatically released for production on the planned release date. In the meantime, the partner will be able to test and integrate the change (refer to the upcoming releases testing and integration)One month - Up to three months for a Business Critical change
Emergency ChangesWhile all changes that may be necessary should be anticipated and planned, there will be times when business requirements will require changes to be made in an emergency. Withings will use commercially reasonable efforts to solve any issue that impacts internal or external “live” systems and requires implementation in order to resolve (or prevent) a current high priority incident or problem.No notification - Up to two weeks