[DOCS] Data privacy

Aberta
  • Algo errado?
#29 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
38/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Domínio
documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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)
Linguagem predominante
Shell
Estrelas
31
Forks
6
Nenhum PR com merge em 30d

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de graphistry/graphistry-cli

Todas as issues de graphistry/graphistry-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.