Plain English, on purpose. These are the terms you agree to when you buy from, subscribe to, or receive data from DeedStake — including the free 25-lead sample.
Last updated 7 August 2026
"DeedStake", "we" and "us" mean the DeedStake service and the person who operates it. "You" means the individual or business that requests, receives, buys or subscribes to data from us. "The Data" means any list, file, spreadsheet, export or feed of property signals and owner contact information we deliver to you — free samples included.
By requesting a free sample, buying a one-time pull, or starting a subscription, you agree to these terms. If you don't agree, don't use the Data.
Payments are processed by Polar as Merchant of Record (see §7). Polar's own terms cover the payment transaction itself; these terms cover the Data.
These six clauses are the whole deal on how the Data may be used. They also flow down obligations our own data providers place on us, so they are not negotiable.
You may use the Data delivered under this Agreement only for your own internal business purposes, to lawfully market or provide your own services to the property owner identified in each record. You may not use the Data to make an eligibility decision about any person — for credit, insurance, employment, tenant screening, or a similar purpose. The Data is not a "consumer report" and may not be used as one. You are solely responsible for determining that your specific use of the Data is lawful.
The Data is licensed to you for your own use only. You may not sell, sublicense, share, publish, broker, or otherwise redistribute the Data — in whole, in part, raw, or combined with other data — to any other person or company, for a fee or for free. This license is non-transferable.
The Data is compiled from public records and licensed third-party sources. It does not include, constitute, or evidence any person's consent to be called, texted, or otherwise contacted for marketing purposes. Before contacting anyone using the Data, you are solely responsible for complying with all applicable law, including the federal Telephone Consumer Protection Act (TCPA), the FTC's Telemarketing Sales Rule / National Do Not Call Registry, applicable state telemarketing laws, and CAN-SPAM. Specifically: (a) live, manually-dialed calls to a residential number must honor the National DNC Registry and occur only 8am–9pm in the recipient's local time; (b) any autodialed call, prerecorded/artificial-voice call, or text message to a mobile number requires the recipient's prior express written consent, which this Data does not provide. Do not autodial or mass-text from this Data.
If you receive a request — directly, or forwarded by us — from someone on the Data asking not to be contacted, you must honor it immediately and add them to your own internal do-not-contact list.
If someone contacts [email protected] asking not to be contacted, we suppress them from future deliveries and forward the request to any subscriber who already received that record.
You agree to indemnify, defend, and hold harmless DeedStake and its data providers from any claim, fine, penalty, or liability (including reasonable legal fees) arising from your use of the Data, including any violation of the TCPA, state telemarketing law, or this Agreement.
Our data providers (including BatchData) are intended third-party beneficiaries of Clauses 2.1–2.5 and may enforce them directly against you.
Two layers, and we're specific about which is which.
Records are de-duplicated by address and checked against a delivered-lead ledger so the same property isn't shipped to you twice, and each record carries a freshness score based on the signal date.
Where a public dataset backs a figure we publish on our marketing pages, we print the dataset's identifier, the filter we applied and the date we pulled it, so you can re-run it yourself against the source.
Each subscription tier includes a monthly cap on delivered records. DeedStake is a push service — we build and send your file; you don't query, pull or request records yourself. Because of that, you cannot exceed your cap by accident and you are never automatically metered.
| Tier | Included records / month | Included geography |
|---|---|---|
| Starter — $149/mo or $1,490/yr | 250 records | 1 ZIP, exclusive to you |
| Pro — $399/mo or $3,990/yr | 650 records | Up to 3 counties (non-exclusive unless you add Exclusive Zone) |
| DFY Lead Ops — $1,200–$1,800/mo, scope-banded (ceiling $2,500/mo) | 1,500 / 2,500 / 3,500 records, banded to the price you're quoted | Bespoke, fully exclusive |
Exclusivity is sold by ZIP code, never by county. Starter includes one exclusive ZIP at no extra charge. On Pro, Exclusive Zone is an add-on covering up to five ZIP codes (+$400/mo or +$4,000/yr, plus $75/mo for each additional ZIP beyond five). It is included at no extra charge on DFY Lead Ops. While a ZIP + buy-box combination is reserved to you, we don't sell that combination to another buyer. That reservation survives your departure: any record we have delivered to you is permanently retired — we will not deliver or sell it to any later customer, even after your subscription ends. A new, later-dated signal on a previously delivered address is a new record.
Reservations are recorded in the ZIP-keyed exclusivity ledger we call the Stake Ledger™, and the fulfilment pipeline checks it before any file is built. We will read the relevant entries to you on request.
Close one deal in 60 days, or that period is free. Here are the exact mechanics, stated up front rather than improvised later.
To invoke it, email [email protected] before day 60 ends.
Two commitments about the data itself, both mechanical rather than editorial. §5 is about the outcome you get; this section is about the file you get. Read §6.3 before you rely on any of it — the exclusions are real and we list them up front rather than in a footnote.
Every file we deliver carries, on every row: the source identifier, the publisher's own dataset identifier, a summary of the exact filter we ran, the date of the newest record in that source at the moment of the pull, and the timestamp of the pull. Those five fields are the receipt. They are printed so that you can take any row back to the publisher's own endpoint and re-run it yourself.
Freshness is always measured as the newest actual record returned live by the source endpoint. A portal's "last updated" metadata is never used, because that timestamp reports edits to the listing rather than refreshes of the data — a dataset can have its page touched years after its last row.
For each source named in the table below we publish a staleness threshold. If we build and deliver your file from a covered source on a day when that source's newest record is older than its stated threshold, that week is credited to your account automatically. We report it to you; you do not have to notice it, claim it, or ask for it.
| Metro | Signal | Source identifier | Stale after |
|---|---|---|---|
| Chicago | Code violation | chicago_code_violations | 7 days |
| Chicago | Vacant building (311) | chicago_311_vacant_buildings | 5 days |
| Dallas | Code violation | dallas_code_violations | 5 days |
| Atlanta metro (DeKalb) | Code violation | dekalb_code_cases | 7 days |
| Tampa metro (Hillsborough) | Probate | hillsborough_probate | 6 days |
| Tampa metro (Hillsborough) | Pre-foreclosure | hillsborough_civil_foreclosure | 4 days |
| Tampa metro (Hillsborough) | Eviction | hillsborough_civil_eviction | 4 days |
The remedy is a service credit against your account, never cash. A stale week is credited at that week's share of your subscription and is applied to your next invoice. The 60-day guarantee in §5 is the only mechanism on this site that returns money; this one does not. Sources are added to this table only after they have been measured, and a source can be removed from it by amendment on notice under §8.
The service level in §6.2 applies only to the sources named in its table, and does not apply to: (a) Phoenix, where the published layer carries no per-case date field of any kind, so there is nothing to measure and we never quote a freshness figure for that metro; (b) Hillsborough County code-enforcement cases, which are republished by the county as a periodic snapshot rather than a live feed — that source is delivered and receipted but is not sold or credited on freshness; (c) San Francisco, which is live in the pipeline and carries a receipt like every other source but sits outside this service level; (d) any period in which the publisher's own endpoint is unavailable, rate-limited, restructured, or has ceased publishing, and any event outside our reasonable control. A county-side outage is not a breach of this clause; we will tell you it happened and no credit accrues.
Freshness is not accuracy, and this clause never becomes a warranty of either. §6.2 is a commitment about the age of records. It says nothing about whether a skip-traced phone number is current or correct, whether an owner wants to sell, or whether any record produces a deal — §3 governs all of that and is unchanged by this section.
A delivered record's identity is sha1(your customer id + the property address + the signal type), lower-cased and whitespace-collapsed. Once that key is written to your delivered-lead ledger, that record is never delivered to you again and never counted against your cap again — in any later week, any later month, for as long as you are a customer. This is permanent and per-customer; it does not reset on renewal, on a plan change, or at the start of a month.
A newly-cited property is a new record. If an address you have already received later picks up a new, later-dated signal, that is a different key: it is a new record, it may be delivered to you, and it counts against your cap in the month it is delivered. A new violation on an old address is a new lead, not a duplicate.
The credit rule. If we deliver you a record you have already received and it counts against your cap, tell us and we will credit those records back to that month's cap and repair the key in the ledger. The remedy is expressed in records, not in money.
Retirement in the other direction — records already delivered to you never being handed to a later holder of your ZIP — is covered by §4 and survives the end of your subscription. The fulfilment pipeline enforces it before it builds a file: when a ZIP changes hands, every record already delivered to that ZIP's former holder is suppressed from the new holder's deliveries.
Questions about these terms, a suppression request, or a guarantee claim: [email protected]. A human replies — Victor himself, usually within one business day.
See also our Privacy Policy.