Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purpose strings #183

Open
sheenhx opened this issue Apr 9, 2024 · 3 comments
Open

Purpose strings #183

sheenhx opened this issue Apr 9, 2024 · 3 comments
Assignees

Comments

@sheenhx
Copy link
Contributor

sheenhx commented Apr 9, 2024

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
5.1.1(ii) Permission Apps that collect user or usage data must secure user consent for the collection, even if such data is considered to be anonymous at the time of or immediately following collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s GeneralData Protection Regulation ("GDPR") or similar statute must comply with all terms of that law.

Issue Description

One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used.

Examples of unclear purpose strings:

  • "App would like to access your Contacts"
  • "App needs microphone access"

Next Steps

Update the location purpose string to explain how the app will use the requested information and provide an example of how the data will be used. See the attached screenshot.

Resources

Support

@sheenhx sheenhx assigned sheenhx and reasje and unassigned sheenhx Apr 9, 2024
@sheenhx
Copy link
Contributor Author

sheenhx commented Apr 9, 2024

compile a 2.3.5 to resubmit @SanghamitraBhowmick1993

@reasje
Copy link
Contributor

reasje commented Apr 10, 2024

So far

  1. I have updated the purpose string for IOS permissions
  2. Also I was able to confirm that IOS webview permission request is working so I removed the permission request before opening any DApp
  3. The IOS 2.3.5 looks ready for submitting request
  4. I have checked Recent IOS Review but I was not able to reproduce the bug with devices they mentioned
  5. Android webview does not work properly like IOS does, meaning It does not request permission, I am checking that.

@reasje
Copy link
Contributor

reasje commented Apr 10, 2024

@sheenhx I was not able to solve the permission request in Android, According to docs we need to get the permission before using It in webview ref.
So on Android we will get permission before opening DApps but on IOS we will get permission inside DApps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants