Terms of Service

2.1 Account Creation

To use the Service, you must create an Account by providing a valid email address. We use magic link authentication — no passwords are stored. You are responsible for maintaining the security of your email account and API Keys.

2.2 Eligibility

You must be at least 18 years old and capable of forming a binding contract under applicable law. The Service is available to individuals (including sole proprietors without an EIN) and business entities. You represent that all information provided during account creation and registration is accurate, current, and complete.

2.3 One Account Per Entity

Each business entity or sole proprietorship should maintain a single Account. Multiple Accounts created to circumvent usage limits, enforcement actions, or pricing tiers may be terminated.

2.4 Accuracy of Information

You agree to maintain accurate and current Account information. Misrepresentation of your business type, use case, or entity information — whether during account creation, registration, or at any time thereafter — constitutes a material breach of these Terms.

3.1 What RelayKit Provides

RelayKit is a compliance-first SMS API platform that automates A2P 10DLC registration for US carriers. The Service includes:

• Free sandbox environment for building and testing SMS integrations
• Dashboard with use case selection and message plan builder
• Automated 10DLC registration including brand registration and campaign registration
• Message routing with carrier-rule compliance checks

3.2 ISV Model

RelayKit operates as an Independent Software Vendor (ISV) registered with Sinch. Your phone number and messaging infrastructure are provisioned under RelayKit's ISV account using dedicated subaccounts. You do not need a Sinch account to use the Service.

3.3 What RelayKit Is Not

RelayKit is not a law firm and does not provide legal advice. The compliance tooling, templates, guidelines, industry-specific guidance, and enforcement mechanisms provided through the Service are best-effort engineering controls designed to help you comply with carrier requirements and applicable regulations. They do not constitute legal counsel, regulatory assurance, or a guarantee of compliance with any law, regulation, or carrier policy.

You are solely responsible for ensuring that your use of SMS messaging complies with all applicable laws, including but not limited to the Telephone Consumer Protection Act (TCPA), state consumer protection laws, and industry-specific regulations. We strongly recommend consulting with qualified legal counsel regarding your specific obligations.

4.1 Sandbox Access

The sandbox is available at no cost immediately upon Account creation. No credit card or payment is required. The sandbox provides outbound and inbound SMS testing, opt-out handling, and message plan building.

4.2 Sandbox Limitations

Sandbox messages are routed through a shared development phone number and are intended for testing purposes only. Sandbox API Keys (prefixed rk_test_) may not be used for production messaging. RelayKit reserves the right to impose rate limits, message caps, or other restrictions on sandbox usage at any time.

4.3 Sandbox Availability

The sandbox is provided on an as-available basis. We may modify, suspend, or discontinue sandbox access at any time without notice. Sandbox availability does not create any obligation to provide paid services.

5.1 Registration Process

When you are ready to send production SMS messages, you must complete the registration process, which includes:

1. Completing the intake wizard with your business details and use case information
2. Reviewing and confirming the campaign description and sample messages generated on your behalf
3. Acknowledging the compliance monitoring consent (Section 9)
4. Completing payment through Stripe checkout

Upon successful payment, RelayKit submits your 10DLC brand and campaign registration to US carriers through The Campaign Registry.

5.2 Registration Accuracy

The registration artifacts — including campaign descriptions and sample messages — are generated based on information you provide. You are responsible for reviewing these artifacts before submission. Campaign descriptions and sample messages are presented as read-only in the review screen because they are optimized for carrier approval. If the information you provided is inaccurate, contact us before confirming your registration.

5.3 Registration Timeline

Campaign registration is reviewed by US carriers. Carrier review timelines vary. RelayKit does not control carrier review timelines and cannot guarantee approval by a specific date. Your sandbox remains fully functional during the review period.

5.4 Registration Rejection

If your registration is rejected by carriers, RelayKit will work to resolve the rejection and resubmit at no additional cost. We will notify you of the rejection reason and any information needed from you. Repeated rejections caused by inaccurate or misleading information you provided may result in Account review.

6.1 Setup Fee

A one-time setup fee of $49 is charged at checkout. This fee covers 10DLC registration, Sinch subaccount provisioning, carrier submission, and rejection handling.

6.2 Monthly Subscription

A recurring monthly subscription begins upon checkout:

• Transactional messaging: $19/month — includes 500 SMS segments, a dedicated phone number, message routing through compliance checks, and registration as carrier-submission CTA.
• With marketing campaigns: $29/month — includes everything in transactional, plus marketing campaign registration and recipient-level marketing consent enforcement.

Your tier is determined by your use case selection during the registration process. Marketing campaigns require an EIN.

6.3 Message Overage

Additional messages are billed at $8 per 500 messages. Volume pricing is available above 5,000 messages per month — contact us for details. Overage charges require a valid payment method on file.

6.4 Payment Processing

All payments are processed through Stripe. By providing payment information, you authorize RelayKit and Stripe to charge your payment method for applicable fees. You are responsible for maintaining a valid payment method.

6.5 Subscription Cancellation

You may cancel your monthly subscription at any time through the Stripe billing portal. Upon cancellation:

• Messaging is paused immediately (outbound messages will not be delivered)
• Your registration data is retained for carrier audit purposes per regulatory requirements
• Your Account data is retained for 90 days before permanent deletion
• Your sandbox continues to function
• No prorated refund is issued for the current billing period

6.6 Payment Failure

If a subscription renewal payment fails, you will be notified and given a 7-day grace period to update your payment method. If payment is not received within the grace period, messaging services will be suspended. Account data retention follows the same policies as voluntary cancellation.

6.7 Refund Policy

The $49 setup fee is non-refundable once the registration process has been initiated, except at RelayKit's sole discretion. Monthly subscription fees are non-refundable for partial billing periods.

No refunds are issued for fees associated with Accounts terminated for violations of these Terms or the AUP, misrepresentation of business information, or submission of fraudulent registration data. This includes both the setup fee and any remaining prepaid subscription period.

8.1 End User Consent

You are solely responsible for obtaining, documenting, and maintaining valid consent from each End User before sending them SMS messages. At minimum, this requires:

• Express written consent for transactional messages, obtained through a clear opt-in mechanism that identifies your business name, the type of messages the End User will receive, the message frequency, and how to opt out.
• Express written consent with clear and conspicuous disclosure for marketing or promotional messages, as required by the TCPA and applicable state laws.
• Maintaining records of consent sufficient to demonstrate compliance if challenged.

You are responsible for implementing the opt-in mechanism in your application and ensuring it meets the requirements of applicable law.

8.2 Opt-Out Handling

End Users must be able to opt out of receiving messages at any time by replying STOP (or equivalent keywords). RelayKit enforces opt-out handling — messages to opted-out recipients are automatically blocked. However, you must:

• Include opt-out instructions in the first message to any new recipient
• Honor opt-out requests without delay
• Not attempt to circumvent or override the opt-out enforcement system
• Not re-subscribe opted-out recipients unless they independently text START to your number

8.3 Message Content

You are responsible for ensuring that the content of your messages:

• Is consistent with your registered use case and Canon Messages
• Complies with the AUP
• Does not contain prohibited content as defined in the AUP
• Includes your business name for sender identification
• Complies with all applicable laws and regulations

8.4 Compliance with Laws

You agree to comply with all applicable federal, state, and local laws governing SMS messaging, including but not limited to:

• The Telephone Consumer Protection Act (TCPA)
• The CAN-SPAM Act (to the extent applicable to SMS)
• State consumer protection and privacy laws (including CCPA/CPRA where applicable)
• Federal Communications Commission (FCC) regulations
• Carrier-specific content and conduct policies

8.5 API Key Security

You are responsible for the security of your API Keys. Do not share API Keys publicly, commit them to public repositories, or embed them in client-side code. Notify RelayKit immediately if you believe an API Key has been compromised. RelayKit is not liable for unauthorized use of your API Keys.

9.1 Consent to Monitoring

By using the Service, you acknowledge and agree that RelayKit processes outbound SMS message content for the purposes of compliance enforcement and platform integrity. This includes:

• Scanning for opt-out requests and ensuring opted-out recipients do not receive further messages
• Monitoring for sender identification and required disclosures in messages to new recipients
• Reviewing message patterns for consistency with your registered use case

9.2 Message Blocking

RelayKit may block individual messages before they reach carriers if they violate compliance rules. You acknowledge that RelayKit has no liability for blocked messages, including any business impact resulting from non-delivery. Blocked messages generate error responses with actionable error codes so you can correct the issue in your application.

9.3 No Sale of Message Data

RelayKit does not sell, share, or disclose the content of your messages to third parties, except as required by law or as necessary to operate the Service (e.g., routing messages through carrier infrastructure). Message content is processed for compliance enforcement purposes only.

9.4 Data Retention

Message metadata (timestamps, recipient phone numbers, delivery status, compliance check results) is retained for 90 days for compliance audit purposes. Full message content is retained for 30 days for dispute resolution, then permanently deleted.

10.1 RelayKit IP

The Service, including all software, APIs, documentation, templates, and infrastructure, is the property of RelayKit LLC and is protected by applicable intellectual property laws. These Terms grant you a limited, non-exclusive, non-transferable, revocable license to use the Service in accordance with these Terms.

10.2 Generated Artifacts

Artifacts generated on your behalf (campaign descriptions, sample messages) are provided for your use in connection with the Service. You may not resell, redistribute, or use these artifacts to provide a competing service.

10.3 Your Content

You retain ownership of all content you create, including message text, business information, and application code. By using the Service, you grant RelayKit a limited license to process your content as necessary to provide the Service, including compliance enforcement and registration submission.

10.4 Feedback

If you provide feedback, suggestions, or ideas regarding the Service, you grant RelayKit a perpetual, irrevocable, royalty-free license to use that feedback for any purpose without obligation to you.

11.1 Enforcement Actions

RelayKit may take one or more of the following enforcement actions if we reasonably believe you have violated these Terms or the AUP:

• Warning: Written notice identifying the violation and required corrective action.
• Message blocking: Increased inline enforcement thresholds or manual blocking rules applied to your Account.
• Rate reduction: Reduction of your messaging throughput.
• Suspension: Temporary suspension of your ability to send messages, with or without prior notice depending on the severity of the violation.
• Termination: Permanent termination of your Account and all associated services.

11.2 Immediate Termination

RelayKit may terminate your Account immediately and without prior notice for:

• Misrepresentation of your business type, entity status, or use case during registration
• Sending messages containing content prohibited under the AUP, particularly SHAFT-C content
• Repeated or egregious violations of the AUP after a warning has been issued
• Conduct that poses an immediate risk to RelayKit's ISV account, carrier trust score, or other customers
• Fraudulent activity, including submitting false business information or forged consent records
• Use of the Service in connection with any illegal activity

11.3 Effect of Termination

Upon termination for cause:

• All messaging services are immediately suspended
• No refund is issued for the setup fee or any remaining subscription period
• API Keys are revoked immediately
• Account data is retained for 90 days for audit purposes, then permanently deleted
• You remain liable for any fees incurred prior to termination

11.4 Voluntary Termination

You may close your Account at any time by canceling your subscription and contacting support. Voluntary termination follows the cancellation procedures in Section 6.5.

11.5 Survival

Sections 3.3 (What RelayKit Is Not), 6.7 (Refund Policy), 8 (Developer Responsibilities), 10 (Intellectual Property), 12 (Limitation of Liability), 13 (Indemnification), 14 (Disclaimer of Warranties), and 15 (Dispute Resolution) survive termination of these Terms.

12.1 Cap on Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, RELAYKIT'S TOTAL AGGREGATE LIABILITY TO YOU FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICE SHALL NOT EXCEED THE GREATER OF (A) THE TOTAL FEES PAID BY YOU TO RELAYKIT IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM, OR (B) ONE HUNDRED DOLLARS ($100).

12.2 Exclusion of Damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL RELAYKIT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO LOSS OF PROFITS, REVENUE, DATA, OR BUSINESS OPPORTUNITIES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT, STRICT LIABILITY, OR OTHERWISE, EVEN IF RELAYKIT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

12.3 Specific Exclusions

Without limiting the foregoing, RelayKit is not liable for:

• Carrier rejection, delay, or failure of your 10DLC registration
• Messages blocked by RelayKit for compliance reasons
• Temporary or permanent suspension of messaging services due to carrier action
• Changes to carrier policies, TCR requirements, or regulatory requirements that affect your registration or messaging capabilities
• TCPA fines, penalties, or litigation arising from your messaging practices
• End User complaints, opt-out failures caused by your application, or consent disputes
• Service interruptions caused by third-party infrastructure (Sinch, carriers, Stripe, Cloudflare)

15.1 Governing Law

These Terms are governed by and construed in accordance with the laws of the State of South Carolina, without regard to its conflict of laws provisions.

15.2 Informal Resolution

Before initiating any formal dispute resolution, you agree to contact RelayKit at support@relaykit.ai and attempt to resolve the dispute informally for at least thirty (30) days.

15.3 Jurisdiction

Any disputes not resolved informally shall be resolved exclusively in the state or federal courts located in Charleston County, South Carolina. You consent to the personal jurisdiction of such courts.