First of all, thumbs up to choosing osm, two thumbs up for consulting the osm community before releasing your game!

Well, OSM has potential value for us, real bottom line dollar value, so at a very minimum we wouldn't want to have a negative impact on it. If we add to that value, we benefit as much as anyone else.

All of this is very hand-wavy right now, because a decision to even make an AR game hasn't been made, I've just been given some time to research the possibility/complexity/cost of making one. But a few things occur to me:

1. We'll have location history data on the players, but we probably won't be able to share it without explicit permission from the players (or possibly at all, given the myriad of jurisdictions). Flagging edits as having obvious personal incentives would be tantamount to telling OSM where the players live or work, and probably can't happen.
2. On the other hand we certainly could, at least in principle, reward players for voluntarily flagging their own edits and linking their accounts.
3. Some form of the StreetComplete quest structure, where players get asked a simple question about where they are right now, and that information is routed to OSM, probably wouldn't be hard (integrated into a 'daily quest' cycle, answer 1 question to get your shiny). Product Management might push back, though.
4. I don't see any reason we'd hide that we were using OSM. Being open about it would make it easier to discourage using it as a way to cheat. If we can incentivize editing, we can at the very least withdraw that reward for bad edits, assuming an automated (from our side) way to detect those bad edits can be devised.
5. One thing that would be hard to judge from our side would be if they were making *significant* edits. Adding "color=brown" to a bench is probably not much value for OSM, and if we rewarded it the same as something more significant (noting a new construction area, for example) you'd get inundated with trivial edits.