API Terms of Service

1. Agreement

1.1 Acceptance

These API Terms of Service ("API Terms") govern access to and use of the PTP Commercial API (the "API") provided by PolTraPro LLC ("PTP"). These API Terms supplement, and prevail over, the public-site Terms of Service in case of conflict for matters relating to API use.

By creating an API key, paying for any tier, or making any request to the API, you ("Subscriber") agree to these API Terms, to the Acceptable Use Policy ("AUP") incorporated by reference, and to the Privacy Policy.

If you are entering into these API Terms on behalf of a company, organization, or other legal entity, you represent that you have authority to bind that entity. "Subscriber" then means that entity.

1.2 Entity-level binding

If Subscriber is an entity, all references to Subscriber's representations, warranties, and obligations apply to the entity. Authorized users acting within the scope of their employment with Subscriber are bound on the entity's behalf.

1.3 Definitions

For purposes of these API Terms:

• "API Data" means any data, content, metadata, or material retrieved through the API.
• "Joined Dataset" means PTP's pre-joined combination of campaign finance, voting records, stock trades, revolving-door connections, prediction-market odds, and other relational joins, including the methodology by which PTP performs the joins.
• "Authorized User" means an individual employed by or contracted to Subscriber who is permitted to access the API on Subscriber's behalf.
• "Documentation" means PTP's published API documentation at poltrapro.com/developers.
• "Subscriber Application" means the software, service, publication, or product Subscriber operates that consumes API Data.
• "Personal Data" has the meaning given in PTP's Privacy Policy.
• "Sensitive Data" means as defined in applicable state privacy law (e.g., TDPSA § 541.001(28)).

---

2. The API

2.1 What the API provides

The API provides programmatic access to PTP's joined political-data product, subject to tier and as-built endpoints. Endpoint inventory is published in the Documentation and is updated as new endpoints are released. Endpoints may include:

• Candidate profiles
• Campaign-finance summaries and itemized contribution records (sourced from FEC public records and state campaign finance agencies)
• Voting records and bill sponsorship data (sourced from Congress.gov and state legislatures)
• Stock-trade disclosures (sourced from House Clerk PTRs and Senate Electronic Filing Disclosure)
• Lobbying disclosure records (sourced from Lobbying Disclosure Act filings)
• Revolving-door connections (when implemented)
• Dark-money organization data (when implemented)
• Prediction-market odds (sourced from Polymarket and other third-party prediction markets)
• The Money-Vote Gap (MVG) metric (proprietary to PTP) and underlying components
• The pre-joined Joined Dataset combining the above

2.2 What the API does not provide

The API does not provide:

• Investment advice, securities recommendations, or trading signals as to any security or commodity
• Voter contact information, voter file data, or registered-voter records
• Voter or political advice or recommendations
• Any service that would constitute the practice of law, accounting, financial planning, or insurance brokerage
• Any product whose principal purpose is the solicitation of political contributions or commercial donor prospecting
• Real-time messaging or push-notification services for end consumers
• Identification or location of natural persons beyond what is in the public records

2.3 No advisory relationship

Provision of API Data does not create any advisory, fiduciary, attorney-client, broker-dealer, or investment-adviser relationship between PTP and Subscriber.

---

3. Account, Keys, and Authentication

3.1 Account creation

Subscriber must register an account at poltrapro.com/developers (and, when launched, /portal). Required registration information:

• Subscriber's legal name (individual) or registered legal entity name
• Subscriber's authorized contact email
• Subscriber's country of operation (for export-control screening per § 9)
• Subscriber's intended use case (free-text description)
• For paid tiers: billing information processed by PTP's payment processor

3.2 Identity verification

PTP may require additional identity verification for paid-tier or high-tier accounts, including business-formation documentation, government identification of authorized users, beneficial-ownership disclosure, or other reasonable measures consistent with U.S. anti-money-laundering and sanctions-compliance practice. (See § 9.)

3.3 API keys

PTP issues API keys to authenticated Subscribers. Each key is associated with a specific account, tier, and rate-limit profile.

Key security. Subscriber is responsible for the security of its keys and for all use of the API made via its keys, whether authorized or not. Subscriber must:

• Store keys securely (encrypted at rest, not committed to public source control)
• Restrict key access to Authorized Users with a need-to-know
• Rotate keys promptly if they are or may be compromised, using the self-service rotation flow at /portal
• Notify PTP immediately at PolTraPro@proton.me if a key is known or suspected to be compromised

No sharing. API keys are personal to Subscriber. Subscriber may not share keys with any third party, sublicense access, sell access, or resell access to the API or to API Data except as expressly permitted in § 5.

Multiple-key prohibition. Subscriber may not register multiple accounts or maintain multiple keys to circumvent rate limits or tier restrictions.

3.4 Authorized users (for entity Subscribers)

Entity Subscribers may grant API key access to Authorized Users employed by or contracted to Subscriber. Subscriber is responsible for ensuring Authorized Users:

• Comply with these API Terms and the AUP
• Receive training on the AUP § 3 (§ 30111(a)(4) compliance) and § 4.2 (harassment prohibition)
• Cease using the API when their employment or engagement with Subscriber ends

---

4. Tiers, Pricing, Rate Limits, Billing

4.1 Tiers

PTP offers the following tier structure, subject to change with notice per § 4.6:

Current tier definitions, rate limits, prices, and feature inclusions are published at poltrapro.com/developers and are incorporated into these API Terms by reference. PTP may change tier definitions, rate limits, and prices on 30 days' notice via the developer portal and Subscriber's email of record.

Existing paid-tier price protection. A paid Subscriber's price remains in effect through the end of the current billing cycle. Price increases take effect at the next renewal after 30 days' notice.

4.2 Rate limits

Each tier has a request limit measured in requests per day, with secondary burst limits measured in requests per second/minute. Subscriber agrees not to attempt to circumvent rate limits, including by:

• Using multiple keys, multiple accounts, or distributed request patterns
• Rotating IP addresses to evade per-IP limits
• Aggregating requests from multiple end users into a single key (where the use case would normally require separate user attribution)
• Any other technical evasion

Rate-limit circumvention is grounds for immediate termination under § 9.3 and the AUP § 4.3.

4.3 Auto-renewal and California Automatic Renewal Law compliance

4.3.1 Auto-renewal terms

Paid subscriptions auto-renew at the end of each billing cycle at the then-current price for that tier, unless Subscriber cancels prior to the renewal date.

4.3.2 California Automatic Renewal Law (Cal. Bus. & Prof. Code § 17600 et seq.) compliance

For Subscribers in California, the following terms are highlighted in a conspicuous manner in the subscription signup flow:

• Automatic renewal: Your subscription will automatically renew at the end of each billing cycle until you cancel.
• Cancellation: You may cancel at any time before the renewal date through the developer portal (/portal) without speaking to a representative.
• Renewal price: The renewal price is the then-current price for your tier as posted at poltrapro.com/developers, unless we provide separate notice of a price change.
• Renewal date: Each billing cycle is one (1) month from your subscription start date for monthly tiers, or one (1) year for annual tiers.
• Renewal reminder: For annual subscriptions, PTP will send a renewal reminder between 15 and 45 days before each renewal date, consistent with Cal. Bus. & Prof. Code § 17602(a)(3).
• Easy cancellation: Cancellation is available via the developer portal /portal in a one-click flow that does not require speaking to a representative or providing reason for cancellation.

4.3.3 Cancellation

Subscriber may cancel auto-renewal at any time via the developer portal at poltrapro.com/portal. Cancellation is effective at the end of the then-current billing cycle. Subscriber retains access through the end of the paid period.

Cancellation does not entitle Subscriber to a refund of fees already paid, except where required by applicable law.

4.3.4 Refunds

Refunds are not provided for partial periods, downgrades mid-cycle, or unused capacity, except:

• Where applicable consumer-protection law requires refund
• Where PTP has materially failed to provide the API during the period (in which case PTP may, at its discretion, refund pro-rated unused time or credit toward the next billing cycle)
• For Enterprise tier, refunds are governed by the negotiated Enterprise agreement

4.4 Sales tax, VAT, and other charges

Listed prices do not include sales tax, use tax, value-added tax (VAT), goods and services tax (GST), or similar taxes. Where applicable law requires, PTP will collect and remit such taxes to the appropriate authority; Subscriber is responsible for any taxes arising from its use of the API that PTP does not collect.

For Enterprise customers in jurisdictions where PTP is not registered to collect tax, Subscriber bears the responsibility for self-assessment and remittance.

4.5 Free tier

The Free tier is offered as a courtesy and may be modified, restricted, or terminated at PTP's discretion at any time, with reasonable notice where feasible.

Free-tier use is subject to the same AUP and all other obligations as paid tiers. Free-tier Subscribers may be subject to additional restrictions on bulk export, redistribution, or commercial use as published in the Documentation.

4.6 Tier modification with notice

PTP may modify tier structure, pricing, or rate limits on 30 days' notice. Existing paid Subscribers retain their then-current pricing through the end of the current billing cycle. If a Subscriber does not agree to a material change, the Subscriber's remedy is to cancel auto-renewal under § 4.3.3.

---

5. License to Use Data Retrieved Through the API

5.1 Grant

Subject to these API Terms, the AUP, and the Privacy Policy, PTP grants Subscriber a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to use API Data for Subscriber's internal business, research, or editorial purposes, and to display individual data points as part of Subscriber's publications, applications, or analyses consistent with §§ 5.2–5.5.

5.2 Permitted uses

• Internal analysis, modeling, and research not republished as a primary commercial product
• Display of API Data in Subscriber's published news articles, academic papers, blog posts, podcasts, videos, or applications, with attribution per § 5.4
• Building software applications that present API Data to end users for informational or editorial purposes
• Integrating API Data into Subscriber's existing data products as one source among others (not as the primary product)
• Citation in academic, journalistic, or educational work consistent with normal citation practice
• Government use: federal, state, or local government agencies, oversight bodies, or inspectors general performing official duties

5.3 Prohibited uses (in addition to AUP)

In addition to the prohibitions in the AUP:

5.3.1 Resale prohibition

• Reselling raw API Data or any subset of it as a primary product.
• Operating a "wrapper" service that re-exposes PTP API endpoints under a different brand.
• Sublicensing or transferring access to the API or API Data to any third party.
• Sharing keys with multiple downstream users to circumvent the per-Subscriber license model.

5.3.2 Joined Dataset republication prohibition

Reproducing or republishing the Joined Dataset (PTP's pre-joined combination of finance + votes + trades + revolving-door + markets) as a derivative dataset or feed.

5.3.3 Fair-use carveout (research and journalism)

Notwithstanding § 5.3.2, bona-fide journalism, academic research, and educational use that incidentally references the Joined Dataset's structure is permitted without prior approval, provided:

• The use is for the purpose of news reporting, academic publication, education, or commentary
• Attribution to PTP is preserved per § 5.4
• The use does not function as a substitute for PTP's API service to third parties
• The use does not reproduce the entire Joined Dataset or large portions of it

PTP reserves the right to challenge any use that exceeds these bounds. Subscribers in doubt should contact PolTraPro@proton.me before publication.

5.3.4 Attribution removal prohibition

• Removing or obscuring source attribution for Primary-Source Data (e.g., FEC source URLs displayed by the API).
• Removing or obscuring attribution to PTP for Editorial Content delivered through the API (e.g., MVG metric, methodology references).
• Renaming PTP-original metrics (e.g., renaming "Money-Vote Gap" or "MVG" to a Subscriber-branded equivalent in a way that obscures provenance).

5.3.5 Donor-prospecting and solicitation

Using API Data to compile, sell, or use donor lists, voter lists, contact databases, or analogous solicitation-purpose products in violation of 52 U.S.C. § 30111(a)(4), analogous state law per AUP § 3, or any other applicable law. (See AUP § 3 for detail.)

5.3.6 Harassment, stalking, intimidation

Using API Data to harass, intimidate, stalk, or facilitate violence. (See AUP § 4.2.)

5.3.7 § 30111(a)(4) violation

Using API Data in any product whose principal purpose violates 52 U.S.C. § 30111(a)(4) or any state-level analogous statute identified in AUP § 3.2.

5.4 Attribution

When Subscriber publishes content materially derived from API Data, attribution should read substantially as:

"Source: Political Transparency Project (poltrapro.com)" with a hyperlink to the relevant Site page or methodology page.

Where the underlying data has its own primary source (FEC, Congress.gov, House Clerk, etc.), Subscriber must also retain attribution to that primary source consistent with the primary source's own terms.

Editorial branding. When attributing PTP, Subscriber may use the "Political Transparency Project," "PTP," or "@PolTraPro" wordmark in a textual reference consistent with nominative fair use. Use of PTP logos in a stylized banner or graphical attribution requires prior written permission.

5.5 Reservation

All rights not expressly granted to Subscriber are reserved by PTP and the original primary-source publishers.

5.6 No copyright on underlying public-record data

The underlying public-record data (FEC filings, Congressional records, etc.) is in the public domain. PTP's copyright is in the Editorial Content, methodology, joins, and presentation. The license granted in § 5.1 covers PTP's original work; nothing in these API Terms purports to grant PTP rights in the underlying public domain.

---

6. Acceptable Use

Subscriber's use of the API is governed by the Acceptable Use Policy ("AUP") at /legal/acceptable-use-policy, which is incorporated by reference into these API Terms.

Violation of the AUP is grounds for immediate suspension or termination of Subscriber's API access. PTP may take enforcement action under AUP § 10 without prior notice for severe violations (AUP §§ 3, 4.2, 5, 7).

Subscriber is responsible for ensuring its Authorized Users comply with the AUP and for any AUP violation by an Authorized User acting on Subscriber's behalf.

---

7. Service Levels and Changes

7.1 Free / hobbyist tier

PTP makes commercially reasonable efforts to provide reliable service to Free and Developer tier Subscribers but offers no specific uptime, latency, or support guarantee on those tiers.

7.2 Paid-tier service expectations

For Research and Enterprise tier Subscribers, PTP offers the following best-effort targets (subject to written SLA for Enterprise):

If PTP fails to meet uptime targets, Subscriber's sole remedy is service credits as follows:

Service credits are calculated against the next billing cycle's fee. Service credits are the exclusive remedy for service-level failures and are subject to the limitation of liability in § 11.

7.3 API changes

PTP may modify, deprecate, or remove API endpoints, fields, or behaviors. PTP commits to:

• Backwards-incompatible changes to a versioned endpoint: at least 60 days' written notice to active Subscribers via email and developer portal, with migration documentation
• Backwards-compatible additions: no advance notice required; documented in the API changelog
• Critical security fixes: as little notice as is consistent with security; documented post hoc
• Maintenance windows: scheduled, with at least 7 days' notice for non-emergency maintenance

Versioning is via /api/v1/* URL path. PTP commits to maintaining /api/v1/* for at least 18 months after the release of /api/v2/*.

7.4 Data accuracy

API Data is drawn from public records and third-party sources that may be incomplete, lagged, or contain errors at their source. PTP makes a good-faith effort to surface current data and to mark known gaps. PTP does not warrant accuracy or completeness of API Data and is not liable for Subscriber's reliance on incorrect or incomplete data.

If Subscriber identifies an error in API Data, please report it to PolTraPro@proton.me.

7.5 Backups and disaster recovery

PTP maintains automated backups of its production database with up to 35 days rolling retention. PTP makes a good-faith effort to restore service from backup in the event of catastrophic data loss but makes no specific recovery-time or recovery-point guarantee on Free, Developer, or Research tiers.

---

8. Confidentiality and Trade Secrets

8.1 Confidentiality of pricing and internal documentation

API Data is publicly licensable subject to these API Terms. PTP's pricing, tier structure, internal product documentation (where shared with Subscriber), unannounced features, and security implementations are confidential.

Subscriber may not publish PTP's confidential pricing, internal documentation, or security implementations without PTP's prior written consent.

8.2 Trade-secret protection

PTP claims trade-secret protection in:

• The Joined Dataset's pre-joining methodology, including the specific rules, weights, and thresholds used
• The MVG metric's underlying computation, including the chamber-median normalization logic and the donor-position inference pipeline
• PTP's internal algorithms for entity resolution (when revolving-door tracker is implemented)
• PTP's editorial classification rules used to tag bills and votes by industry

Subscriber receives API Data, not access to the trade-secret methodology. Reverse-engineering the methodology from API Data outputs is prohibited.

8.3 No reverse engineering

Subscriber may not reverse-engineer, decompile, or otherwise attempt to derive PTP's source code, database schema, methodology, or trade secrets from API Data or from interaction with the API. This prohibition does not apply to bona-fide academic research and journalism into PTP's editorial methodology with the goal of public commentary or critique, subject to AUP § 5.

8.4 Confidentiality term

Confidentiality obligations under this § 8 survive termination for three (3) years or for so long as the relevant information remains confidential, whichever is shorter.

---

9. Sanctions, Export Controls, and Foreign-Customer Compliance

9.1 Sanctions compliance representation

Subscriber represents and warrants on a continuing basis that:

• Subscriber is not located in, organized under the laws of, or controlled by any country, region, or person subject to comprehensive U.S. sanctions, including those administered by OFAC under the Specially Designated Nationals and Blocked Persons List (SDN List) or any other applicable list
• Subscriber is not, and is not owned 50% or more by, any person on the SDN List, the Foreign Sanctions Evaders List, or any other applicable sanctions list
• Subscriber will not use the API or API Data to do business with any person on the SDN List or in a comprehensively sanctioned jurisdiction
• Subscriber will not use the API or API Data in violation of U.S. sanctions

9.2 OFAC SDN screening

PTP reserves the right to screen Subscriber and Subscriber's affiliates against the OFAC SDN List, the Foreign Sanctions Evaders List, the Sectoral Sanctions Identifications List, the Consolidated Sanctions List, and any other applicable sanctions lists at the time of API key issuance and periodically thereafter. PTP may suspend or terminate API access immediately if screening returns a positive result, without prior notice.

9.3 Export-control compliance

Subscriber represents and warrants that:

• API Data is not "controlled technology" under the Export Administration Regulations (EAR, 15 C.F.R. Parts 730-774) or the International Traffic in Arms Regulations (ITAR, 22 C.F.R. Parts 120-130) by virtue of being received from PTP
• Subscriber will not use API Data in any manner that violates U.S. export-control laws
• Subscriber will not transfer API Data to any restricted person or destination under the EAR, ITAR, or analogous foreign export-control regimes

9.4 Foreign-government customers and FARA

If Subscriber is a foreign government, foreign-state-owned enterprise, foreign political party, or is acting at the direction of any of the foregoing:

• Subscriber must disclose this to PTP at the time of API key issuance
• Subscriber must comply with the Foreign Agents Registration Act (FARA, 22 U.S.C. § 611 et seq.) and analogous state laws (Arkansas, Louisiana, Nebraska, Oklahoma, Texas as of 2025; Florida SB 700 nonprofit restrictions; and any subsequent state enactments)
• Subscriber's use of API Data may not include lobbying, political advocacy, or public-relations activity in the United States at the direction of a foreign principal, except in compliance with FARA's registration and disclosure requirements
• PTP may decline to issue API keys to foreign-government or foreign-state-owned customers in its sole discretion

---

10. Data Processing and Privacy

10.1 Personal data in API requests

If Subscriber transmits Personal Data to PTP (e.g., in request parameters, headers, or webhooks), Subscriber represents that it has authority to do so and has provided all required notices and obtained all required consents from the data subjects.

10.2 PTP's role under data protection laws

PTP acts as a controller with respect to Subscriber's account information and API usage logs (as described in the Privacy Policy). PTP does not act as Subscriber's data processor with respect to public-record political data delivered through the API.

10.3 Data Processing Addendum

For Enterprise Subscribers subject to GDPR, UK GDPR, the Swiss Federal Act on Data Protection, CCPA/CPRA (as a "service provider"), or similar data-protection law that requires a Data Processing Addendum ("DPA"), the parties will execute PTP's standard DPA. The DPA template is available from PolTraPro@proton.me.

10.4 Subprocessors

PTP's subprocessor list is published in the Privacy Policy § 6.1. PTP will provide at least 30 days' notice before adding a new subprocessor that processes Personal Data of Subscriber's end users.

---

11. Disclaimers

11.1 As-is, no warranty

THE API IS PROVIDED "AS IS" AND "AS AVAILABLE." PTP DISCLAIMS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, AND UNINTERRUPTED OPERATION, TO THE FULLEST EXTENT PERMITTED BY LAW.

PTP DOES NOT WARRANT THAT:

• THE API WILL MEET SUBSCRIBER'S REQUIREMENTS
• THE API WILL OPERATE UNINTERRUPTED, ERROR-FREE, OR SECURE
• DEFECTS WILL BE CORRECTED
• API DATA IS ACCURATE, CURRENT, OR COMPLETE
• ANY THIRD-PARTY DATA SOURCE WILL CONTINUE TO BE AVAILABLE

11.2 No investment, legal, or other professional advice

API DATA IS PROVIDED FOR INFORMATIONAL AND EDITORIAL PURPOSES ONLY. NOTHING IN THE API CONSTITUTES INVESTMENT ADVICE, LEGAL ADVICE, ACCOUNTING ADVICE, TAX ADVICE, OR PROFESSIONAL ADVICE OF ANY KIND. PTP IS NOT A REGISTERED BROKER-DEALER, INVESTMENT ADVISER, COMMODITY TRADING ADVISOR, FINANCIAL PLANNER, OR ATTORNEY. Subscriber must consult appropriate licensed professionals before making any decision based on API Data.

---

12. Limitation of Liability

12.1 Cap

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, PTP'S TOTAL CUMULATIVE LIABILITY ARISING FROM OR RELATED TO THESE API TERMS, THE AUP, OR THE PRIVACY POLICY SHALL NOT EXCEED THE GREATER OF:

• ONE HUNDRED DOLLARS ($100), OR
• THE AMOUNT SUBSCRIBER PAID TO PTP IN THE TWELVE (12) MONTHS PRECEDING THE FIRST CLAIM.

For Enterprise Subscribers, the cap may be modified by negotiated agreement (typically: amount paid in the 24 months preceding the first claim).

12.2 Exclusion of consequential damages

PTP IS NOT LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR PUNITIVE DAMAGES, INCLUDING LOST PROFITS, LOST DATA, LOST BUSINESS, LOSS OF GOODWILL, OR BUSINESS INTERRUPTION, EVEN IF PTP HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

12.3 Statutory exceptions

The limitations in §§ 12.1 and 12.2 do not apply to liability that cannot be excluded under applicable law, including:

• Liability for gross negligence or willful misconduct
• Liability for fraud or fraudulent misrepresentation
• Liability under specific consumer-protection statutes that prohibit waiver

12.4 Time limitation

To the maximum extent permitted by law, Subscriber must commence any action arising out of or related to these API Terms within one (1) year after the cause of action accrues, or the action is forever barred.

---

13. Indemnification

13.1 By Subscriber

Subscriber will indemnify, defend, and hold harmless PTP and its officers, members, managers, employees, contractors, agents, successors, and assigns from any third-party claim, demand, action, proceeding, loss, damage, liability, cost, or expense (including reasonable attorneys' fees) arising out of or related to:

• Subscriber's breach of these API Terms, the AUP, or the Privacy Policy
• Subscriber's misuse of API Data, including any use that violates 52 U.S.C. § 30111(a)(4), analogous state law, anti-spam law (CAN-SPAM, TCPA), or any other applicable law
• Subscriber's products or services that incorporate API Data
• Subscriber's misrepresentation of API Data, its source, or PTP's editorial positions
• Subscriber's Authorized Users' actions with respect to the API
• Subscriber's violation of third-party intellectual property, privacy, publicity, or contractual rights
• Subscriber's failure to comply with applicable consumer-protection, election, campaign-finance, sanctions, export-control, or data-protection laws

PTP reserves the right, at Subscriber's expense, to assume the exclusive defense and control of any matter for which Subscriber has agreed to indemnify, and Subscriber agrees to cooperate.

13.2 By PTP

PTP will defend Subscriber against claims that the API Data, as delivered through the API in accordance with these API Terms, infringes the intellectual property rights of a third party, and PTP will pay damages finally awarded against Subscriber or the settlement amount, provided:

• Subscriber promptly notifies PTP in writing
• Subscriber gives PTP sole control of the defense and settlement
• Subscriber provides reasonable cooperation

PTP's indemnification obligation does not apply to claims arising from:

• Subscriber's modification of API Data
• Subscriber's combination of API Data with materials not provided by PTP
• Subscriber's continued use of API Data after notice of a claim
• Subscriber's breach of these API Terms

---

14. Term and Termination

14.1 Term

These API Terms are effective on Subscriber's first request to the API and continue until terminated.

14.2 Termination by Subscriber

Subscriber may terminate at any time by canceling auto-renewal under § 4.3.3 and ceasing API use. Paid subscriptions remain effective through the end of the current billing cycle.

14.3 Termination by PTP

PTP may suspend or terminate Subscriber's access immediately for:

• Any AUP violation
• Rate-limit circumvention
• Non-payment
• Fraud or fraudulent misrepresentation
• Sanctions or export-control violation
• Material breach of these API Terms
• A determination that Subscriber's use creates legal or reputational risk to PTP
• Any time without cause for Free-tier Subscribers

For paid Subscribers, PTP will provide reasonable notice of suspension or termination except in cases of severe violation (AUP §§ 3, 4.2, 5, 7), security risk, or where prior notice would prejudice PTP's interests.

14.4 Effect of termination

On termination:

• Subscriber must cease all API use immediately
• Subscriber must delete cached API Data within 30 days, except API Data that has been incorporated into Subscriber's published works (which may be retained subject to ongoing attribution per § 5.4)
• The license in § 5.1 terminates
• §§ 5.4 (attribution), 8 (confidentiality), 9 (sanctions/export), 10 (data processing), 11 (disclaimers), 12 (limitation of liability), 13 (indemnification), 16 (governing law), 17 (dispute resolution), 18 (general) survive

---

15. Compliance with Law

Subscriber represents and warrants that its use of the API will comply with all applicable U.S. federal, state, and local laws, and applicable foreign laws, including but not limited to:

• The Federal Election Campaign Act (52 U.S.C. § 30101 et seq.) and FEC regulations (especially 52 U.S.C. § 30111(a)(4) and 11 C.F.R. § 104.15)
• The state-level donor-data use restrictions in AUP § 3.2
• Federal and state consumer-protection laws
• Applicable state comprehensive privacy laws (CCPA/CPRA, VCDPA, CPA, CTDPA, UCPA, TDPSA, OCPA, MCDPA, ICDPA, TIPA, DPDPA, NJDPA, NHPA, NDPA, MCDPA-MN, MODPA, ICDPA-IN, KCDPA, RIDTPPA, FDBR, and any subsequent enactments)
• Anti-spam law (CAN-SPAM Act, 15 U.S.C. § 7701 et seq.)
• Telephone Consumer Protection Act (47 U.S.C. § 227) and Telemarketing Sales Rule
• Children's Online Privacy Protection Act (COPPA, 15 U.S.C. § 6501 et seq.)
• Applicable export-control laws (EAR, ITAR)
• Applicable sanctions laws (OFAC and parallel state regimes)
• Applicable election-period restrictions and state electioneering disclosure laws
• Applicable foreign-agent registration laws (FARA and state Baby FARA in AR, LA, NE, OK, TX, plus any subsequent enactments)
• Applicable right-of-publicity and AI-content laws
• Applicable defamation, privacy, and intellectual property laws

Subscriber's compliance with applicable law is a continuing obligation. If Subscriber becomes aware of any non-compliance, Subscriber must notify PTP at PolTraPro@proton.me promptly and cooperate with PTP to remediate.

---

16. Governing Law

These API Terms are governed by the laws of the State of Arizona without regard to its conflict-of-laws principles. The U.N. Convention on Contracts for the International Sale of Goods does not apply.

---

17. Dispute Resolution

17.1 Forum selection

Disputes arising out of or related to these API Terms shall be brought exclusively in the state or federal courts located in Maricopa County, Arizona, or Pima County, Arizona, and Subscriber consents to personal jurisdiction in those courts.

17.2 Class action and arbitration

No class arbitration. No class action. Disputes between Subscriber and PTP may be brought only in Subscriber's individual capacity, not as a plaintiff or class member in any purported class or representative proceeding.

17.3 Equitable relief

Notwithstanding any provision of this § 17, PTP may seek injunctive or other equitable relief in any court of competent jurisdiction for breaches of §§ 3 (account/keys), 5 (license/prohibitions), 8 (confidentiality), 9 (sanctions/export), or any threatened breach that would cause irreparable harm.

17.4 Equitable relief — protective scope

In recognition of the difficulty of measuring damages for breach of confidentiality, trade-secret protection (§ 8), or unauthorized commercial republication of the Joined Dataset (§ 5.3.2), Subscriber agrees that PTP is entitled to seek temporary, preliminary, or permanent injunctive relief without posting bond, in addition to any other remedy.

---

18. General

18.1 Entire agreement

These API Terms, together with the AUP, the Privacy Policy, the DPA (if executed), the Documentation, and any tier-specific terms or Enterprise agreements, constitute the entire agreement between Subscriber and PTP with respect to the API.

18.2 No assignment by Subscriber

Subscriber may not assign these API Terms or any rights or obligations hereunder without PTP's prior written consent. Any purported assignment without consent is void. PTP may assign these API Terms freely in connection with a merger, acquisition, sale of substantially all assets, or other corporate reorganization.

18.3 No third-party beneficiaries

These API Terms confer no rights on any person or entity other than Subscriber and PTP.

18.4 Severability

If any provision of these API Terms is held invalid, illegal, or unenforceable, the validity, legality, and enforceability of the remaining provisions are not affected.

18.5 No waiver

PTP's failure to enforce any provision of these API Terms is not a waiver.

18.6 Force majeure

Neither party is liable for any delay or failure to perform under these API Terms caused by events beyond reasonable control (force majeure events), including but not limited to acts of God, natural disasters, war, terrorism, civil unrest, government action, internet or telecommunications outages, denial-of-service attacks, supply-chain disruption, pandemic, or labor disturbance.

18.7 Notices

PTP will deliver notices to Subscriber by email to the address on file. Subscriber notices to PTP go to PolTraPro@proton.me with a copy to PolTraPro@proton.me for AUP-related matters.

18.8 Headings

Headings in these API Terms are for convenience only and do not affect interpretation.

18.9 Counterparts and electronic signature

For Enterprise customers requiring a written agreement, these API Terms (or any Enterprise schedule incorporating them) may be executed in counterparts and by electronic signature, each of which constitutes an original.

---

19. Contact

PolTraPro LLC Service-of-process address available on written request via PolTraPro@proton.me