Good question. We don't. We simply forgot to remove it when porting our chrome extension. Will be gone in the next update! Thanks for pointing that out.

*Update: The permission is now gone.