Zingg-0.3.3
  • Welcome to Zingg
  • Step By Step Guide
    • Installation
      • Working with Docker Image
    • Hardware Sizing
    • Configuration
    • Creating training data
      • findTrainingData
      • label
      • findAndLabel
      • Using preexisting training data
      • Exporting labeled data as csv
    • Building and saving the model
    • Finding the matches
    • Linking across datasets
  • Data Sources and Sinks
    • Zingg Pipes
    • Snowflake
    • Cassandra
    • MongoDB
    • Neo4j
    • Parquet
  • Running Zingg on Cloud
    • Running on AWS
    • Running on Azure
    • Running on Databricks
  • Zingg Models
    • Pretrained models
  • Improving Accuracy By Defining Own Functions
  • Generating Documentation
  • Output Scores
  • Security And Privacy
  • Updating Labeled Pairs
  • Reporting bugs and contributing
  • Community
  • Frequently Asked Questions
  • Reading Material
Powered by GitBook
On this page

Security And Privacy

Zingg models are built on your data, deployed within your network. No data leaves your environment.

However, Zingg does collect usage metrics and writes it to Google Analytics. This is done to understand and improve user experience. Please be assured that Zingg does not capture any user data or input data and will never do so.

The following details are captured:

  • Data source type: type of data format e.g. csv, snowflake

  • Fields count: number of fields used for training

  • Total Data count: for match phase, number of total records

  • Execution Time: execution time of the program

  • Matched and Nonmatched records count: for train phase, number of matched and nonmatched records

If you do not wish to send this data, please set collectMetrics flag to false in the configuration json while running Zingg.

No usage data is being collected in the 0.3.0 release

PreviousOutput ScoresNextUpdating Labeled Pairs

Last updated 2 years ago