From 154bee6a6e89f9ca07e7915974c067ea74357239 Mon Sep 17 00:00:00 2001 From: Umputun Date: Tue, 5 Jun 2018 12:15:46 -0500 Subject: [PATCH] add privacy section to readme --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index a4cda8e2..3d8112eb 100644 --- a/README.md +++ b/README.md @@ -414,6 +414,22 @@ Sort can be `time`, `active` or `score`. Supported sort order with prefix -/+, i _all admin calls require auth and admin privilege_ + +## Privacy + +* Remark42 is trying to be very sensitive to any private or semi-private information. +* Authentication requesting the lowest (minimal) possible scope from providers. All extra information returned by them dropped immediately and not stored in any form. +* Generally remark42 keeps user id, username and avatar link only. None of these fields exposed directly - id and name hashed, avatar proxied. +* There is no tracking of any sort. +* Login mechanic uses JWT stored in a cookie (httpOnly, secured). The second cookie (XSRF_TOKEN) is a random id preventing Cross-Site Request Forgery +* There is no cross-site login, i.e., user's behavior can't be analyzed across independent sites running remark42. +* There are no third-party analytic services involved. +* User can request all information remark42 knows about and export to gz file. +* Supported complete cleanup of all information related to user activity. +* Cookie lifespan can be restricted to session-only +* All potentially sensitive data stored by remark42 hashed and encrypted. + + ## Technical details * Data stored in [boltdb](https://github.com/coreos/bbolt) (embedded key/value database) files under `BOLTDB_PATH`