njsmith
added draft pp
Can we say something like we'll hash the identifier? this way we really can't tie it back to an individual person? we can has the IP or the MAC address or something. Unless we plan to ping the IP to get a geographic location
Can we say something like we'll hash the identifier?
The IP is logged by the webserver, there is no really point in hashing it. It's not collected by our system. the unique identifier will likely be a UUID, there is no real point in hashing a UUID.
Updated the language to reflect the IP address consideration and UUIDs.
Also, I think that any IP pinging or location reporting will have to be done client-side. While this is more work for the client to do, it alleviates the need to store anything personally identifiable.
Looks really great!
The only thing I'd add in is a bit more on the why IP addresses are collected server side - for server operations, debugging, etc. The IP Address is shared to a server no matter what, as you can't network without it. ;)
Read that section and wondered what the provisions of standard server log were to people not used to working with servers. Maybe that doesn't matter.