Skip to content

[DOCS] Data privacy #29

@lmeyerov

Description

@lmeyerov

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) 

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions