ngn/libremdb
1
0
Fork 0
Code Issues 1 Pull Requests 10 Actions Packages Activity
libremdb/views/pug/privacy.pug

19 lines
1.5 KiB
Plaintext
Raw Normal View History

initial commit
2022-03-19 17:22:07 +05:30
extends base
block content
main.main.privacy
h1.heading.heading__primary.privacy__heading Privacy Policy
docs: update privacy section having heroku's potential logging advisory across instances' webpages(where instances might not be even using heroku) isn't ideal. So, rephrased the privacy/faq sections in README as well as on the webpage.
2022-06-04 04:05:32 +05:30
p.privacy__jist In short: libremdb doesn't collect any personally identifiable data at all.
initial commit
2022-03-19 17:22:07 +05:30
.privacy__item
docs: update privacy section having heroku's potential logging advisory across instances' webpages(where instances might not be even using heroku) isn't ideal. So, rephrased the privacy/faq sections in README as well as on the webpage.
2022-06-04 04:05:32 +05:30
h2.heading.heading__secondary.privacy__item-heading Data you directly provide
initial commit
2022-03-19 17:22:07 +05:30
p.privacy__item-text None.
.privacy__item
docs: update privacy section having heroku's potential logging advisory across instances' webpages(where instances might not be even using heroku) isn't ideal. So, rephrased the privacy/faq sections in README as well as on the webpage.
2022-06-04 04:05:32 +05:30
h2.heading.heading__secondary.privacy__item-heading Data you passively provide
p.privacy__item-text A stack trace is logged to console on the server if you hit some error route.
initial commit
2022-03-19 17:22:07 +05:30
.privacy__item
h2.heading.heading__secondary.privacy__item-heading Data stored in your browser
p.privacy__item-text To remember theme preferences, the website stores a key named 'theme' in Local Storage provided by your browser. Apart from that, there is nothing stored in your browser. To remove the key, press F12 > Storage(or Application in chromium-based browsers) > Local Storage > right click > Delete.
docs: update privacy section having heroku's potential logging advisory across instances' webpages(where instances might not be even using heroku) isn't ideal. So, rephrased the privacy/faq sections in README as well as on the webpage.
2022-06-04 04:05:32 +05:30
p.privacy__item-text To permamently disable libremdb from storing your theme prefrences, either turn off JavaScript or disable access to Local Storage for libremdb.
.privacy__item
h2.heading.heading__secondary.privacy__item-heading Data collected by other services
p.privacy__item-text libremdb connects to 'm.media-amazon.com' for fetching images. So, Amazon might log your IP address. If you use the official instance which is deployed on Heroku, then Heroku might also log you IP address. You're advised to follow due precaution.
Reference in New Issue Copy Permalink