Source and lifecycle disclosure
Data Practices
How DealSkeptic selects fields, describes coverage, retains report evidence, and responds when source permission changes.
Selected-field approach
DealSkeptic queries property, permit, tax, spatial, environmental, and jurisdiction records only for an individual property review. Adapters retain selected report fields rather than raw datasets. Natural-person and contact fields are excluded, and the product offers no CSV, bulk JSON, GIS, or raw-source download. We do not resell source datasets.
Coverage meanings
- Success
- The named source returned usable evidence for this request.
- Partial
- Some covered source work completed, but a gap or warning remains.
- Unavailable
- The source could not be checked; the result is unknown, not clear.
- Not licensed
- The adapter did not run because current policy does not permit that use.
Current source categories
DealSkeptic maintains a source-by-source authorization and lifecycle register internally. The public summary below explains what users can expect without publishing dataset identifiers, integration details, or licensing records. Each report separately identifies the sources actually used, their retrieval context, direct verification links, limitations, and required attribution.
| Category | Current coverage | Selected use |
|---|---|---|
| Property and assessment records | Available for supported King County property reviews. | Selected non-person parcel, land, building, assessment, sale, and assessor-reference facts. |
| Permit and code records | Coverage varies by issuing jurisdiction; unsupported areas require direct portal review. | Selected record scope, dates, status, and work-description evidence when an authorized source is available. |
| Tax-status indicators | Point-in-time screening only; current balances require direct verification. | Selected property-account and receivable facts, excluding taxpayer and contact information. |
| Maps, zoning, and parcel-overlap screens | Available only for supported geographies and layers; not a survey or buildability determination. | Parcel-specific mapped context and derived overlap results. |
| Environmental, hazard, and district screens | Varies by public program, geography, update cycle, and map resolution. | Selected property-specific matches and bounded proximity or intersection findings. |
Lifecycle matrix
| Category | Current handling | Retention |
|---|---|---|
| Transient raw source responses | Processed in memory for the individual request; no DealSkeptic application cache is enabled. | 0-second application cache TTL; discarded when request processing ends. |
| Normalized selected fields | Only allowlisted property fields needed for the report are retained in a saved report. | For the private-beta period or until a verified deletion request; no fixed automatic expiry is enabled yet. |
| Derived spatial matches and findings | Stored in the report with source and retrieval context; old reports are not silently refreshed. | For the private-beta period or until a verified deletion request. |
| Submitted address and listing claims | Stored with a saved report so the user can understand what was reviewed. | For the private-beta period or until a verified deletion request. |
| Feedback | Rating, optional reason, and optional comment are stored with a pseudonymous browser identifier. | For the private-beta period or until a verified deletion request. |
| Operational telemetry | Limited to timing, outcome, jurisdiction, counts, source status, and hashed browser identifier when available. | For the private-beta period; there is no fixed automatic expiry yet. Provider service/security logs follow provider settings. |
| Account and beta membership | An external authentication provider handles sign-in; DealSkeptic stores beta email, user ID, and access status. | Until beta access is removed, the private beta ends, or a verified deletion request is completed. |
Historical reports and source changes
Saved reports retain their original retrieval context and are not silently refreshed. When a current source policy narrows sharing or blocks use, DealSkeptic rechecks access and can revoke the share token or stop displaying the source-derived report. Raw responses are not stored in the application cache.
Corrections and source concerns
Report an incorrect fact or deletion request to support@dealskeptic.com. Send attribution, licensing, or source-authorization concerns to licensing@dealskeptic.com. Public-source use does not imply that King County, Seattle, Washington State, FEMA, or another agency endorses DealSkeptic.