ODBL non-compliance

This page has mostly been inspired from the great work of OpenStreetMap community.

Process (suggestion)

1. When you discover a license non-compliance, check first if the usage of Open Food Facts data is substantial. If the usage of Open Food Facts data is substantial, continue with the next steps. If you are not sure, ask other people on a suitable place: #license channel on slack, or contact@openfoodfacts.org.
2. In fact, even if you are sure, you should definitely share your case with other people before.
3. Add an entry to the bottom of the table below. If you are unsure about the non-compliance, discuss it on the one of our common communication channels (see above). If you are sure, you can report it on slack, at forum or a mailing list, too.
4. Contact the publisher with a suitable pleasant and non-threatening email and update the record with the date you've contacted them.
5. Wait for a response for a suitable period. If that does not create the desired response then you should follow up with a second attempt to contact the publisher.
6. If that does not work and the violation is considered serious then report it, if not done yet, at #license channel on slack or contact@openfoodfacts.org.

Hints to contributors

Be gentle! We are a project for providing food transparency and not to argue with somebody about legal issues. It doesn't help anybody playing the police and collecting as much cases as possible. This could give Open Food Facts a bad image. Don't be too correct. If they give it their best then it is ok.

List of usages which doesn't comply with ODBL license

Page	Attribution ok	Share-Alike ok	Added by	Dates contacted	Date fixed	Comments
https://www.example.org	no	no	XXXX on 2020-05-03	XXXX on 2020-05-03 via email
Page	Attribution ok	Share-Alike ok	Added by	Dates contacted	Date fixed	Comments

See also

• Lacking proper attribution on OpenStreetMap wiki