Page MenuHomePhabricator

[Cashtab] Add privacy policy
ClosedPublic

Authored by bytesofman on Feb 25 2022, 21:38.

Details

Reviewers
emack
Group Reviewers
Restricted Project
Commits
rABCc4fefd9248fc: [Cashtab] Add privacy policy
Summary

T2270

Google chrome store requires extensions to have a privacy policy for approval.

This diff creates a privacy policy accessible by a URL in Cashtab. It also adds a link to this policy from the Settings page (Configure.js)

Test Plan

npm start
Navigate to settings, click privacy policy link at bottom, confirm privacy policy is displayed
Navigate to localhost:3000/#/privacy, confirm privacy policy is displayed
Open an incognito window and navigate to localhost:3000/#/privacy and ensure privacy policy is displayed (and menu is not, as no wallet has been created)
Test in extension (just as a link from the settings page)

Diff Detail

Repository
rABC Bitcoin ABC
Branch
add-privacy-policy
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 18367
Build 36536: Build Diffcashtab-tests
Build 36535: arc lint + arc unit

Event Timeline

emack requested changes to this revision.Feb 26 2022, 02:29
emack added a subscriber: emack.

I don't think this is going to fly with Google. I did something similar years ago when publishing a VR app and it got tangled in the review process for a long time because the publication review team took exception to the effort.

At a minimum, a privacy policy will need to cover:

  • the entity issuing the privacy policy
  • what info do we collect from users
  • how do we collect this info from users
  • how we intend to use this information
  • contact point if the user has further privacy related queries

I suggest the following as a start but can we get someone on the team with a legal background to canvas this?


Cashtab Privacy Policy

Bitcoin ABC (insert legal entity) attaches significant importance to the privacy protection of you (or referred to as “you” or “user”). When you use the Cashtab web application, we will collect, use, and protect the Google Analytics information in accordance with this privacy policy (the “Policy”).

This policy can be updated by Bitcoin ABC at any time. If you do not accept the policy, please stop using Cashtab immediately. If you continue to use Cashtab, we will deem it as accepting the policy. Once a revised policy is published on the Cashtab website, it will automatically take effect immediately. We encourage you to review our privacy policies each time you visit Cashtab.

1. What kind of information do we collect from you?

Cashtab uses Google Analytics to track aggregated internet traffic data to https://cashtab.com in order to support the continuous improvements to the web application. Cashtab does not collect any personal information from you.

When you create or import a wallet on Cashtab, your mnemonic seed, biometrics data, transaction history and so on are stored only on your device and are not stored on our server.

2. How do we collect this information from you?

Google Analytics acquires user data from each website visitor through the use of page tags. A JavaScript page tag is inserted into the code of each page. This tag runs in the web browser of each visitor, collecting data and sending it to one of Google's data collection servers. Google Analytics can then generate customizable reports to track and visualize data such as the number of users, bounce rates, average session durations, sessions by channel and page views.

3. How is your information managed?

Please refer to Google's Privacy Policy on how analytics data is stored via Google Analytics as Cashtab does not store any of this data.

4. How do we use your information?

The aggregated reports generated by Google Analytics allow the Cashtab team to assess the popularity of various features in Cashtab and inform on future user experience design decisions.

5. Further questions

If you have any further privacy related queries please feel free to reach out to us on (insert general bitcoinabc email).

This revision now requires changes to proceed.Feb 26 2022, 02:29
This revision is now accepted and ready to land.Feb 26 2022, 14:33
This revision was automatically updated to reflect the committed changes.