Privacy Policy

Information we collect

When you sign in, DirtIQ processes your email address to confirm your identity and provide access to an authorized workspace. Security records may include the sign-in method, outcome, time, requested public route, browser user-agent, and a limited authentication failure category. Verification codes and session tokens are not written to the app's sign-in history.

If you use a workspace, DirtIQ processes account and company information, parcel records, source references, tasks, notes, and review decisions needed to provide the service. The public explorer uses aggregate market information and does not send individual parcel details, owner data, tax values, or source URLs to the browser.

Site measurement records public page views, public explorer visits, sign-in starts and completions, journal article reads, demo-request clicks, and builder-interest form starts and completions. The separate funnel events record builder-interest views, successful builder submissions, and successful ZIP-brief signups with only a page path and event timestamp. They contain no form values, email addresses, selected ZIP fields, or IP-derived identity. Page-view measurements may include a coarse mobile/desktop category, referring site origin, and load time; they do not include full referrer paths.

Owner inquiries

If you submit a lot-owner inquiry, DirtIQ collects your name, email address, the property's street address and ZIP code, your contact consent, and the submission time. Phone, city, preferred contact method, and message are optional. The source page is recorded to understand which public page led to the inquiry.

Inquiry details are used to review and respond to your request. They are not published as a listing, public explorer result, valuation, or offer, and are not routed to a builder client. Within the app, access is limited to DirtIQ administrators and an authenticated DirtIQ user specifically assigned to the inquiry. Inquiry details are not included in public analytics.

A short-lived HMAC-derived network identifier may be held in server memory to limit repeated submissions. The raw network address and that identifier are not written to the inquiry record.

Builder requests

If you submit a builder-interest request, DirtIQ collects your name, company, email, optional phone, target ZIPs, portfolio size, contact consent, optional message, submission time, and source page. Builder requests are stored privately and separately from lot-owner requests.

Individual builder request details are not published or rendered, and private records are not read or counted by public pages. Separate allowlisted analytics events count only form starts and completions; they include no submitted form values or contact details. Access is restricted to the authorized DirtIQ operator; the public site has no read path for these records. Registering interest is not a scheduled demo, territory reservation, waitlist priority, or license.

A short-lived HMAC-derived network identifier may be held in server memory to limit repeated submissions. The raw network address and that identifier are not written to the inquiry record.

ZIP brief subscriptions

If you request a ZIP brief, DirtIQ collects your email address, selected ZIP, contact consent, submission time, source page, and subscription status. These details are stored in a private subscriber table; subscriber records and counts are not rendered or counted on public pages.

ZIP briefs come from zips@dirtiq.tech when that ZIP's data updates; no fixed send schedule is promised. To unsubscribe at any time, email zips@dirtiq.tech and DirtIQ will update the private subscription status. A short-lived HMAC-derived network identifier may be held in server memory to limit repeated signups; neither the raw network address nor that identifier is written to subscriber or funnel-event records.

How we use information

We use account information to authenticate authorized users, protect company-scoped workspaces, maintain security records, and operate DirtIQ. Aggregate site measurements help us understand whether public pages and key visitor flows are working. We use lot-owner inquiry details only to review and respond to the inquiry, builder inquiry details only to review and respond to builder requests, and ZIP brief subscriber details only to send the requested ZIP brief and process unsubscribe requests.

Sale and service providers

DirtIQ does not sell personal information. Information is processed by the hosting, authentication, and data services needed to operate the app. When configured, the email delivery provider processes builder request details to send the requested notification to DirtIQ and subscriber email addresses to deliver requested ZIP briefs. Access to workspace records is subject to company and account permissions.

Cookies and measurement

The app uses a session cookie to keep an authorized user signed in. The public measurement endpoint is first-party and does not use advertising cookies. You can block cookies in your browser, but workspace sign-in will not function without the session cookie.

Account access and deletion requests

DirtIQ access is granted by an account or company administrator. To close your account or request access to or deletion of account information, contact DirtIQ LLC at zips@dirtiq.tech. For company workspace records, contact the administrator who granted your access so shared parcel research can be reviewed separately.

Contact

Questions about this policy or your information: contact DirtIQ LLC at zips@dirtiq.tech.