Today’s digitally connected world relies on secure data transmission and lawful data management. That’s why companies need to disclose how they get their data, how it is used, and the impact it can have on communities. At `Where` we are, our goal is to be leaders in transparent data creation, transfer, and storage.
At `Where`, we handle different types of data; in this article, we’ll outline how `Where` creates address data.
`Where` Address
An address is composed of several key elements, including the:
- Number
- Street name
- Region
- County
These elements help uniquely identify a location within a mapped region. For mapping purposes, each address also contains:
- Latitude
- Longitude
These values are captured using a GNSS receiver outside the property being assigned an address.
Below is an example of a `Where` address:
16 Where Road, Roysambu, Nairobi County
This is address number 16, located on the left side of Where Road in Roysambu region in Nairobi county. Each address is generated automatically based on the location and the number of addresses before it if there is one.
Is an Address Personal Data?
To answer this question, we’ll define personal data. According to GDPR, personal data is any information that is related to an identified or identifiable natural person.
So, an address on its own is not personal data as it is information related to a location, not a person.
However, if you add an address to a data set containing personal data, it becomes personal data. That’s because the address would then be linked to an identifiable natural person.
At `Where`, we only provide addresses that describe a location.
Public Place
Addresses are created by teams standing on public roads. They do not trespass or include any data beyond what is generated by the application and captured by a GNSS receiver.
Zero Tracking
A `Where` address is static and does not do any form of tracking. Once created, it is verified, encrypted, and stored.
Leave a Reply