Acceptable Use Policy

1. INTRODUCTION AND SCOPE

This Acceptable Use Policy (“AUP”), version 1, last updated August 14, 2026, governs Your use of the MarketCheck Developer Platform (the “Service”) provided by Market Check Cars, Inc., a Nevada corporation (“MarketCheck”).

This AUP supplements the Terms of Service available at developers.marketcheck.com/terms (the “Terms”). In the event of a conflict between this AUP and the Terms, the Terms shall control. Capitalized terms not defined in this AUP have the meanings assigned to them in the Terms.

You are required to comply with this AUP at all times when accessing or using the Service. Violations of this AUP may result in throttling, suspension, or immediate termination of Your access to the Service, as provided in Section 9.1 of the Terms.

By accessing or using the Service, You acknowledge that You have read, understood, and agree to be bound by this AUP.

2. FAIR USE AND RATE LIMITS

Each subscription tier includes documented rate limits and call allowances. You must comply with the limits applicable to your tier at all times.

(a)      2.1 Respect the rate limits, call quotas, and usage thresholds published for your subscription tier in the Developer Platform documentation.

(b)      2.2 Do not attempt to circumvent rate limits through any means, including (without limitation) creating multiple accounts, obtaining additional API keys, rotating IP addresses, distributing requests across proxies, or employing any other technical method designed to exceed your authorized usage.

(c)      2.3 The free tier (500 calls per month) is provided solely for evaluation and development purposes. You may not use the free tier as a production data source.

(d)      2.4 If your usage consistently approaches or exceeds your tier’s limits, you must upgrade to an appropriate paid tier or contact MarketCheck to discuss enterprise access.

(e)      2.5 MarketCheck reserves the right to throttle or reject requests that exceed your tier’s rate limits without prior notice.

3. RESPONSIBLE INTEGRATION

3.1 You are responsible for all API consumption that originates from your integration, including calls generated by search engine crawlers, social media bots, automated agents, or other downstream consumers of your application. All such calls count toward your usage and billing regardless of how they are initiated.

3.2 If your integration architecture causes third-party crawlers or bots to generate API calls (for example, by embedding live API responses in publicly crawlable pages), you bear full responsibility for the resulting usage volume and associated charges.

3.3 You must implement appropriate technical controls to prevent unintended amplification of API usage. At a minimum, you should deploy caching headers, robots.txt rules, and access controls sufficient to limit automated or indirect consumption of MarketCheck endpoints.

3.4 You must not embed API keys in client-side code, public repositories, or any other location accessible to end users or automated systems. API keys must be stored securely on the server side and protected from unauthorized access.

4. PROHIBITED CONDUCT

4.1 Sections 5 (Restrictions and Prohibited Uses), 6 (AI and Model Training), 7 (Caching and Retention), and 8 (Attribution and Branding) of the Terms of Service set out the full list of legal restrictions governing your use of the Service. This Section 4 supplements those restrictions with operational and behavioral prohibitions.

4.2 In addition to the restrictions in the Terms, the following conduct is prohibited:

(a)      Using the Service in a way that degrades performance or availability for other customers.

(b)      Sending requests at a rate or volume designed to stress-test or benchmark the Service without prior written coordination with MarketCheck.

(c)      Submitting malicious, malformed, or intentionally oversized payloads.

(d)      Attempting to access endpoints, data, accounts, or systems that your subscription does not authorize.

(e)      Using automated tools to create accounts or bypass onboarding steps.

(f)      Misrepresenting your identity, company affiliation, or intended use case during sign-up or in communications with MarketCheck.

(g)      Sharing API keys or account credentials with anyone outside your organization, or allowing third parties to use your credentials to access the Service.

5. SECURITY RESEARCH

5.1 If you discover a security vulnerability in the Service, report it promptly to security@marketcheck.com. Do not exploit, publicly disclose, or demonstrate any vulnerability before MarketCheck has had a reasonable opportunity to investigate and remediate the issue.

5.2 You must obtain prior written authorization from MarketCheck before performing any penetration testing, vulnerability scanning, or load testing against production endpoints. Unauthorized testing of this nature will be treated as a violation of this Policy and may result in immediate account termination under Section 9.1 of the Terms.

5.3 When submitting a vulnerability report, include a clear description of the issue, the steps required to reproduce it, and any potential impact you have identified. Direct all reports to security@marketcheck.com.

5.4 Authorized security researchers who comply with this Section 5 and report vulnerabilities in good faith will not face account action solely on the basis of their research activities.

6. MONITORING AND ENFORCEMENT

6.1 MarketCheck monitors API usage patterns, request volumes, and account activity to detect conduct that is inconsistent with this Policy or the Terms of Service.

6.2 If MarketCheck identifies a potential violation, it may, at its sole discretion, take one or more of the following actions:

(a)      Issue a written warning describing the concern and requesting corrective action;

(b)      Throttle your API access to reduce request rates or limit available endpoints;

(c)      Suspend your account pending investigation; or

(d)      Terminate your access immediately under Section 9.1 of the Terms.

6.3 MarketCheck is not required to provide advance notice before taking any enforcement action described in Section 6.2. Where practicable, MarketCheck will use reasonable efforts to notify you of the nature of the concern and the action taken.

6.4 MarketCheck may select and escalate among the actions listed in Section 6.2 in any order, based on the severity, frequency, or impact of the violation. Repeated or severe violations may result in permanent account termination and a ban on future sign-ups across all subscription tiers.

7. REPORTING VIOLATIONS

7.1 If you believe another user of the Service is violating this Policy or the Terms of Service, you may submit a report to abuse@marketcheck.com.

7.2 To allow MarketCheck to investigate effectively, each report should include the following information to the extent available:

(a)      The account name, application name, or other identifier associated with the suspected violator.

(b)      A description of the conduct you believe violates this Policy or the Terms, including the specific section(s) at issue.

(c)      Any supporting evidence, such as screenshots, URLs, timestamps, or log excerpts that document the suspected violation.

7.3 MarketCheck will review all reports submitted in good faith. Submission of a report does not obligate MarketCheck to take any particular action or to disclose the outcome of its investigation to the reporting party.

7.4 Do not submit reports that are frivolous, retaliatory, or that you know to be false. Abuse of the reporting process may itself constitute a violation of this Policy.

8. CHANGES TO THIS POLICY

8.1 MarketCheck reserves the right to update or modify this Acceptable Use Policy at any time.

8.2 When MarketCheck makes material changes to this Policy, it will (a) post the revised version at developers.marketcheck.com/acceptable-use with an updated “Last updated” date, and (b) notify account holders via email to the address associated with their account.

8.3 Non-material changes, such as corrections of typographical errors or minor clarifications that do not alter the substance of any provision, may be made without email notification but will be reflected in the updated “Last updated” date on this page.

8.4 Your continued use of the Service after any changes to this Policy take effect constitutes your acceptance of the revised Policy. If you do not agree with a change, you must stop using the Service and close your account before the change takes effect.

9. CONTACT INFORMATION

For questions or concerns related to this Policy, the Terms, or your use of the Service, contact MarketCheck using the appropriate channel below.

Market Check Cars, Inc. · 169 Madison Ave STE 57434, New York, NY 10016