API Terms | Dealr Policies

These API Terms (“API Terms”) govern access to and use of the Dealr application programming interfaces, including the Dealr.cloud API, its webhooks, its OpenAPI document, and the connectors and SDKs Dealr publishes for it (together, the “API”), by Dealr, Inc. (“Dealr”). They are the integrator terms referred to in Section 10.2(c) (Integrator conditions) of the Master Services Agreement.

Who these terms bind. “You” means the person or business that accepts these API Terms, and the business on whose behalf an individual accepts them. You are one of:

a Customer of Dealr, acting through its own End Users, building or running an integration for its own business;
an Integrator: a third party a Customer designates to access the Services or retrieve its Customer Content, such as a software vendor, agency, or consultant; or
a Developer: anyone else who reads the Documentation or builds an application meant to be used by Customers.

Your classification depends on who you are, not on how your Credentials were issued. Once a Customer authorizes you, or you access a Customer’s account, Credentials, or Customer Content, you are an Integrator if you are not the Customer or its employee, including when the Customer gives your personnel End User logins, personal API keys, or an organization key. Until then, you are a Developer. A Customer’s employee acts as the Customer.

Credentials. API keys, OAuth client secrets, access and refresh tokens, and webhook signing secrets are “Credentials.” Dealr issues Credentials that reach Customer Content only within a Customer’s account, to the Customer or for an Integrator the Customer authorizes. A Developer may register an OAuth client but obtains no access to Customer Content until a Customer authorizes it.

Definitions. If you accept on behalf of an entity, you represent and warrant that you have authority to bind it. Capitalized terms not defined here (such as Customer, Customer Content, End User, Integrator, Services, and Policy Center) have the meanings in the Master Services Agreement General Terms (the “MSA”). In these API Terms:

“Applicable Law” has its MSA meaning and also includes all laws applicable to you, your integration, and your processing of Customer Content.
“Documentation” means the Dealr.cloud API developer documentation at https://dealr.cloud/docs/api, the OpenAPI document, and the API changelog, which Dealr designates as Documentation under the MSA.
“Security Incident” includes any actual or reasonably suspected unauthorized access to, or acquisition, use, or disclosure of, Credentials or Customer Content in your or your service providers’ systems.
An API endpoint is “generally available” when the Documentation marks it stable in a dated API version. Endpoints under /unstable/ or marked otherwise are early access under Section 6(a).

How you accept. You accept these API Terms by clicking to accept them when Credentials are issued, when you register an OAuth client, or when you authorize an application that uses the API. Dealr records each acceptance with the accepting user, the organization, the version accepted, and the time. If you are issued, receive, or use Credentials for a Customer’s account, or register an OAuth client, you and the entity you act for also accept these API Terms on first use, whether or not you clicked. If you read or use the public Documentation without accepting in one of those ways, Sections 2, 7, 11, 12, 14, and 16, and Section 10 to the extent you receive non-public information, apply to that use. Section 15(b)–(d) does not apply to that use, and disputes about it are resolved under Section 9 of the Website Terms of Use.

Customers and their End Users. If you are a Customer’s End User, your organization’s use of the API is governed by its MSA. Nothing you accept here amends the MSA, and the MSA controls if they conflict, except as Section 1(a) provides.

1. Relationship to the Customer’s agreement

(a) The Customer’s agreement controls the Customer’s data. All access to Customer Content through the API is access under the Customer’s agreement with Dealr (the MSA and its components). Nothing in these API Terms expands what that agreement permits. These API Terms are an Incorporated Policy under the MSA. If you are the Customer and they conflict with the MSA, the MSA controls, except that Sections 3 (Credentials), 4 (Rate limits and fair use), and 6 (Early access) of these API Terms control as to the API.

(b) These API Terms bind Integrators and Developers in full. If you are not the Customer, these API Terms apply to you directly and in full, whatever the Customer’s agreement with Dealr says. No Customer agreement, instruction, or authorization waives, narrows, or relaxes your obligations under these API Terms or limits Dealr’s rights or remedies against you. You are not a party to, or a third-party beneficiary of, any Customer’s agreement with Dealr, and you may not rely on its limitations of liability, warranties, or other protections.

(c) Integrators act for a Customer. If you are an Integrator, you access a Customer’s account only as that Customer has authorized. The Customer is responsible for your acts and omissions under MSA Section 10.2(c), and you are also directly liable to Dealr for them under these API Terms. Dealr may pursue you, the Customer, or both, but will not recover the same loss twice. Your rights to a Customer’s data end when that Customer’s authorization, its account, or its agreement with Dealr ends.

(d) No Customer, no Customer Content. A Developer with no Customer authorization may read the public Documentation under the Website Terms of Use and these API Terms, but may not access any Customer Content.

(e) Dealer Data Laws. “Dealer Data Laws” means state statutes regulating access to, use of, or fees for data stored in a dealer data or dealer management system, including A.R.S. §§ 28-4651 to 28-4655, MCA §§ 30-11-717 to 30-11-720, ORS 650.123, 47 O.S. § 564.3, N.C. Gen. Stat. § 20-305.7, Utah Code Title 13, Chapter 73, the Michigan Motor Vehicle Dealer Data Collection Act (2026 Pub. Act 113), and O.C.G.A. §§ 10-1-630 et seq., each as amended, and any other state statute regulating access to or use of data in a dealer data system. Where a Dealer Data Law applies to a Customer, it controls over these API Terms to the extent of any conflict, consistent with MSA Section 10.4 (State-specific rider).

(f) Fees, access list, and revocation.

(i) Fees. Dealr may charge Customers or Integrators fees for API access or usage, on at least thirty (30) days’ notice or as an Order Form provides. Where a Dealer Data Law applies, Dealr will not charge a fee to access or write Customer Content through the API beyond what that law permits.

(ii) Recipient list and audit. The Services provide a Customer a list of the Integrators, Credentials, and AI Client Connections with access to its Customer Content, and access records reasonably sufficient for the Customer to audit that access, for as long as Dealr retains them (currently ninety (90) days).

(iii) Revocation. A Customer may revoke an Integrator’s Credentials at any time through the Services. Dealr stops honoring revoked Credentials promptly, normally on the next request made with them. Dealr is not responsible for activity under Credentials before their revocation takes effect.

(g) AI Client Connections. AI Client Connections are governed by MSA Section 10.2(d). The connected AI application’s provider is not an Integrator, and its own terms, not these API Terms, govern its retention and use of data, including any use for model training. The Services notify the authorizing End User of this when a connection is authorized, and Customers and End Users should review the provider’s terms before authorizing a connection.

2. Your license

(a) Grant. Subject to these API Terms, Dealr grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license during the term of your access to use the API and its Documentation to build, test, and run integrations that access the Services as these API Terms and the authorizing Customer permit.

(b) OpenAPI document and code samples. You may copy the OpenAPI document, and the code samples in the Documentation, into your own integration code, and generate client libraries from the OpenAPI document, solely to build integrations with the Services. You may not publish or distribute the OpenAPI document or a generated client as a stand-alone product, or use either to build a product that substitutes for the Services.

(c) Accommodation. Dealr currently provides the API without a separate fee, as an accommodation to Customers. The allocation of risk in these API Terms reflects that.

(d) Feedback. Dealr may use any suggestions or feedback you give about the API without restriction or obligation to you.

(e) Reserved. Dealr reserves all rights not expressly granted. The API, the OpenAPI document, the Documentation, and the Services are Dealr Materials under the MSA.

3. Credentials and security

(a) Keep Credentials secret. Credentials are confidential. Store them securely, never embed them in client-side code, mobile apps, or public repositories, and limit them to the personnel and systems that need them. Do not share Credentials with, or obtain them from, anyone other than as Dealr’s credential-issuance process provides. A Customer who gives you Credentials does so only on condition that you have accepted these API Terms.

(b) Least privilege. Request only the scopes and permissions your integration needs. Credentials act with the permissions of the Customer, End User, or role they were issued for, and you may not attempt to exceed them.

(c) Responsibility. You are responsible for all activity under your Credentials. Each request made with them is the authorizing Customer’s instruction under MSA Section 8.2(d) and is attributed to that Customer under MSA Section 3.2(c). That attribution allocates responsibility between Dealr and the Customer only. It does not reduce your responsibility to Dealr or to the Customer for activity under your Credentials.

(d) Report compromise. Tell Dealr at security@dealr.cloud, and the affected Customer, without undue delay and in any event within seventy-two (72) hours after you discover a Security Incident. Revoke or rotate the affected Credentials, cooperate with Dealr’s and the Customer’s investigation, and support any notice the Customer must give, including the Customer’s FTC notification under 16 C.F.R. § 314.4(j).

(e) Security standard. If you are an Integrator, you will comply with the STAR Standards (Standards for Technology in Automotive Retail) security guidelines, or other generally accepted information-security standards at least as comprehensive. At a minimum, you will maintain safeguards meeting 16 C.F.R. § 314.4, including access controls, encryption of customer information in transit and at rest, multi-factor authentication, logging, and an incident response plan. A current SOC 2 Type II report or ISO/IEC 27001 certification covering the systems that process Customer Content is sufficient evidence that you comply with this Section 3(e). On reasonable request, you will describe your safeguards to Dealr and to the authorizing Customer, and, after a Security Incident or where Dealr reasonably suspects a breach of these API Terms, give Dealr the records and access reasonably needed to verify your compliance.

(f) Insurance. If you are an Integrator that is not the Customer or its employee, you will maintain, while you have access and for one (1) year after, cyber liability (including network security, privacy, and data breach response) and technology errors and omissions insurance, each with limits of at least one million dollars ($1,000,000) per claim and in the aggregate, from insurers rated A- or better by A.M. Best. The policies will be on a form that covers your indemnity obligations under these API Terms, will name Dealr as an additional insured on the cyber policy where commercially available, and, if written on a claims-made basis, will include an extended reporting period of at least one (1) year. You will give Dealr a certificate of insurance on request and notify Dealr within ten (10) days if any required coverage is cancelled or reduced. Your insurance does not limit your liability under these API Terms.

4. Rate limits, fair use, and fees

(a) Limits. Dealr sets rate limits, quotas, page sizes, and other usage limits for the API and publishes them in the Documentation or in response headers. Dealr may change them at any time, with or without notice. You will stay within them, honor Retry-After and similar signals, and back off when told to.

(b) No circumvention. You will not use multiple Credentials, accounts, or IP addresses, or any other means, to get around a limit or a suspension.

(c) Fees. Any API fees under Section 1(f)(i) are billed to the Customer under its Order Form, or to an Integrator under the terms Dealr presents when the fee is introduced. You will pay the fees Dealr notifies to you, as invoiced, within thirty (30) days. Continued use after a fee takes effect is acceptance of it. Dealr may suspend Credentials for amounts more than ten (10) days overdue.

5. Data use

(a) Purpose limit. You will access, use, store, and share Customer Content obtained through the API only to the extent allowed by your written agreement with the authorizing Customer and these API Terms, only to provide the integration or service that Customer requested, and only as Applicable Law permits.

(b) No resale or unrelated use. You will not sell, rent, or license Customer Content; use it to build or enrich profiles or databases for any use other than the authorizing Customer’s; use it for advertising or marketing other than on that Customer’s behalf; or combine one Customer’s Content with another Customer’s or use one Customer’s Content for another Customer.

(c) AI training. You will not use Customer Content, or any data derived from it (including anonymized, aggregated, or de-identified forms), to train, fine-tune, or improve any machine-learning or AI model, except (i) a model used solely to provide services to the Customer whose Customer Content is used, where that Customer has expressly authorized that use in writing, or (ii) with Dealr’s prior written consent. You will not combine different Customers’ Content for model training, and will not sell, license, or disclose Customer Content or models derived from it to third parties. Nothing in this Section 5(c) limits a Customer’s rights under an applicable Dealer Data Law or its right to export its own data.

(d) Consumer information. Customer Content often includes consumers’ personal and financial information.

(i) Safeguards. If you are an Integrator, you will implement and maintain safeguards for Customer Content meeting 16 C.F.R. § 314.4.

(ii) GLBA and DPPA use limits. You will use and disclose nonpublic personal information only as necessary to perform the services the Customer requested, consistent with 15 U.S.C. § 6802(c) and 16 C.F.R. § 313.11. You will use personal information from a motor vehicle record only for a purpose permitted by 18 U.S.C. § 2721(b), and will keep the redisclosure records 18 U.S.C. § 2721(c) requires for five (5) years.

(iii) Minimum data. You will not request contact fields or other personal information your integration does not need.

(e) Acting as a service provider. To the extent you process personal data on a Customer’s behalf, you act as that Customer’s service provider or processor. You will process it only on the Customer’s documented instructions, will not sell or share it, and will give the Customer information reasonably needed to assess your safeguards. The Customer remains responsible for selecting and periodically assessing its Integrators (16 C.F.R. § 314.4(f)) and for any separate service-provider or processor agreement Applicable Law requires. Dealr is not a party to that agreement.

(f) Your service providers. You may let your own service providers process Customer Content only under written terms at least as protective as these API Terms. You remain responsible for their acts and omissions, and will give Dealr or the Customer a list of them on request.

(g) Retention and deletion. Keep Customer Content only as long as needed for the authorized purpose. When the authorizing Customer’s authorization or agreement ends, or on that Customer’s or Dealr’s request, you will delete Customer Content within thirty (30) days unless, within that period, the Customer directs you in writing to return it instead. You will cooperate in a secure transition and confirm deletion in writing on request, unless Applicable Law requires you to keep the data.

6. Early access; changes to the API

(a) Early access. Endpoints under /unstable/, and any endpoint or feature that is not generally available, may change, or be withdrawn, at any time, including without a deprecation period and within a date version. Dealr will give reasonable notice where practicable and records changes in the API changelog.

(b) After general availability. Dealr will give at least thirty (30) days’ notice before removing a generally available endpoint or making a breaking change to it, except where a shorter period is reasonably necessary to address a security vulnerability, a legal requirement, or a threat to the integrity of the Services.

(c) Discontinuing the API. Subject to any applicable Dealer Data Law, Dealr may discontinue the API, or any part of it, on thirty (30) days’ notice, or sooner where reasonably necessary for security, legal compliance, or the integrity of the Services.

(d) No service levels. No uptime, latency, support, or other service-level commitment applies to the API, including any in the MSA or a Product Schedule, unless the authorizing Customer’s Order Form expressly extends it to the API.

7. Prohibited conduct

You will not, and will not help or permit anyone else to:

(a) access the API other than through the interfaces and Credentials Dealr provides, or access data you are not authorized to see, including other Customers’ data;

(b) probe, scan, or test the vulnerability of the API, except good-faith security research that you report promptly to security@dealr.cloud and conduct under any vulnerability-disclosure policy Dealr publishes;

(d) scrape the Services’ user interface in place of, or to get around limits on, the API;

(e) misrepresent your identity, your integration, or your relationship with a Customer or with Dealr;

(f) use the API in violation of the Acceptable Use & Communications Policy or Applicable Law, including to send communications the AUP prohibits; or

(g) use the API to build, train, or benchmark a product or service that competes with the Services, or publish performance benchmarks of the API without Dealr’s written consent.

8. Apps, listings, and branding

(a) Your integration is yours. You are solely responsible for your integration, its support, and your terms and privacy notices with the Customers and End Users who use it. Your integration is not part of the Services, and Dealr does not endorse it.

(b) Disclose what you access. If you offer your integration to Customers other than yourself, you will clearly tell each Customer, before it authorizes you, what data your integration accesses, what it changes, and how you use and retain that data.

(c) Branding. You may use the “Dealr” name only to describe accurately that your integration works with the Services, and only as Dealr’s brand guidelines, if any, allow. You may not suggest Dealr sponsors, certifies, or partners with you without Dealr’s written consent. Listing in a Dealr marketplace or directory, if Dealr offers one, is at Dealr’s discretion and may be subject to additional terms.

9. Monitoring, suspension, and termination

(a) Monitoring. Dealr logs and monitors API use to operate, secure, and bill for the Services and to enforce these API Terms.

(b) Suspension. Dealr may throttle, suspend, or revoke Credentials or your access, with or without notice, if Dealr reasonably believes you have breached these API Terms, your use threatens the security, integrity, or availability of the Services or any Customer’s data, or Applicable Law requires it, and as Section 4(c) provides for overdue fees. Where practicable, Dealr will tell you, and the affected Customer, why. Suspension on security grounds is a reasonable security condition, not a restriction on a Customer’s access to its own data.

(c) Termination. You may stop using the API at any time. If you are the Customer, your API access ends only as the MSA and Section 6 provide. Otherwise, Dealr may end these API Terms as to you on thirty (30) days’ notice for any reason, or immediately for breach. Your access to a Customer’s account ends automatically when that Customer’s authorization or agreement with Dealr ends.

(d) Survival. Sections 1(b), 1(c), 2(d), 2(e), 3(c), 3(d), 3(e) (as to verification after a Security Incident or suspected breach), 3(f), 5, 7, 8(a), 9(d), 10, 11, 12, 13, 15, and 16 survive termination, along with any payment obligation accrued before it.

10. Confidentiality

Non-public information you receive about the API or the Services, including non-public Documentation, security information, and Credentials, is Dealr’s confidential information. You will use it only to build and run your integration and will protect it with at least reasonable care. This obligation lasts while you have access and for two (2) years after it ends, and indefinitely for trade secrets and Credentials. It does not apply to information that is or becomes public through no fault of yours, that you already knew or independently develop, or that you rightfully receive from a third party without a duty of confidentiality.

11. Disclaimers

THE API, THE OPENAPI DOCUMENT, AND THE DOCUMENTATION ARE PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. DEALR DOES NOT WARRANT THAT THE API WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR UNCHANGED, THAT WEBHOOKS WILL BE DELIVERED, OR THAT DATA RETURNED THROUGH THE API IS ACCURATE OR COMPLETE. DEALR IS NOT RESPONSIBLE FOR ANY ACTION YOUR INTEGRATION TAKES IN THE SERVICES OR FOR ANY LOSS OR CORRUPTION OF DATA IT CAUSES. If you are the Customer, the API is not covered by the performance warranties in your MSA unless your Order Form expressly extends them to it.

12. Limitation of liability

(a) Integrators and Developers. EXCEPT AS PROVIDED IN SECTION 12(b), DEALR’S TOTAL LIABILITY TO YOU ARISING FROM THE API OR THESE API TERMS WILL NOT EXCEED THE GREATER OF (i) THE FEES YOU PAID TO DEALR UNDER THESE API TERMS IN THE TWELVE (12) MONTHS BEFORE THE FIRST EVENT GIVING RISE TO THE CLAIM AND (ii) ONE HUNDRED DOLLARS ($100), AND DEALR IS NOT LIABLE TO YOU FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA, OR GOODWILL. THIS SECTION 12 LIMITS DEALR’S LIABILITY ONLY; IT DOES NOT LIMIT YOUR LIABILITY TO DEALR. THESE LIMITS APPLY EVEN IF A LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE, AND REFLECT THAT THE API IS PROVIDED WITHOUT A SEPARATE FEE (SECTION 2(c)).

(b) Exclusions. Section 12(a) does not limit Dealr’s liability for its willful and wanton misconduct or fraud, or any liability that cannot be limited under applicable law.

(c) Time to bring claims. If you are an Integrator or Developer, any claim you have against Dealr arising from the API or these API Terms must be brought within one (1) year after it arises, or it is permanently barred.

(d) Customers. For a Customer, liability relating to the API is governed exclusively by Section 13 (Limitation of Liability) of its MSA.

13. Indemnity

(a) Scope. If you are an Integrator or Developer, you will defend Dealr and its Affiliates, directors, officers, employees, contractors, and licensors against any third-party claim, and pay the resulting losses, damages, fines, and reasonable attorneys’ fees, to the extent arising from: (i) your breach of Sections 3, 4, 5, 7, 10, or 16(a), or of Applicable Law; (ii) your integration or its content, including a claim that it infringes or misappropriates a third party’s intellectual property; or (iii) your access to, use of, or disclosure of Customer Content, including any Security Incident, and any claim by a Customer or a consumer arising from your processing.

(b) Procedure. Dealr will notify you promptly of a claim (delay relieves you only to the extent it prejudices you), let you control the defense with counsel reasonably acceptable to Dealr, and cooperate at your expense. You may not settle a claim in a way that admits fault by, or imposes an obligation on, Dealr without Dealr’s written consent. Dealr may participate with its own counsel at its own expense. Dealr may retain or take control of the defense, at your expense, if you do not assume it promptly, if the claim is brought by a governmental authority or a Customer, if it seeks relief other than money damages against Dealr, or if Dealr reasonably doubts your ability to fund the defense or any judgment.

14. Changes to these API Terms

If you are the Customer, MSA Section 17 (Changes to the Agreement) controls how changes take effect. Otherwise: Dealr may update these API Terms by posting a new version at the Policy Center and in the API changelog. Dealr will give at least thirty (30) days’ notice of a material change by email to the address on the account under which your Credentials were issued, or, if you have none, by that posting, except for changes required by law or for security, and changes that do not adversely affect you, which may take effect on posting. A change applies prospectively only and does not apply to a dispute arising before it takes effect. If you object to a change, your sole remedy is to stop using the API before it takes effect.

15. Governing law; disputes

(a) Customers. A Customer’s disputes relating to the API are resolved under Section 14 (Dispute Resolution) of its MSA.

(b) Integrators and Developers. Colorado law governs these API Terms, without regard to conflict-of-laws rules. Any dispute between Dealr and an Integrator or Developer arising out of or relating to the API or these API Terms will be resolved by final and binding individual arbitration administered by the American Arbitration Association, by a single arbitrator, seated in Larimer County, Colorado, with hearings by videoconference at either party’s request, under the Federal Arbitration Act. The AAA’s Commercial Arbitration Rules apply to a business, and its Consumer Arbitration Rules apply to an individual not acting for a business. Where their thresholds are met, the AAA’s Mass Arbitration Supplementary Rules also apply. The arbitrator has exclusive authority to resolve disputes about the interpretation, applicability, or enforceability of this Section 15, except that whether an arbitration agreement was formed, and the enforceability of the class waiver, are for a court. Nothing in this Section 15 requires arbitration of a claim that federal law (9 U.S.C. §§ 401–402) lets you bring in court. YOU AND DEALR EACH WAIVE THE RIGHT TO A JURY TRIAL AND TO PARTICIPATE IN A CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE ACTION.

(c) Individuals: informal resolution. If you are an individual not acting for a business: (i) before starting an arbitration, you and Dealr will each send the other a written notice of dispute (to Dealr at legal@dealr.cloud) and negotiate in good faith for sixty (60) days; and (ii) Dealr pays the AAA fees the Consumer Arbitration Rules assign to the business.

(d) Carve-outs. Either party may bring an individual claim in small claims court, and either party may bring a court action to collect amounts due under these API Terms. Either party may seek injunctive or other equitable relief in the state and federal courts for Larimer County, Colorado, to protect its intellectual property or confidential information, and Dealr may do so to protect Credentials, Customer Content, or the security of the Services, in each case without posting a bond to the extent the law allows. If the class waiver is found unenforceable as to a claim, that claim proceeds only in those courts.

16. General

(a) Sanctions and export. You represent that you are not located in, organized under the laws of, or ordinarily resident in a country or region subject to comprehensive U.S. sanctions, and are not on, or owned or controlled by a party on, any U.S. government restricted-party list (including OFAC’s Specially Designated Nationals List). You will not export, re-export, or transfer the API, Dealr software, or Customer Content in violation of U.S. export control or sanctions laws. Dealr may suspend Credentials immediately to comply with those laws.

(b) Miscellaneous. If you are an Integrator or Developer, these API Terms, together with the documents they reference, are the entire agreement between you and Dealr about the API. They do not modify any Customer’s agreement with Dealr except as Section 1(a) provides. You may not assign them without Dealr’s written consent. Dealr may assign them to an Affiliate or a successor to its business. If any provision is unenforceable, it will be enforced to the maximum extent permissible and the rest remain in effect. Dealr’s failure to enforce a provision is not a waiver. Notices to Dealr go to legal@dealr.cloud. Notices to you go to the contact details on the account under which your Credentials were issued or, for a Developer, are given by posting at the Policy Center.

Contact: legal@dealr.cloud · Security reports: security@dealr.cloud