2 ms·

Hopefully we're not talking health/medical IoT devices. If that's the case, please hire a consultancy to help along. > How should I design my services/infrastr

by atmosx 8y ago

Hopefully we're not talking health/medical IoT devices. If that's the case, please hire a consultancy to help along. > How should I design my services/infrastructure to be able to easily retrieve all personal information related to a user? Details depend on implementation. Might be just a simple API/DB call or more. IIRC your DB data should be encrypted, RDS supports encryption at rest out of the box. > Are the data points collected by the sensors considered personal information (and thus must be deleted when the user terminate its account)? If, by retrieving them, a user can be identified then yes. Can you use an UUID and control the info on the AWS side? A common pattern is to use an envelop encryption scheme (like KMS for instance) and instead of actually deleting the data, you delete the key. This way, the data cannot be decrypted and is considered lost/deleted. Special care should be taken in order to design your DB in a way to support deletion and data retrieval.

Sytten 8y ago
Not not medical. > Details depend on implementation. Might be just a simple API/DB call or more. IIRC your DB data should be encrypted, RDS supports encryption at rest out of the box. Make sense, but it's more the scaling of this concept that worries me (when you start to have multiple services and DBs). It's easy to forget one API call. > If, by retrieving them, a user can be identified then yes. Can you use an UUID and control the info on the AWS side? Points will be linked to a user via a UUID yes, but (for example) is the temperature of the room at time X considered personal data? I like this idea. Downside is that if you want to view the data to debug a problem in production, it's harder.
- atmosx 8y ago
  > [...] is the temperature of the room at time X considered personal data? Temperature alone doesn't say much. By comparison an email address can lead to a specific person.

by atmosx 8y ago

Sytten 8y ago

Not not medical. > Details depend on implementation. Might be just a simple API/DB call or more. IIRC your DB data should be encrypted, RDS supports encryption at rest out of the box. Make sense, but it's more the scaling of this concept that worries me (when you start to have multiple services and DBs). It's easy to forget one API call. > If, by retrieving them, a user can be identified then yes. Can you use an UUID and control the info on the AWS side? Points will be linked to a user via a UUID yes, but (for example) is the temperature of the room at time X considered personal data? I like this idea. Downside is that if you want to view the data to debug a problem in production, it's harder.

atmosx 8y ago
> [...] is the temperature of the room at time X considered personal data? Temperature alone doesn't say much. By comparison an email address can lead to a specific person.