MyTCRPlus API Terms of Service & Fair Use Policy

Effective Date: January 13, 2026
Last Updated: January 13, 2026
Version: 1.0

API Provider: Native Chaos Holdings LLC (d/b/a MyTCRPlus)
Business Address: 1887 Mesa Vista Dr, Henderson, NV 89014
Email: info@mytcrplus.com
Phone: 760-269-8277
API Documentation: https://api.mytcrplus.com/docs.html

1. Acceptance & Binding Agreement

By accessing or using the MyTCRPlus API (the “API”), you (“Client,” “you,” “Developer”) accept and agree to be bound by these API Terms of Service (“API Terms”). These API Terms supplement and are incorporated into the MyTCRPlus Terms and Conditions and Privacy Policy, which apply to all MyTCRPlus services.

Authorization Requirement: If you are accessing the API on behalf of an organization, you represent that you have authority to bind that organization to these API Terms. If you lack such authority or do not agree to these terms, you must immediately cease API access.

Modification Notice: We reserve the right to modify these API Terms at any time. Material changes require 30 days advance notice via email to your registered API account address. Continued API use after the effective date constitutes acceptance of modified terms. Non-material changes (clarifications, formatting, corrections) take effect immediately upon posting.

Version History: Previous versions of these API Terms are available upon request to info@mytcrplus.com.

2. Service Description

The MyTCRPlus API provides programmatic access to compliance intelligence tools supporting 10DLC campaign registration, TCR vetting preparation, TCPA consent validation, and SMS/MMS policy adherence.

Available Endpoints

Pre-Registration Validators:

TCR Use Case Selector (POST /use-case-selector) — Returns recommended TCR use case category based on messaging program characteristics
SMS Message Validator (POST /message-validator) — Analyzes message content for TCPA compliance, opt-out language, SHAFT violations
Brand Consistency Checker (POST /brand-check) — Validates alignment between business name, EIN, domain, and DBA
Consent Language Validator (POST /consent-validator) — Evaluates web form disclosure text for required TCPA elements

Policy & Content Scanners:

Content Policy Scanner (POST /policy-scan) — Identifies prohibited content (SHAFT, high-risk financial, cannabis) in message samples
Carrier Policy Checker (GET /provider-checklist) — Returns carrier-specific registration requirements for Twilio, Bandwidth, Sinch, Plivo, Telnyx

Diagnostic & Remediation:

Error Diagnostic Tool (POST /diagnostic) — Provides remediation roadmaps for specific TCR rejection codes
Trust Score Simulator (POST /trust-score) — Estimates TCR trust score based on brand attributes and reputation signals

ROI & Analysis:

ROI Calculator (POST /roi-calculator) — Calculates TCO comparison between in-house compliance build vs. managed platform
Anonymized Approval Database (GET /approval-db) — Searches real-world TCR submission outcomes by industry, use case, message content

Service Boundaries

What the API Provides:

Real-time validation against current TCPA, CTIA, and carrier policy rules
Actionable feedback with specific violation flagging and remediation steps
Structured JSON responses with compliance scoring and pass/fail indicators

What the API Does NOT Provide:

Legal advice or regulatory representation
Guaranteed carrier approval or TCR vetting outcomes
Direct submission to TCR or carrier platforms
Automated campaign registration or brand vetting services
Protection from TCPA litigation or regulatory enforcement

Data Sources: Validation rules derived from publicly available CTIA Messaging Principles, carrier policy documentation (T-Mobile, AT&T, Verizon), TCR guidelines, and industry best practices. Rules updated quarterly or as carrier policies change.

3. API Access & Authentication

API Key Management

Key Generation: API keys issued upon account activation. Generate keys via MyTCRPlus dashboard under “API Settings.”

Authentication Method: Include API key in Authorization header of all requests:

Authorization: Bearer YOUR_API_KEY_HERE

Key Security:

Treat API keys as passwords; do not expose in client-side code, public repositories, or browser applications
Rotate keys immediately if compromise suspected
Use environment variables or secure secret management systems for key storage
Separate keys for development, staging, production environments

Key Rotation: Rotate keys every 90 days for security best practices. We provide 7-day transition period when rotating keys, during which both old and new keys remain valid.

Unauthorized Access: Unauthorized API access attempts, key sharing, or credential reuse across organizations violates these terms and triggers immediate suspension.

Account Requirements

Registration: Valid MyTCRPlus account required for API access. Register at https://mytcrplus.com or contact info@mytcrplus.com for enterprise accounts.

Account Information: Provide accurate business registration details (legal name, EIN, contact information). Update account information within 10 days of changes.

Verification: High-volume API plans may require business verification (DUNS number, articles of incorporation, tax ID) before activation.

4. Fair Use Policy

Usage Limits

API usage subject to fair use principles designed to ensure service availability and performance for all clients.

Rate Limits by Plan Tier

Plan Tier	Requests/Minute	Requests/Day	Concurrent Connections
Free Trial	5	100	1
Basic	20	2,000	2
Standard	60	10,000	5
Plus	120	25,000	10
Enterprise	Custom	Custom	Custom

Rate Limit Headers: API responses include rate limit status:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 42
X-RateLimit-Reset: 1641679200

Exceeded Limits: Requests exceeding rate limits return HTTP 429 Too Many Requests with retry-after header. Persistent violations may trigger temporary throttling or account review.

Acceptable Use Guidelines

Permitted Uses:

Integration into internal compliance workflows, CRM systems, SMS platforms
Pre-submission validation before TCR campaign registration
Batch processing of historical campaign data for compliance audits
Building customer-facing compliance tools (with proper attribution)
Quality assurance testing and development environments

Prohibited Uses:

Reselling API access without written authorization
Circumventing rate limits via multiple accounts or key rotation schemes
Scraping, mirroring, or attempting to replicate MyTCRPlus proprietary algorithms
Using API for competitive intelligence against MyTCRPlus or to build competing services
Excessive polling or redundant validation requests for identical input data
Load testing or stress testing without prior written approval
Automated bulk processing exceeding reasonable compliance validation needs

Burst Allowance

Short-term burst traffic permitted up to 150% of rate limit for maximum 60 seconds per hour. Sustained bursts trigger throttling without penalty. Consistent burst requirements indicate plan upgrade needed.

Enterprise Custom Limits

Organizations exceeding Plus tier limits should contact info@mytcrplus.com for custom rate limits, dedicated infrastructure, and SLA guarantees.

5. Usage Restrictions & Prohibited Conduct

Prohibited Activities

Security Violations:

Attempting to bypass authentication, reverse engineer API logic, or exploit vulnerabilities
DDoS attacks, distributed scanning, or coordinated abuse attempts
Sharing API keys with unauthorized parties or across organizational boundaries
Probing for security weaknesses, injection attacks, or unauthorized data access

Illegal or Harmful Use:

Using API to support messaging programs violating TCPA, CAN-SPAM, state telemarketing laws
Validating content for spam, phishing, malware distribution, or social engineering campaigns
Supporting illegal activities, controlled substances, or explicit material
Facilitating high-risk financial schemes (crypto scams, payday loans, debt relief) prohibited by carriers
Lead generation, affiliate marketing, or debt collection without proper compliance infrastructure

Abuse of Service:

Submitting fabricated data, stress testing, or intentionally malformed requests
Creating multiple accounts to circumvent rate limits or suspension
Automated scraping of API responses to build competing datasets
Using API for purposes unrelated to SMS compliance validation

Content Violations:

Attempting to validate messaging programs containing SHAFT content (Sex, Hate, Alcohol, Firearms, Tobacco)
Political messaging without proper disclaimers and legal counsel
Impersonation of government agencies, financial institutions, or trusted entities
Misleading, deceptive, or fraudulent message content

Enforcement Actions

Violations trigger escalating enforcement:

Warning: First-time minor violations receive email warning with 48-hour remediation deadline
Throttling: Repeated violations reduce rate limits by 50% for 7-day probation period
Suspension: Material violations trigger 30-day account suspension with appeal opportunity
Termination: Persistent abuse, security threats, or illegal activity result in permanent termination without refund

Appeal Process: Suspended accounts may appeal to info@mytcrplus.com with detailed remediation plan. Appeals reviewed within 5 business days. Final decisions at MyTCRPlus sole discretion.

6. Data Privacy & Protection

API usage governed by the MyTCRPlus Privacy Policy, incorporated by reference. Key provisions for API users:

Data Collection

API Request Data: We log API requests including timestamps, endpoint accessed, request parameters, response codes, processing time, and originating IP address for security, performance monitoring, and support purposes.

User-Submitted Data: Message samples, business information, phone numbers, and campaign details submitted via API are processed according to Privacy Policy Section 2 (Information We Collect).

Usage Analytics: Aggregated, anonymized usage metrics (request volumes, error rates, popular endpoints) used for service improvement. Individual request data retained 90 days; aggregated metrics retained indefinitely.

Data Protection Measures

Encryption:

TLS 1.3 required for all API communications (HTTPS mandatory)
Data at rest encrypted using AES-256
API keys hashed using bcrypt before database storage

Access Controls:

API keys scoped to specific account with role-based permissions
Multi-factor authentication available for API key management portal
Audit logging of all key generation, rotation, and deletion events

Retention:

Request logs retained 90 days for security and debugging
User-submitted validation data retained as per Privacy Policy Section 9 (Data Retention)
Export your data anytime via dashboard or by contacting support

Data Sharing

No Third-Party Sharing: API request data and user-submitted content not shared with third parties except:

Service providers (hosting infrastructure, analytics platforms) under strict confidentiality agreements
Legal obligations (court orders, regulatory inquiries) as described in Privacy Policy Section 6
With your explicit consent for specific purposes

Anonymized Insights: Aggregated compliance intelligence (e.g., common rejection reasons, approval rates by industry) may be published in anonymized form with all identifying details removed.

User Rights

Exercise data rights per Privacy Policy Section 8:

Access: Request copy of your API usage logs and submitted data
Deletion: Request deletion of your data (subject to legal retention requirements)
Portability: Export API request history in machine-readable JSON format
Correction: Update inaccurate account or business information

GDPR Compliance: For EEA/UK users, API operations comply with GDPR Articles 5-22. Contact dpo@mytcrplus.com for data protection inquiries.

7. Rate Limiting & Throttling

Rate Limit Enforcement

Rate limits applied per API key across all endpoints. Limits reset at start of each clock minute (requests/minute) or calendar day (requests/day).

Response Codes:

200 OK — Request processed successfully, rate limit not exceeded
429 Too Many Requests — Rate limit exceeded, includes Retry-After header with seconds until reset
503 Service Unavailable — Temporary throttling due to system load or abuse detection

Retry-After Header Example:

HTTP/1.1 429 Too Many Requests
Retry-After: 42
X-RateLimit-Reset: 1641679200

Handling Rate Limits

Best Practices:

Implement exponential backoff with jitter when receiving 429 responses
Cache validation results to avoid redundant API calls for identical input
Batch requests where possible (single API call with multiple validation items)
Monitor rate limit headers and throttle client-side before hitting limits
Use webhooks (if available) instead of polling for status updates

Sample Exponential Backoff:

import time
import random

def api_request_with_retry(url, data, max_retries=5):
    for attempt in range(max_retries):
        response = make_api_request(url, data)
        if response.status_code != 429:
            return response
        
        retry_after = int(response.headers.get('Retry-After', 60))
        jitter = random.uniform(0, 1)
        wait_time = (2 ** attempt) + retry_after + jitter
        time.sleep(wait_time)
    
    raise Exception("Max retries exceeded")

Upgrade Recommendations

If consistently approaching rate limits, consider plan upgrade:

Basic → Standard: 3x rate increase ($39.99/month)
Standard → Plus: 2x rate increase ($49.99/month)
Plus → Enterprise: Custom limits and dedicated infrastructure

Contact info@mytcrplus.com for enterprise pricing and SLA options.

8. Service Level & Availability

Uptime Commitments

Target Uptime: 99.5% monthly uptime (excludes scheduled maintenance)

Uptime Calculation:

Uptime % = (Total Minutes in Month - Downtime Minutes) / Total Minutes in Month × 100

Scheduled Maintenance: Announced 72 hours in advance via email and status page (status.mytcrplus.com, if available). Typically conducted Sunday 2-6 AM Pacific, monthly maximum 4 hours.

Service Credits: Plus and Enterprise plans receive service credits for verified outages exceeding downtime allowance:

Monthly Uptime	Service Credit
< 99.5%	10% of monthly API fees
< 99.0%	25% of monthly API fees
< 95.0%	50% of monthly API fees

Credit Claims: Submit within 30 days of outage month via info@mytcrplus.com with affected timestamps. Credits applied to next billing cycle; not redeemable for cash.

Response Time Commitments

P50 Latency Target: 200ms for validation endpoints under normal load
P95 Latency Target: 500ms for validation endpoints under normal load
P99 Latency Target: 1,000ms for validation endpoints under normal load

Database Query Endpoints: GET requests (Provider Checklist, Approval Database) may experience higher latency (500-2000ms) due to data retrieval complexity.

Performance Degradation: If latency exceeds targets by 50% for sustained 30-minute period, we investigate and deploy fixes within 4 hours. Plus/Enterprise clients receive proactive notification.

Status Monitoring

Public Status Page: Real-time API status, incident history, and maintenance schedule available at status page (URL provided upon request).

Monitoring: 24/7 automated monitoring with alerts for:

API endpoint availability (every 60 seconds)
Response time degradation (every 5 minutes)
Error rate spikes (threshold: >5% error rate sustained 10 minutes)
Rate limit anomalies indicating potential abuse

9. Intellectual Property Rights

MyTCRPlus Proprietary Rights

Owned Property: MyTCRPlus retains all ownership rights to:

API software, algorithms, validation logic, scoring models
Documentation, code samples, API specifications
Database schemas, rule engines, compliance intelligence
Trademarks, service marks, trade names, logos

License Grant: Subject to compliance with these API Terms, MyTCRPlus grants you non-exclusive, non-transferable, revocable license to access and use the API solely for purposes described in Section 4 (Fair Use Policy).

Restrictions: You may not:

Reverse engineer, decompile, disassemble API software or validation logic
Remove, obscure, or alter proprietary notices or attribution requirements
Use MyTCRPlus trademarks without prior written authorization
Create derivative works based on API responses or validation algorithms
Extract, copy, or replicate validation rules to build competing services

User Content

Your Property: You retain ownership of business information, message samples, and other content submitted via API (“User Content”).

License to MyTCRPlus: You grant MyTCRPlus non-exclusive, worldwide, royalty-free license to:

Process User Content to provide API services
Store User Content for service delivery and support purposes
Create anonymized, aggregated insights from User Content (with all identifying details removed)

License Termination: License terminates upon API access termination, with 30-day retention for transition support and legal compliance.

Attribution Requirements

Powered by MyTCRPlus: If you build customer-facing tools using the API, include attribution:

"Compliance validation powered by MyTCRPlus"

Attribution must be visible to end users (footer, settings page, or validation results display). Link to https://mytcrplus.com required unless white-label agreement obtained.

White-Label Options: Contact info@mytcrplus.com for white-label licensing removing attribution requirements (enterprise plans only).

10. Compliance Disclaimer

CRITICAL: The API provides tools supporting compliance efforts but does not constitute legal advice or guarantee compliance outcomes.

No Legal Advice

MyTCRPlus is not a law firm and does not provide legal advisory services. API validation results represent:

Automated analysis against current TCPA, CTIA, and carrier policy rules
Technical guidance based on industry best practices
Compliance intelligence derived from public regulatory frameworks

API results do NOT represent:

Legal opinions on your specific compliance situation
Guarantee of carrier approval or TCR vetting success
Protection from TCPA litigation or regulatory enforcement
Advice on consent mechanisms, record-keeping, or opt-out procedures

Client Responsibility

You remain solely responsible for:

Obtaining qualified legal counsel for TCPA, CAN-SPAM, state telemarketing law compliance
Implementing proper consent mechanisms before messaging initiation
Maintaining consent records for statutory limitation periods (4+ years recommended)
Honoring opt-out requests within legally mandated timeframes (10 business days maximum)
Monitoring regulatory changes affecting your messaging programs
Ensuring message content complies with carrier-specific content policies

Regulatory Variability

Compliance requirements vary by:

Industry Vertical: Healthcare (HIPAA), finance (GLBA), political (FEC), debt collection (FDCPA)
Message Content: Marketing vs. transactional; promotional vs. informational
Recipient Jurisdiction: State-specific telemarketing restrictions (California, Florida, Texas)
Carrier Interpretation: T-Mobile, AT&T, Verizon may enforce policies differently
Use Case Category: Low-risk (2FA, notifications) vs. high-risk (sweepstakes, debt collection)

No Guarantees

We do not guarantee:

TCR campaign approval or brand vetting outcomes
Specific trust score results or vetting timelines
Carrier approval (T-Mobile, AT&T, Verizon) or throughput allocation
Message deliverability rates or filtering avoidance
Protection from TCPA class action litigation or FTC enforcement

Final Outcomes: Campaign approval, trust scores, and carrier policies determined by The Campaign Registry (TCR), individual carriers, and factors outside MyTCRPlus control including brand reputation, message content, sending patterns, and subscriber complaint rates.

Recommendations Not Instructions

API validation recommendations (e.g., “add STOP keyword,” “include frequency disclosure”) represent best practices, not mandatory legal requirements. Legal counsel should review all recommendations in context of your specific compliance situation.

11. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW:

Liability Cap

MyTCRPlus total aggregate liability for all claims arising from API use shall not exceed the amount you paid for API services in the 12 months immediately preceding the claim. For free trial users, liability capped at $100.

Excluded Damages

MyTCRPlus is NOT liable for indirect, incidental, consequential, special, punitive, or exemplary damages, including:

Business Losses:

Lost profits, revenue, business opportunities, goodwill, or reputation damage
Costs of procurement of substitute services
Business interruption or loss of productivity

Compliance Failures:

TCR campaign rejections or brand vetting failures
Carrier suspension, filtering, or throughput throttling
TCPA penalties, class action settlements, or regulatory fines
Failed compliance audits or customer complaints

Technical Issues:

Data loss, corruption, or unauthorized access (except gross negligence)
API downtime, latency, or rate limiting impacts
Integration errors or compatibility issues
Third-party service failures (hosting, carriers, TCR)

Reliance Damages:

Decisions made based on API validation results
Campaign launches without independent legal review
Undetected compliance violations or policy changes

Disclaimers

AS-IS Basis: API provided “as is” and “as available” without warranties of any kind, express or implied, including:

Merchantability, fitness for particular purpose, non-infringement
Accuracy, reliability, or completeness of validation results
Uninterrupted, error-free, or secure operation
Compatibility with your systems or workflows

No Warranty: We do not warrant that:

API meets your specific compliance requirements
Validation rules reflect most current carrier policies (updates quarterly)
Outcomes match TCR or carrier approval decisions
API operates without bugs, errors, or downtime

Allocation of Risk

These limitations reflect the allocation of risk between parties, the fees charged for API services, and the inherently variable nature of telecommunications compliance. Some jurisdictions limit liability exclusions; in such cases, liability limited to maximum extent permitted by law.

12. Indemnification

Your Indemnification Obligations

You agree to indemnify, defend, and hold harmless MyTCRPlus, Native Chaos Holdings LLC, and our officers, directors, employees, agents, affiliates, and partners from any claims, liabilities, damages, losses, costs, or expenses (including reasonable attorneys’ fees) arising from:

API Misuse:

Violation of these API Terms or Fair Use Policy
Unauthorized API access, key sharing, or credential compromise
Circumvention of rate limits or authentication mechanisms
Use of API for prohibited purposes per Section 5

Content Violations:

User Content violating TCPA, CAN-SPAM, CTIA guidelines, or carrier policies
Illegal, fraudulent, deceptive, or harmful messaging programs
SHAFT content, high-risk financial schemes, or prohibited industries
Impersonation, phishing, malware distribution

Compliance Failures:

Messaging campaigns launched without proper consent mechanisms
TCPA class action litigation or FTC enforcement actions
Failure to honor opt-out requests or maintain consent records
Reliance on API validation without independent legal counsel

Third-Party Claims:

Allegations that your use of API violates third-party rights
Subscriber complaints regarding unauthorized messaging
Carrier disputes or policy violations
Regulatory inquiries or investigations

Indemnification Process

Notice: We will promptly notify you of any claim subject to indemnification.

Defense: You may assume defense of claim with counsel reasonably acceptable to us. We reserve right to participate in defense with own counsel at our expense.

Settlement: You may not settle any claim without our prior written consent if settlement: (a) admits liability on our behalf, (b) imposes obligations on us, or (c) does not include full release.

Cooperation: We will reasonably cooperate in defense of claim at your expense.

13. Termination & Suspension

Termination by You

Voluntary Cancellation: Cancel API access anytime by:

Emailing info@mytcrplus.com with subject “API Cancellation”
Providing 30 days written notice
Deleting API keys via dashboard

Effect: API access continues through end of current billing cycle. No refunds for prepaid fees. Data export available for 30 days post-termination.

Termination or Suspension by MyTCRPlus

Immediate Suspension (No Notice):

Material breach of API Terms (prohibited use, security violations)
Non-payment exceeding 7-day grace period
Fraudulent activity, credential compromise, or system abuse
Legal requirement or regulatory order
Conduct threatening API security, performance, or other users

Suspension with Notice (7 Days):

Repeated rate limit violations
Minor policy violations with opportunity to cure
Account verification issues requiring documentation

Permanent Termination:

Failure to cure breach within suspension period
Persistent abuse after multiple warnings
Illegal activity or TCPA violations using API
Reselling API access without authorization

Appeals: Suspended accounts may appeal to info@mytcrplus.com with detailed remediation plan. Appeals reviewed within 5 business days. Reinstatement decisions at MyTCRPlus sole discretion.

Effect of Termination

Access Revocation: All API keys invalidated immediately upon termination effective date.

Payment Obligations: Outstanding fees remain due. No refunds for prepaid monthly subscriptions or unused request allocations.

Data Export: 30-day window to export API request history and User Content. After 30 days, data deleted per retention policies.

Survival: Sections 9 (IP Rights), 10 (Compliance Disclaimer), 11 (Liability Limitation), 12 (Indemnification), and 17 (General Provisions) survive termination.

14. Fees & Payment

Pricing Structure

API access fees based on plan tier. Current pricing:

Plan	Monthly Fee	Setup Fee	Rate Limit
Free Trial	$0	$0	5 req/min, 100 req/day (30 days)
Basic	$49/month	$99	20 req/min, 2,000 req/day
Standard	$149/month	$199	60 req/min, 10,000 req/day
Plus	$299/month	$299	120 req/min, 25,000 req/day
Enterprise	Custom	Custom	Custom limits, SLA, dedicated support

Setup Fees: One-time fee covering account provisioning, API key generation, onboarding documentation. Charged upon first activation; non-refundable after key issuance.

Monthly Fees: Billed in advance on recurring subscription date. Prorated for partial months at activation.

Billing Terms

Payment Methods: Credit card, ACH transfer (Enterprise only). Payment processors: Stripe, PayPal.

Automatic Renewal: Subscriptions renew automatically unless cancelled with 30 days notice.

Failed Payments:

Grace period: 7 days from payment due date
Reminder emails sent at days 3, 5, 7
API access suspended on day 8 if payment not received
Reactivation fee: $25 after suspension
Account deletion after 60 days non-payment

Disputed Charges: Report disputes within 30 days to info@mytcrplus.com. Disputes do not suspend payment obligations pending resolution.

Price Changes

Advance Notice: Price increases require 30 days email notice to active API subscribers.

Grandfathering: Existing subscribers may maintain legacy pricing for:

Basic/Standard/Plus: Through end of current calendar quarter after notice
Enterprise: Per contract terms (typically 12 months)

New Features: Additional endpoints or premium features may carry supplemental charges with prior notice.

Refund Policy

No Refunds: API fees are non-refundable except:

Service credits for verified outages (Section 8)
Termination by us without cause (prorated refund)
Required by applicable law

Cancellation: Cancelling subscription does not entitle refund for current billing cycle. Access continues through paid period.

15. Support & Maintenance

Support Channels

Email Support: info@mytcrplus.com — All plan tiers
Phone Support: 760-269-8277 — Plus and Enterprise only
Developer Portal: https://api.mytcrplus.com/docs.html — Self-service documentation

Response Times

Plan	Response Time	Channels	Hours
Free Trial	48 hours	Email only	Business days
Basic	24 hours	Email only	Business days
Standard	12 hours	Email only	Business days
Plus	4 hours	Email, phone	24/7
Enterprise	Custom	Email, phone, Slack	24/7 with SLA

Business Days: Monday-Friday, 9 AM – 6 PM Pacific, excluding federal holidays.

Support Scope

Included:

API integration guidance and troubleshooting
Authentication and rate limit issues
Endpoint functionality questions
Error code interpretation
Documentation clarifications
Bug reports and feature requests

Not Included:

Custom integration development
Legal advice on compliance requirements
Debugging your application code
Training on TCPA, TCR, or carrier policies (see Enterprise for consulting)
Carrier-specific registration assistance (see main MyTCRPlus services)

Maintenance Windows

Scheduled Maintenance: Monthly maintenance windows announced 72 hours in advance. Typically Sunday 2-6 AM Pacific, maximum 4 hours.

Emergency Maintenance: Critical security patches or infrastructure failures may require unscheduled maintenance. Notification via status page and email.

Notification Methods:

Email to registered API account address
Status page updates (status.mytcrplus.com, if available)
API response headers during maintenance: HTTP 503 Service Unavailable

16. Changes to API & Terms

API Changes

Versioning: API uses semantic versioning (e.g., v1.2.3). Current version: v1.

Backwards Compatibility:

Minor updates (v1.X): Additive only (new endpoints, optional parameters). No breaking changes.
Major updates (vX.0): May include breaking changes. Previous major version supported for 12 months minimum.

Deprecation Notice: Endpoint deprecations announced 6 months in advance via:

Email to active API users
Developer blog (blog.mytcrplus.com, if available)
API response headers: X-API-Deprecated: true

Breaking Changes: Major version releases with breaking changes require:

12-month support period for previous version
Migration guide and code samples
Direct outreach to high-volume API users

Terms Changes

Modification Rights: We reserve the right to modify these API Terms at any time.

Notice Requirements:

Material changes: 30 days advance email notice
Non-material changes (clarifications, formatting): Effective immediately upon posting
Emergency changes (legal compliance, security): Effective immediately with post-facto notice

Acceptance: Continued API use after effective date constitutes acceptance of modified terms.

Rejection: If you do not agree to modified terms, discontinue API use before effective date and notify us for potential refund eligibility (prorated monthly fees only).

Version History: Previous versions archived and available upon request to info@mytcrplus.com.

17. General Provisions

Governing Law

These API Terms governed by Nevada state law without regard to conflict of law principles. UN Convention on Contracts for International Sale of Goods does not apply.

Dispute Resolution

Informal Resolution: Before formal proceedings, parties agree to 30-day good-faith negotiation period via email to info@mytcrplus.com.

Binding Arbitration: Disputes not resolved informally shall be resolved through binding arbitration under American Arbitration Association (AAA) Commercial Arbitration Rules.

Arbitration Terms:

Location: Las Vegas, Nevada
Single arbitrator selected per AAA procedures
Discovery limited to document exchange and one deposition per side
Arbitrator may award damages and injunctive relief, but not punitive damages exceeding statutory limits
Each party bears own attorney fees unless arbitrator awards otherwise

Class Action Waiver: You waive right to participate in class action lawsuits or class-wide arbitration. Claims must be brought individually.

Small Claims Exception: Either party may bring claims in small claims court if claim qualifies and filed individually.

Injunctive Relief: Either party may seek emergency injunctive relief in court to prevent irreparable harm pending arbitration.

Entire Agreement

These API Terms, together with MyTCRPlus Terms and Conditions and Privacy Policy, constitute complete agreement between parties regarding API services and supersede all prior agreements, representations, or understandings.

Conflicting Terms: If conflict between API Terms and general Terms and Conditions, API Terms control for API-specific matters.

Severability

If any provision held invalid or unenforceable, remaining provisions remain in full effect. Invalid provisions modified to achieve intended economic effect to extent permitted by law.

Waiver

Failure to enforce any provision does not constitute waiver of that or any other provision. Waivers must be in writing and signed by authorized representative.

Assignment

By MyTCRPlus: We may assign these API Terms in connection with merger, acquisition, or sale of assets. We will notify you of assignment 30 days in advance.

By You: You may not assign these API Terms or API access without prior written consent. Assignment without consent is void.

Effect of Assignment: Permitted assignments bind successors and assigns.

Notices

Legal Notices: Send to:

Native Chaos Holdings LLC
Attn: Legal Department
1887 Mesa Vista Dr
Henderson, NV 89014
Email: info@mytcrplus.com

Notice Effectiveness: Notices effective upon delivery confirmation or 3 business days after sending if delivery unconfirmed.

Relationship of Parties

Parties are independent contractors. These API Terms do not create partnership, joint venture, employment, or agency relationship. Neither party has authority to bind the other.

Force Majeure

Neither party liable for delays or failures caused by circumstances beyond reasonable control, including:

Natural disasters, pandemics, acts of war or terrorism
Government actions, embargoes, regulatory changes
Internet outages, DDoS attacks, ISP failures
TCR operational issues or carrier policy changes
Labor strikes, supplier failures, utility disruptions

Obligations: Affected party must provide prompt notice and use reasonable efforts to resume performance. If force majeure exceeds 60 days, either party may terminate without penalty.

Export Controls

API subject to U.S. export control laws. You represent that you are not:

Located in embargoed country (Cuba, Iran, North Korea, Syria, Crimea)
Listed on U.S. restricted party lists (SDN, Entity List, Denied Persons)
Engaged in activities prohibited under export regulations

You agree to comply with all applicable export laws and not export or re-export API access, technical data, or derivatives to prohibited destinations or persons.

Third-Party Beneficiaries

These API Terms do not confer rights upon any third party except MyTCRPlus affiliates, officers, directors, employees, and agents, who are intended beneficiaries of limitations of liability and indemnification provisions.

Headings

Section headings are for convenience only and do not affect interpretation.

18. Contact Information

General API Inquiries

Email: info@mytcrplus.com
Subject: “API Inquiry”

Phone: 760-269-8277
Business Hours: Monday-Friday, 9 AM – 6 PM Pacific

Technical Support

Email: info@mytcrplus.com
Subject: “API Support – [Brief Issue Description]”

Response Times: Per Section 15 (Support & Maintenance) based on plan tier.

API Key Issues

Email: info@mytcrplus.com
Subject: “API Key – [Generation/Rotation/Compromise]”

Compromise Response: Immediate key revocation within 1 hour during business hours; new key issued within 4 hours.

Billing & Payments

Email: info@mytcrplus.com
Subject: “Billing Inquiry – [Invoice Number or Issue]”

Phone: 760-269-8277

Enterprise Sales

Email: info@mytcrplus.com
Subject: “Enterprise API Inquiry”

Phone: 760-269-8277

Custom rate limits, SLA guarantees, white-label options, dedicated infrastructure, and premium support available.

Legal & Compliance

Mailing Address:
Native Chaos Holdings LLC
Attn: Legal Department
1887 Mesa Vista Dr
Henderson, NV 89014

Email: info@mytcrplus.com
Subject: “Legal Notice – [Topic]”

Data Protection Officer (GDPR)

Email: dpo@mytcrplus.com

For EEA/UK data protection inquiries, data subject requests, or GDPR compliance questions.

Abuse & Security

Email: info@mytcrplus.com
Subject: “Security Issue – [Urgent/Non-Urgent]”

Phone: 760-269-8277 (urgent security issues only)

Document Control

Version: 1.0
Effective Date: January 13, 2026
Last Updated: January 13, 2026
Next Scheduled Review: April 13, 2026
Document Owner: Native Chaos Holdings LLC Legal Department

Change Log:

v1.0 (2026-01-13): Initial API Terms & Fair Use Policy release

Legal Disclaimer

MyTCRPlus provides compliance validation tools supporting 10DLC registration, TCR vetting preparation, and TCPA adherence. The API delivers automated analysis against current regulatory frameworks but does not constitute legal advice or guarantee compliance outcomes. Messaging campaign approval, deliverability, and regulatory sufficiency depend on factors outside our control including brand reputation, carrier policies, TCR vetting, and evolving telecommunications regulations.

Organizations remain responsible for obtaining qualified legal counsel, implementing proper consent mechanisms, maintaining compliance records, and monitoring regulatory changes affecting their specific messaging programs. Consult legal counsel if unclear about your compliance situation.

References:

END OF API TERMS OF SERVICE & FAIR USE POLICY

MyTCRPlus API Terms of Service & Fair Use Policy

Table of Contents

1. Acceptance & Binding Agreement

2. Service Description

Available Endpoints

Service Boundaries

3. API Access & Authentication

API Key Management

Account Requirements

4. Fair Use Policy

Usage Limits

Rate Limits by Plan Tier

Acceptable Use Guidelines

Burst Allowance

Enterprise Custom Limits

5. Usage Restrictions & Prohibited Conduct

Prohibited Activities

Enforcement Actions

6. Data Privacy & Protection

Data Collection

Data Protection Measures

Data Sharing

User Rights

7. Rate Limiting & Throttling

Rate Limit Enforcement

Handling Rate Limits

Upgrade Recommendations

8. Service Level & Availability

Uptime Commitments

Response Time Commitments

Status Monitoring

9. Intellectual Property Rights

MyTCRPlus Proprietary Rights

User Content

Attribution Requirements

10. Compliance Disclaimer

No Legal Advice

Client Responsibility

Regulatory Variability

No Guarantees

Recommendations Not Instructions

11. Limitation of Liability

Liability Cap

Excluded Damages

Disclaimers

Allocation of Risk

12. Indemnification

Your Indemnification Obligations

Indemnification Process

13. Termination & Suspension

Termination by You

Termination or Suspension by MyTCRPlus

Effect of Termination

14. Fees & Payment

Pricing Structure

Billing Terms

Price Changes

Refund Policy

15. Support & Maintenance

Support Channels

Response Times

Support Scope

Maintenance Windows

16. Changes to API & Terms

API Changes

Terms Changes

17. General Provisions

Governing Law

Dispute Resolution

Entire Agreement

Severability

Waiver

Assignment

Notices

Relationship of Parties

Force Majeure

Export Controls

Third-Party Beneficiaries

Headings

18. Contact Information