Legal

Privacy Policy

How Ziplytica handles platform, billing, enrichment, and operational data in the live application environment.

Last updated: October 15, 2026

Overview

This Privacy Policy describes how Ziplytica, Inc. ("Ziplytica," "we," "us") collects, uses, stores, and shares information when you use our platform, including territory access, lead workflows, billing, and contact-enrichment features.

Ziplytica provides business software to authorized brokerage teams. This policy is not legal advice. Where this policy conflicts with a signed order form or master services agreement, the signed agreement controls.

What We Collect

We collect account, authentication, usage, billing, territory, lead-workflow, and support data needed to operate the platform.

When contact enrichment is used, we may collect and store request metadata, provider request identifiers, returned contact fields, confidence or quality indicators, compliance flags, operational logs, and credit or billing audit records tied to the requesting account and lead.

When customers upload or enter property-owner lists, we collect the records they provide, which may include owner names, property and mailing addresses, phone numbers, and email addresses.

We may also collect device, browser, cookie, and analytics data consistent with our cookie and analytics practices.

Third-Party Data Providers and Subprocessors

Ziplytica uses third-party vendors to provide infrastructure, payments, analytics, email delivery, contact enrichment, and direct-mail fulfillment. Those vendors process data on our behalf or under separate contractual terms governing their data products.

Contact enrichment and outreach fulfillment may be provided through Tracerfy, FastAppend, Lob. Enrichment data may be derived from public records, licensed third-party sources, and provider-maintained suppression or compliance files.

Platform infrastructure subprocessors include Stripe, Supabase, Vercel. These vendors support authentication, database storage, payments, hosting, and operational reliability.

We share with enrichment and fulfillment providers only the minimum information required to perform a lookup or send, such as property address, owner or entity name, lead identifiers, mail recipient details, and account context needed for billing and audit.

We may update subprocessors from time to time. Material changes will be reflected in this policy or in customer notices where required by law or contract.

How Enrichment Data Is Used

Enrichment data is used to return contact results to authorized users, reconcile credits, investigate provider or infrastructure incidents, and maintain audit records.

Contact information obtained through enrichment or provided by customers is maintained in our property-owner records and may be made available to other authorized customers through the platform, including without a new provider lookup. We do not identify which customer provided a record.

Returned contact data is provided on a best-effort basis and may be incomplete, stale, or inaccurate. Ziplytica does not use enrichment results to establish consent for calls, texts, emails, or automated outreach.

Enrichment data is licensed for use inside the Ziplytica platform under your agreement with us. It is not provided for resale, bulk export, database creation, or redistribution outside the platform except as expressly permitted in writing.

Controller Roles and Customer Responsibilities

For personal information processed through contact enrichment, Ziplytica and our data licensors generally operate as independent controllers or independent businesses, not as processors of one another, unless a separate data processing addendum says otherwise.

Your brokerage remains responsible for determining lawful bases, notices, and compliance for any outreach or downstream use of returned contact data, including TCPA, federal and state do-not-call rules, CAN-SPAM, privacy laws, fair-housing obligations, and anti-harassment laws.

A returned phone number or email does not establish permission to call, text, autodial, send ringless voicemail, or use automated outreach. You must maintain your own suppression, consent, and legal review processes before contact.

Prohibited and Restricted Uses

Enrichment data must not be used for consumer-report purposes under the Fair Credit Reporting Act, including employment screening, tenant screening, credit or insurance eligibility, or similar regulated decisioning.

You must not use enrichment data to stalk, harass, surveil, or locate covered persons protected by Daniel's Law or comparable statutes, or to violate anti-discrimination, fair-housing, or anti-stalking laws.

You must not train, fine-tune, benchmark, or feed enrichment data into AI or machine-learning systems except where expressly authorized by Ziplytica and applicable data licensors.

Suppression, Opt-Out, and Privacy Requests

Our providers maintain suppression, deletion, and compliance files that may affect whether contact fields are returned or displayed. You must honor suppression, opt-out, and takedown instructions applicable to your use of returned data.

If you receive a privacy, deletion, correction, opt-out, or do-not-contact request relating to data obtained through Ziplytica, notify us promptly at privacy@ziplytica.com or use the privacy request form on our site so we can coordinate with provider obligations.

We aim to acknowledge privacy requests within five business days and complete verified requests within thirty days unless applicable law requires a different timeline.

Data Retention

Property-owner records, including contact information obtained through enrichment or provided by customers, are retained for as long as they remain useful in providing the platform. We remove or suppress records in response to verified deletion, opt-out, and do-not-contact requests.

Account and profile information is retained while your account is active. After a verified account deletion request, we delete or de-identify it, except for records we must keep for billing, tax, security, fraud prevention, or other legal obligations.

Sign-in security records, such as IP address and device information, are retained for up to one year. Territory page-view records are retained for up to 180 days. Email delivery records, demo requests, market inquiries, closed territory waitlist entries, and support assistant transcripts (including a follow-up email address) are retained for up to two years.

Billing, credit, and audit records are retained as needed to support billing, fraud prevention, dispute resolution, and legal obligations.

Access Controls and Security

Enrichment results are returned only to authenticated users operating under an authorized account and territory context.

Operational logs, audit records, and support-alert records are restricted to personnel with a legitimate need to investigate billing, access, security, or incident issues.

We maintain administrative, technical, and organizational controls designed to protect platform data. No method of transmission or storage is completely secure.

Cookies and Analytics

We use cookies and similar technologies for authentication, session management, security, preferences, and product analytics.

Essential cookies and strictly necessary scripts — including sign-in session cookies, fraud-prevention captcha widgets (Cloudflare Turnstile, Google reCAPTCHA, or hCaptcha when enabled), and service-worker assets needed for core functionality — run without marketing consent.

Non-essential analytics identifiers and beacons are used only after you accept them in our cookie banner. You can reopen preferences from the site footer.

You can control cookies through browser settings, though disabling certain cookies may limit platform functionality.

Marketing Site Analytics

When you accept analytics cookies, we may collect page-path interest signals, anonymous session identifiers, referrer URLs, and coarse device or browser metadata to understand product demand and improve the marketing site.

On the territories browse experience, we may store an anonymous viewer key in local storage and record ZIP-level view events (including hashed IP and user-agent metadata) to display live competition indicators and measure market interest.

These records are used for product analytics, operational alerting, and aggregate reporting — not for third-party ad retargeting. Reject non-essential cookies to disable this collection.

Contact

For privacy, data-accuracy, or subprocessor questions, contact privacy@ziplytica.com or submit a request at /privacy/request.

Security incidents affecting platform data should be reported to security@ziplytica.com or /security/report without unreasonable delay.