Timeline for Amazon Echo/Dot on your network
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2017 at 18:56 | answer | added | Kamic | timeline score: 1 | |
| S Feb 27, 2017 at 18:48 | history | suggested | chicks | CC BY-SA 3.0 | spelling in title |
| Feb 27, 2017 at 18:18 | review | Suggested edits | |||
| S Feb 27, 2017 at 18:48 | |||||
| Feb 27, 2017 at 13:51 | history | tweeted | twitter.com/StackSecurity/status/836212143078924289 | ||
| Feb 25, 2017 at 0:35 | comment | added | JesseM | Points 5 and 6 are partially incorrect about "always listening and sending data back to amazon." The "always listening" part is limited to local hardware trying to detect the activation phrase. Once activated, then further audio data is sent back to Amazon. Point 3 can be addressed with the addition of purchase PIN to authorize the purchases. | |
| Feb 24, 2017 at 15:11 | comment | added | orion3999 | Patching and updating is done by amazon, with no control from us. as we do not have access to the data, it does not fit in with our data storage/legal requirements. the device is personally owned, so I would guess that it would be the owner of Echo/Dot's personal account. | |
| S Feb 23, 2017 at 19:29 | history | suggested | iainpb | removed csp tag | |
| Feb 23, 2017 at 18:33 | comment | added | iainpb | You may also consider how you manage patching / updating the device and data storage - your data is shuffled off to Amazon for processing, how does that fit with your data storage / legal requirements and then finally who has acess to amazon accounts linked to it | |
| Feb 23, 2017 at 18:31 | review | Suggested edits | |||
| S Feb 23, 2017 at 19:29 | |||||
| Feb 23, 2017 at 15:03 | review | First posts | |||
| Feb 23, 2017 at 15:31 | |||||
| Feb 23, 2017 at 15:02 | history | asked | orion3999 | CC BY-SA 3.0 |