83 lines
7.8 KiB
HTML
83 lines
7.8 KiB
HTML
<html><body><style>
|
|
* {
|
|
font-family:sans-serif;
|
|
}
|
|
body {
|
|
text-align:center;
|
|
padding:1em;
|
|
}
|
|
.messages {
|
|
width:100%;
|
|
max-width:700px;
|
|
text-align:left;
|
|
display:inline-block;
|
|
}
|
|
.messages img {
|
|
background-color:rgb(248,244,240);
|
|
width:36px;
|
|
height:36px;
|
|
border-radius:0.2em;
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
margin-right:0.65em;
|
|
}
|
|
.messages .time {
|
|
display:inline-block;
|
|
color:rgb(200,200,200);
|
|
margin-left:0.5em;
|
|
}
|
|
.messages .username {
|
|
display:inline-block;
|
|
font-weight:600;
|
|
line-height:1;
|
|
}
|
|
.messages .message {
|
|
display:inline-block;
|
|
vertical-align:top;
|
|
line-height:1;
|
|
width:calc(100% - 3em);
|
|
}
|
|
.messages .message .msg {
|
|
line-height:1.5;
|
|
}
|
|
</style><div class="messages"><div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-16 03:03</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-17 01:16</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-04-17/348134203537_1bc2a6f28471cf6ec828_72.png" /><div class="message"><div class="username">hutch</div><div class="time">2018-04-17 04:04</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 09:02</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-08-14 09:02</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-13/329132457109_199841cd908ca7faa97f_72.jpg" /><div class="message"><div class="username">rachel</div><div class="time">2018-08-14 09:02</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/411838218004_c7eba2c8e4f6b1a5ba77_72.png" /><div class="message"><div class="username">graeme</div><div class="time">2018-08-14 09:02</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-06-13/382065868838_3c9e05c4abd3cc1c0552_72.png" /><div class="message"><div class="username">obi</div><div class="time">2018-08-14 09:02</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 09:56</div><div class="msg">Last week we had a call on:
|
|
- UXifying our privacy policy
|
|
- Integrating our Terms and Conditions in the app flow
|
|
|
|
Here's a break down of features/architectural decisions and how their Terms and Conditions might be integrated in the app flow.
|
|
<a href="https://docs.google.com/spreadsheets/d/1YHPO5mnS6cfkBzDxJI7y9MhKgxM_MXTqC6JdoctJaWA/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1YHPO5mnS6cfkBzDxJI7y9MhKgxM_MXTqC6JdoctJaWA/edit?usp=sharing</a>
|
|
|
|
*TL;DR*
|
|
We need some more information about the effect of features. Especially on the level of control; Does the user opt-in/opt-out once? Is it session-based? Can it be altered in Profile? Is it possible to opt-out at all or does that equal uninstalling the app?
|
|
|
|
Assessment below is to give users more control than an _ACCEPT ALL_ during onboarding. Level of control can obviously be discussed.
|
|
|
|
*Assessment*
|
|
- People need to `OPT-IN/OPT-OUT` of 2 items during `ONBOARDING` (Status Whisper Mailservers and Instabug) > `we can decide to offer less control and provide only ACCEPT`
|
|
- People need to `ACCEPT` 1 item during `ONBOARDING` (Infura) (+Testfairy for nightly users only)
|
|
- People need to be `NOTIFIED` of 1 item during `ONBOARDING` (Testflight or Google Play Beta Testing); assuming acceptance is handled on the OS level.
|
|
- People need to `OPT-IN/OPT-OUT` of at least 2 items during `WALLET ONBOARDING` (Cryptocompare, Etherscan)
|
|
- People need to `ACCEPT` ERC721 assets (Collectibles)) and Web3 Browser Terms and Conditions `UPON USE`
|
|
- People need to `ACCEPT` Camera permission request `UPON USE`; assuming this is handled on OS level</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 10:01</div><div class="msg">@hester set the channel purpose: Integrating Terms and Conditions and our Privacy Policy into the Core app.
|
|
|
|
<a href="https://www.iubenda.com/privacy-policy/45710059">https://www.iubenda.com/privacy-policy/45710059</a>
|
|
<a href="https://discuss.status.im/t/mobile-app-privacy-policy/190">https://discuss.status.im/t/mobile-app-privacy-policy/190</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 10:03</div><div class="msg">@chad @graeme @rachel @obi What do you see as the best way forward?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/411838218004_c7eba2c8e4f6b1a5ba77_72.png" /><div class="message"><div class="username">graeme</div><div class="time">2018-08-14 11:17</div><div class="msg">quick question on this, if a user opted out of mailserver, then they would not be able to send/recieve messages on chat?</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/411838218004_c7eba2c8e4f6b1a5ba77_72.png" /><div class="message"><div class="username">graeme</div><div class="time">2018-08-14 11:21</div><div class="msg">think this ties to your point about needing more info, I have a chat based meeting with @andreap tomorrow and will ask</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 11:35</div><div class="msg">~Awesome, thanks @graeme. Indeed, I'm not sure about the workings of the mailserver. I can imagine it might be possible to send a message without the Mailserver, but not to view any prior messages. I can also imagine the mailserver is essential because the initial key exchange is a message and not having access to this history would also mean not having access to any contacts to send a message to.~
|
|
|
|
Actually, I'll add it to the #core-chat sync agenda. Will you join? It's in 25 min.</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-08-07/411838218004_c7eba2c8e4f6b1a5ba77_72.png" /><div class="message"><div class="username">graeme</div><div class="time">2018-08-14 11:59</div><div class="msg">Yup see you there</div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2017-12-12/285244060371_dbc007c8c7963b36a3ee_72.jpg" /><div class="message"><div class="username">hester</div><div class="time">2018-08-14 13:52</div><div class="msg">Details on Mailserver: <a href="https://status-im.slack.com/archives/C9B1T4B9B/p1534252058000100">https://status-im.slack.com/archives/C9B1T4B9B/p1534252058000100</a></div></div></div><br/>
|
|
<div><img src="https://avatars.slack-edge.com/2018-03-06/324554464353_18f48763243f656a4978_72.jpg" /><div class="message"><div class="username">patrick771</div><div class="time">2018-08-23 11:42</div><div class="msg">has joined #privacy</div></div></div><br/>
|
|
</div></body></html> |