Best way to handle latitude, longitude data

[j0x0j]

Problem

The latlng (latitude, longitude) parameter is passed in plain text to the newPolicy method HurricaneGuardNewPolicy.sol#L80 and saved to the Database Contract HurricaneGuardDatabase.sol#L147. This may be considered personally identifiable information, it should not be public.

Possible Solutions

• Use Oraclize Encrypted Queries
  Solves the transit problem but still saves the the plain bytes in the Database Contract
• Encrypt the parameter off-chain.
  Does the API server hold the private key? What happens when a user interacts directly with the contract using meta mask, do we encrypt in the front end using a public key?
• Don't save latlng in Database Contract?