Skip to content

Commit

Permalink
add privacy controls
Browse files Browse the repository at this point in the history
  • Loading branch information
cpholguera committed Jan 18, 2024
1 parent e971590 commit 707f046
Show file tree
Hide file tree
Showing 4 changed files with 42 additions and 0 deletions.
13 changes: 13 additions & 0 deletions controls/MASVS-PRIVACY-1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# MASVS-PRIVACY-1

## Control

The app minimizes access to sensitive data and resources.

## Description

Apps should only request access to the data they absolutely need for their functionality and always with informed consent from the user. This control ensures that apps practice data minimization and restricts access control, reducing the potential impact of data breaches or leaks.

Furthermore, apps should share data with third parties only when necessary, and this should include enforcing that third-party SDKs operate based on user consent, not by default or without it. Apps should prevent third-party SDKs from ignoring consent signals or from collecting data before consent is confirmed.

Additionally, apps should be aware of the 'supply chain' of SDKs they incorporate, ensuring that no data is unnecessarily passed down their chain of dependencies. This end-to-end responsibility for data aligns with recent SBOM regulatory requirements, making apps more accountable for their data practices.
11 changes: 11 additions & 0 deletions controls/MASVS-PRIVACY-2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# MASVS-PRIVACY-2

## Control

The app prevents identification of the user.

## Description

Protecting user identity is crucial. This control emphasizes the use of unlinkability techniques like data abstraction, anonymization and pseudonymization to prevent user identification and tracking.

Another key aspect addressed by this control is to establish technical barriers when employing complex 'fingerprint-like' signals (e.g. device IDs, IP addresses, behavioral patterns) for specific purposes. For instance, a fingerprint used for fraud detection should be isolated and not repurposed for audience measurement in an analytics SDK. This ensures that each data stream serves its intended function without risking user privacy.
9 changes: 9 additions & 0 deletions controls/MASVS-PRIVACY-3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# MASVS-PRIVACY-3

## Control

The app is transparent about data collection and usage.

## Description

Users have the right to know how their data is being used. This control ensures that apps provide clear information about data collection, storage, and sharing practices, including any behavior a user wouldn't reasonably expect, such as background data collection. Apps should also adhere to platform guidelines on data declarations.
9 changes: 9 additions & 0 deletions controls/MASVS-PRIVACY-4.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# MASVS-PRIVACY-4

## Control

The app offers user control over their data.

## Description

Users should have control over their data. This control ensures that apps provide mechanisms for users to manage, delete, and modify their data, and change privacy settings as needed (e.g. to revoke consent). Additionally, apps should re-prompt for consent and update their transparency disclosures when they require more data than initially specified.

0 comments on commit 707f046

Please sign in to comment.