Oky

A grid will be shown here for Oky’s progress to becoming a DPG.

Req. #
Indicator
Status
Evidence
1
Relevance to Sustainable Development Goals
2
Use of Approved Open Licenses
3
Clear Ownership
4
Platform Independence
not applicable
5
Documentation
6
Mechanism for Extracting Data
All non-PII data is stored in a postgress SQL database and can be exported in standard CSV or SQL statement formats on demand. However, Oky has strict data governance processes in place, and access is very restricted.
7
Adherence to Privacy and Applicable Laws
8
Adherence to Standards & Best Practices
REST, JSON, CSV. GitHub
9
Do No Harm by Design
The Oky app has been designed with very high privacy settings, to protect users. We do not hold in our database any personally identifiable data. While user-generated fields at time of registration (username, password, secure answer) are not able to identify an individual, as part of Oky’s strict data governance approach, Oky hashes and salts these fields to render the original values inaccessible. This hashing approach is used with the purpose to: (a) obfuscate the username to anyone who might access the database, and (b) to guarantee user authentication, ie. to allow users to log into their account on the same device or a different device.
9a
Data Privacy & Security
not applicable
9b
Inappropriate & Illegal Content
not applicable
9c
Protection from Harassment
not applicable