[DOCS] Data privacy

Aperta
  • Qualcosa non va?
#29 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
38/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Ambito
documentation

Direzione di ricerca

The issue asks for security documentation based on the Slack Q&A, but names no documentation file or test. First, inspect the repository’s existing documentation structure and identify where security and privacy information belongs. Document the described data handling and browser side disclosures accurately, and consider the work done when those points are clearly covered in the relevant docs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

docs

Document q/a from Slack:

Good questions, and I'm going to file a ticket to add to our security docs :slightly_smiling_face:
Our design is:
-- Self-managed (Docker): Graphistry sees nothing except ~annual billing information. For legal & ethical reasons, we either need to know who you are, or work through a trusted reseller.
-- Cloud Marketplaces (AWS/Az): AWS/Az send us billing reports such as account and utilization.
-- Graphistry Hub: We're built so contractors etc. cannot access production systems (e.g., cannot log into production servers + log into cloud admin panels), but devs can. We are actively hiring 2 people to help launch individual & team tiers, and ~half that work is about putting in privacy/sharing controls. If you care about tenant isolation etc, would actually welcome a conv on that, as we're planning the features for those 2 people!
An important issue for especially privacy sensitive users is the current browserside leaks usage information in 2 places. First, some of our JS dependencies loaded additional JS via CDNs, so we've worked with upstream maintainers to fix those, and the next release already removes all but one of those. Second, we had a leftover Google Analytics include (essentially just IP/URL), which we already removed for the next release as well -- it may already be gone on Hub, and I'm not sure if it ever went to Marketplace or Docker distros (requires a GA ID parameter). (edited)
Lingua principale
Shell
Stelle
31
Fork
6
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di graphistry/graphistry-cli

Tutte le issue di graphistry/graphistry-cli

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.