1. What this Policy is
This Acceptable Use and Abuse Policy (this “Policy”) is the “AUP” in, and part of, the Investorlift Data Services Developer Agreement (Beta) (the “Developer Agreement”) you accept when you sign in to the Console; capitalized terms have its meanings, and it controls on a conflict. The Policy binds every Key and every use of the API and the Data by you or your product; you answer for your Keys, product, staff and users; only a signed agreement with Investorlift that says so varies it for you; and Licensors may enforce its data rules against you directly (Developer Agreement Section 18.2).2. What you may do
Developer Agreement Section 5 is the license; this section describes it and grants nothing more. You may call the API from your own software, including through an MCP Client; show Data inside your own product to your End Users, with the required attribution; use Data internally, in your own real estate business, to analyze, underwrite and select opportunities; and, subject to Section 3, lawfully contact a company the Data names or the owner or occupant of a property it identifies. Your End User terms must carry Section 5.2’s restrictions. Derived Data, as the Developer Agreement defines it, is yours, but 3.6 to 3.10 apply to any that identifies a natural person, and an output carrying a person’s name or any other Data value is a copy of Data, not Derived Data.3. Prohibited uses
The Data 3.1 No resale as data. Do not sell, license, publish or otherwise make the Data available as data: no file, feed, export, download, database, API or bulk report of it. 3.2 No bulk copying. Do not extract, mirror or copy the Data in bulk or a meaningful part of a market’s records, or keep Data beyond the cache rule of Developer Agreement Section 7; a kept name or any other value beyond its Section 7.2 identifiers is a copy under that rule. 3.3 No competing datasets. Do not use the Data to build, seed or enrich a dataset, feed or data product that substitutes for or competes with the Data or a Licensor’s data products. 3.4 No model training. Do not train, fine-tune or evaluate a machine learning model on the Data, assemble Data for that purpose, or keep Data in a store built to feed a model beyond the cache rule; Developer Agreement Sections 6.1(c) and 7.3 govern in-session use and the MCP Client transcript, which a removal notice under 3.11 reaches. 3.5 Keep notices and attribution. Do not show Data without the attribution Developer Agreement Section 8 requires; do not remove or altermeta.terms, a request id or any other notice in a response you pass on or store, or the attribution where you show Data; and do not pass the Data off as your own or another’s.
People
3.6 No consumer-report uses. The Data is not a consumer report, and what it carries about a lender describes recorded lending activity, not any borrower’s creditworthiness. Do not use it, or let End Users use it, as a factor in deciding anyone’s eligibility for credit, insurance, employment, housing, a lease or a governmental license or benefit, for tenant screening or background checks, or for any other purpose the Fair Credit Reporting Act governs, or build on it a background-check, tenant-screening or person-locating product (Developer Agreement Section 9.3).
3.7 No unlawful contact. The Data conveys no consent to call, text, email, mail or visit anyone and no do-not-call, litigator or quiet-hours status; if you contact anyone using it, or using contact details obtained elsewhere for a record in it, you are the caller or sender, and compliance with the laws Developer Agreement Section 9.4 names is yours alone.
3.8 No stalking or surveillance. Do not use the Data to stalk, harass, threaten, intimidate, track or surveil anyone, to find where a specific individual lives for a purpose unrelated to a real estate transaction, or to infer a protected characteristic; assessing a named investor’s market activity, as Section 2 permits, is none of these (Developer Agreement Section 9.6).
3.9 No discrimination. Do not use the Data to discriminate in housing, lending or a related service in violation of the Fair Housing Act, the Equal Credit Opportunity Act or state law (Developer Agreement Section 9.6).
3.10 No re-identification. Do not use the Data, alone or with other sources, to identify or locate a natural person behind a field the API withholds (Developer Agreement Section 9.1 lists them), or a person the API never names: a buyer or owner with no investor id, an owner-occupant, a parcel owner whose redacted_reason is set, or a person whose record Investorlift has removed. Do not append phone numbers, email addresses or a home address to any record for a prohibited use or to defeat a removal. Reading the public filings of a company or trust the API names, or contacting it through its registered agent or officers, is not re-identification; 3.7 governs the contact and the enriched record stays Data. Sections 3.6 to 3.9 apply to a served name or address that is a person’s.
3.11 Privacy requests and removals. Developer Agreement Section 9.5 states these duties in full. Forward any privacy request about a person in the Data, with the record identifiers and the requester’s details, to support@investorlift.com, subject “Privacy request” or “Removal request”, within 5 Business Days, and tell the requester you have. Forwarding does not discharge your own duty under a law that requires you to stop disclosing information about a person once notified: comply within the period that law allows from your own receipt, whether or not Investorlift has acted, and you may withhold the records concerned meanwhile. When Investorlift notifies you under Developer Agreement Section 22.1 that a record was removed, stop showing it at once, delete every copy within 10 Business Days (a store carrying the person’s name or any other Data value is a copy; only the Section 7.2 identifier may stay) and do not re-acquire it.
The API, Console and Documentation
3.12 No circumventing limits or the gateway. Do not evade an Allowance, rate limit, cap, Key rule, suspension, revocation or the gateway: no retry loops that ignore Retry-After, no spreading one workload across Keys or accounts, no reaching the API or its MCP endpoint through any host but api.investorlift.com, including an origin behind the gateway.
3.13 No tiling a market. Do not sweep a market with pin or list calls across a grid of viewports or filters to reconstruct its records; cell counts at wide zooms and pins when zoomed in, as the API’s limits direct, are normal use.
3.14 No more than three Keys. Hold no more than three Keys per person or company, counting every Key under every account and subscription you or anyone acting for you controls; a second Investorlift account violates Section 4 whatever its Key count.
3.15 No Key sharing. A Key serves the account that holds it and the products that account holder operates, and requests from all of them count against the same Allowances; do not give it to anyone outside your organization or to another company, or embed it in a product you do not operate. People who build or run your products for you may use it (Developer Agreement Section 4.2).
3.16 No scraping. Do not crawl, scrape or automate the Console, or harvest the Documentation in bulk. The Documentation’s own features (its copy and open-in-assistant menu, its search, its documentation MCP server and the OpenAPI document it publishes) are yours to use and are not the API (Developer Agreement Section 6.1(e)); the playground’s calls are API requests under your Key.
3.17 No automated account creation. A person creates each account and subscription by hand.
3.18 No security testing without consent. Do not probe, scan, load-test or try to penetrate the API, the gateway, the Console or the Documentation without Investorlift’s written consent, requested at support@investorlift.com; report a vulnerability to the same address.
3.19 No misrepresentation. Do not state or imply that Investorlift, a Licensor or a Public Source endorses, operates, has verified or is responsible for your product, or, absent an Enterprise agreement stating one, has committed to or guarantees any availability, uptime, response time or continuity of Data Services or the Data (a commitment you make to your End Users is yours alone, Developer Agreement Sections 6.1(g) and 12.2); do not pose as Investorlift; and beyond the required attribution line do not use their names, marks or logos, including in a product name or domain (Developer Agreement Sections 8.3 and 14.1). A truthful plain-text statement that your product uses Investorlift Data Services is not a trademark use.
3.20 Nothing unlawful. Do not use the API or the Data in violation of any law or anyone’s rights.
4. Keys and accounts
Developer Agreement Sections 1.2 and 4 govern accounts and Keys: one Investorlift account, with accurate details; Keys only from the Console, kept secret and out of client code and repositories, rolled on suspicion, a leaked Key deleted on the Console at once and reported to support@investorlift.com within 72 hours. Investorlift may roll, suspend or revoke a Key at any time to protect Data Services, the Data, a Licensor, a Public Source or other users, as Developer Agreement Section 4.4 provides.5. Allowances and fair use
Your Allowances and limits are the numbers on the Plans and limits page (https://developers.investorlift.com/guides/plans-and-limits) and the Console, not here; reaching a limit is not abuse, evading one is. These signals start a review of a Key, not a step, and a review that finds no violation of Section 3 leaves the Key unchanged: sweeping a market with viewport or filter calls (3.13); more than three Keys per person or company (3.14); one Key serving a product or customer outside your organization (3.15); scraping the Console or Documentation (3.16); asking support for the name of a person behind a deed party with no investor id (3.10). The Privacy Notice (https://developers.investorlift.com/guides/privacy) says what Data Services records about your requests.6. Enforcement
In order:- Email warning naming the rule; your Key is unchanged.
- 24-hour throttle of your Key to the Free Plan’s per-minute rate limit, whatever your Plan; your Allowances, subscription and fee are unchanged and nothing is credited. On Free, already at that limit, Investorlift may go straight to step 3.
- Revocation of the Key. The Key stops and is not restored unless Investorlift reinstates you (Section 7). Rolling or replacing it, resubscribing, or moving the same work to another Key or account is evasion under 3.12: that Key or subscription is revoked too and you move to step 4. A paid subscription is canceled at the end of the current period unless your appeal asks to keep it, and is restored if your appeal succeeds before the period ends; a Free subscription is unchanged. Data you hold stays under the cache rule until it expires; fetch nothing new.
- Closure of the account for Data Services: every Key is deleted, the subscription ends, and Investorlift may also close your Investorlift account under the Terms of Service (Developer Agreement Section 1.4). Your license ends and Developer Agreement Section 13.3 applies: stop using the Data and delete every copy within 30 days, except Derived Data and what that Section lets you keep.