LeadQC by Zeplinixby Zeplinix
Security & data handling

Your files are production data.
We treat them that way.

Your files stay yours. Every record you upload is a real prospect and a real relationship. SOC 2-aligned controls, built for production data. This page explains how LeadQC handles it.

Last reviewed 12 Nov 2026 · Questions: hello@zeplinix.com

  • Encryption in transit
  • Encryption at rest
  • Workspace isolation
  • DPA available
  • Retention controls
  • No training on customer files
  • Auditability
  • Explainable QC decisions

How your data moves
through LeadQC.

Four stages. One workspace, yours. Nothing leaves it except the three files you download.

  1. 01 · UploadInside the authenticated product

    Files are uploaded in your LeadQC workspace after login, never through a public form or email. Your workspace is isolated from every other customer.

  2. 02 · ProcessLive checks, corrections, enrichment, your rules

    Records are re-checked against current signals, corrected and enriched, then qualified against the QC rules you configured. Every decision is logged with its reason.

  3. 03 · DeliverThree files back to you

    The error file, the corrected + enriched file and the GTM-ready file are produced for your workspace only. Nothing is shared, pooled or resold.

  4. 04 · Retain, then delete90 days, or sooner on request

    Uploaded data and outputs are retained for 90 days so you can re-download them, then permanently deleted. Ask and we delete earlier.

What we do with your data.
What we never do.

We do
  • Run live validation, correction, enrichment and qualification on the records you upload. That is the only purpose we process them for
  • Keep your outputs available for 90 days so your team can re-download them
  • Log every processing decision so results are auditable and explainable
  • Count how many records each run processed, so usage and billing are accurate. Counts only, never the contents
  • Encryption Data is encrypted in transit (TLS) and at rest. Credentials and keys are kept out of the codebase and web root.
  • Access control Internal access to customer workspaces is least-privilege, limited to operating the service, and reviewed.
  • Workspace isolation Each customer's files, rules and outputs live in their own workspace. There is no shared record pool.
  • Auditability Every rejection, correction and quality decision carries its reason in the outputs. Nothing disappears inside a black box.
  • Retention & deletion 90-day retention for re-download, then permanent deletion. Earlier deletion on request, confirmed in writing.
  • DPA & sub-processors A Data Processing Agreement and the current sub-processor and hosting details are available on request before any production file moves.
We never
  • Train models on your files
  • Sell, share, resell or pool your data
  • Use your prospects for our own outreach
  • Mix your workspace with another customer's
  • Keep files past the retention window without your instruction
  • Accept production files through this website

SOC 2-aligned controls. Certification not claimed.

Don't take this page's word for it either.
Ask.

Before production data moves, request the DPA, the sub-processor and hosting details, and a walkthrough of the controls. Published privacy policy, terms and GDPR statement. If you find a security issue, tell us first.