I could use more clarification, I really do not understand this answer and I'm not sure if it's falling upon a nuance I don't see. The OSM Legal FAQ says in 3d, "However, if the two datasets are matched 'trivially' by, for example, automated matching using a simple criterion such as name/locality, this is not 'substantial' and remains a Collective Database." (http://wiki.openstreetmap.org/wiki/Legal_FAQ#3c._If_I_make_something_with_OSM_data.2C_do_I_now_have_to_apply_your_license_to_my_whole_work.3F) If you are placing pins on an OSM map (from your own tile server) and those pins are being placed based on a latitude and longitude you already know (generated from your own app), that surely remains a Collective Database and thus does not require releasing your customer information. (Surely lat/long is far more trivial than name/locality.) If you are placing pins on an OSM map and those pins are being placed based on street address you already know (from customers giving it to you), isn't that too a trivial match and thus a Collective Database and does not require releasing your customer information? (Address is less trivial than name/locality, but still seems very trivial.) I'm struggling to understand the Legal FAQ any other way. Thanks.

I could use more clarification, I really do not understand this answer and I'm not sure if it's falling upon a nuance I don't see. The OSM Legal FAQ says in 3d, "However, if the two datasets are matched 'trivially' by, for example, automated matching using a simple criterion such as name/locality, this is not 'substantial' and remains a Collective Database." (http://wiki.openstreetmap.org/wiki/Legal_FAQ#3c._If_I_make_something_with_OSM_data.2C_do_I_now_have_to_apply_your_license_to_my_whole_work.3F) If you are placing pins on an OSM map (from your own tile server) and those pins are being placed based on a latitude and longitude you already know (generated from your own app), that surely remains a Collective Database and thus does not require releasing your customer information. (Surely lat/long is far more trivial than name/locality.) If you are placing pins on an OSM map and those pins are being placed based on street address you already know (from customers giving it to you), isn't that too a trivial match and thus a Collective Database and does not require releasing your customer information? (Address is less trivial than name/locality, but still seems very trivial.) I'm struggling to understand the Legal FAQ any other way. Thanks.

I could use more clarification, I really do not understand this answer and I'm not sure if it's falling upon a nuance I don't see. The OSM Legal FAQ says in 3d, "However, if the two datasets are matched 'trivially' by, for example, automated matching using a simple criterion such as name/locality, this is not 'substantial' and remains a Collective Database." (http://wiki.openstreetmap.org/wiki/Legal_FAQ#3c._If_I_make_something_with_OSM_data.2C_do_I_now_have_to_apply_your_license_to_my_whole_work.3F) If you are placing pins on an OSM map (from your own tile server) and those pins are being placed based on a latitude and longitude you already know (generated from your own app), that surely remains a Collective Database and thus does not require releasing your customer information. (Surely lat/long is far more trivial than name/locality.) If you are placing pins on an OSM map and those pins are being placed based on street address you already know (from customers giving it to you), isn't that too a trivial match and thus a Collective Database and does not require releasing your customer information? (Address is less trivial than name/locality, but still seems very trivial.) I'm struggling to understand the Legal FAQ any other way. Thanks.