Service Agreement

Last Updated: March 14, 2026 Effective Date: March 14, 2026

Introduction

This Service Agreement ("Agreement") describes the standard terms governing how RCKSTRT provides custom software development services and how clients and partners engage with those services. This Agreement applies to all project engagements and is incorporated by reference into the RCKSTRT Terms of Service.

The specific scope, pricing, timeline, deliverables, and commercial terms for your engagement are set out in the applicable project agreement, partnership agreement, proposal, order form, statement of work, or the checkout and onboarding flow within the platform. Where any project-specific document conflicts with this Agreement, the project-specific document controls for that engagement.

1. Scope of Work

1.1 Project Definition

Before project work begins, RCKSTRT will work with you to establish the scope of the engagement. Scope definition may occur through a discovery session, technical specification process, proposal, statement of work, or a structured intake and approval flow within the platform depending on the engagement type.

A project scope covers, as applicable:

the type of application or software to be developed (web, mobile, cross-platform, or a combination);
the key features and functional requirements;
the platforms and environments to be targeted;
any specific third-party integrations required;
performance, accessibility, or compliance requirements disclosed during intake; and
delivery milestones and acceptance criteria.

1.2 Scope Changes

RCKSTRT develops software to the scope confirmed at the time work begins. Requests for work outside the confirmed scope — including new features, modifications to approved designs, additional integrations, and changes to requirements — are treated as scope changes ("Change Orders").

Change Orders:

must be requested through the platform workspace or in writing by email;
will be reviewed and priced by RCKSTRT before any work begins on the additional scope;
require your written or platform-based approval before they are executed and billed; and
may affect the project timeline and delivery date.

RCKSTRT will not perform Change Order work or bill for Change Orders without prior approval. Approval of a Change Order constitutes an amendment to the original project scope and billing terms.

1.3 Discovery and Technical Specification

For complex engagements, RCKSTRT may conduct a discovery or technical specification phase before development begins. This phase produces documented requirements, architecture decisions, and a development plan. Discovery work is billed as part of the project engagement and is non-refundable once completed, as it represents delivered work product.

2. Delivery

2.1 Timeline Estimates

RCKSTRT will provide estimated delivery timelines in the project agreement, proposal, or intake confirmation. Timelines are estimates based on confirmed scope at the time of agreement. RCKSTRT will communicate proactively if a material delay is anticipated.

Delivery timelines may be affected by:

scope changes after project kickoff;
delays in receiving required materials, approvals, or feedback from you;
third-party API or service dependencies outside RCKSTRT's control;
technical complexity discovered during development not apparent at scoping; and
force majeure events as described in the Terms of Service.

RCKSTRT will not be liable for timeline delays caused by client-side delays in providing materials, responding to questions, or approving milestones.

2.2 Milestones and Approvals

Where a project is structured with defined milestones:

RCKSTRT will submit each milestone for your review and approval through the platform workspace;
you will have a reasonable review period (stated in the project agreement or, if not stated, 5 business days) to review and respond;
if you do not respond within the review period, the milestone may be deemed approved and the project will advance;
approval of a milestone is your acknowledgment that the delivered work meets the agreed requirements for that milestone; and
material rework requests after milestone approval may be treated as Change Orders.

2.3 Final Delivery and Handoff

Upon project completion:

RCKSTRT will conduct final delivery through the platform, including deployment to a staging or production environment as agreed;
you will have a final review period to accept delivery, which may be stated in the project agreement (if not stated, 7 business days applies by default);
RCKSTRT will provide reasonable handoff documentation, including access credentials, environment variables, deployment instructions, and repository access as applicable; and
transfer of ownership (where applicable) follows the process described in Section 4 of the Terms of Service and will not occur before all applicable payment and administrative conditions are satisfied.

2.4 Hosted vs. Transferred Deployments

RCKSTRT may offer to maintain hosting, deployment, or infrastructure management for your application on an ongoing basis as described in your project agreement. If no post-delivery hosting arrangement is agreed:

during an active monthly plan, RCKSTRT may create or control project-specific runtime accounts in its own name or workspace for hosting, database, monitoring, or deployment convenience;
third-party subscription, usage, hosting, and infrastructure costs associated with those project-specific runtime accounts remain your responsibility and may be invoiced separately or forwarded to you as pass-through charges if stated in the project agreement, checkout flow, or invoice;
RCKSTRT will facilitate a transfer of the application to your own hosting environment as part of the handoff;
you are responsible for ongoing infrastructure costs after transfer; and
RCKSTRT is not responsible for application performance, uptime, or security after ownership and hosting transfer is complete.

3. Client Responsibilities

3.1 Timely Input and Materials

To enable RCKSTRT to deliver projects on schedule, you agree to:

provide all required content, copy, brand assets, credentials, third-party access, and other materials within the timeframes specified in the project agreement or reasonably requested during the project;
respond to requests for clarification, decisions, and milestone approvals within the review periods established in the project agreement;
designate a primary point of contact authorized to make project decisions on your behalf; and
notify RCKSTRT promptly if there is a change to your requirements, timeline preferences, or business context that may affect the project.

Delays caused by late delivery of materials, extended review periods, or unresponsiveness may extend the project timeline and RCKSTRT will not be liable for resulting delays.

3.2 Accurate Information

You represent and warrant that:

all information, materials, and requirements you provide to RCKSTRT are accurate, complete, and not misleading;
you own or have all necessary rights, licenses, and permissions to provide project materials (including third-party content, trademarks, designs, and APIs) to RCKSTRT for use in the project;
the development work you are requesting is lawful in your jurisdiction and in the jurisdictions where the resulting software will be used; and
you will promptly disclose any material constraints, regulatory requirements, or risks that may affect the project that you become aware of during the engagement.

3.3 Regulatory and Compliance Obligations

RCKSTRT builds software to your stated specifications. You are responsible for ensuring that your project requirements, business model, and the resulting software comply with applicable laws, regulations, and industry standards in your jurisdiction, including but not limited to:

data protection and privacy laws (e.g., GDPR, CCPA, HIPAA if applicable);
financial regulations (e.g., money transmission laws, securities regulations);
accessibility standards (e.g., WCAG 2.1 — if a specific accessibility standard is a requirement, it must be included in the project scope); and
any sector-specific regulatory requirements.

RCKSTRT does not provide legal, compliance, or regulatory advice. If your project requires regulatory compliance, you should engage appropriate professional advisors.

3.4 Third-Party Services and Accounts

If your project requires integrations with third-party services (e.g., payment processors, CRMs, social platforms, databases):

you are generally responsible for establishing and maintaining accounts with those third-party services, especially where the service is tied to your legal identity, payouts, publishing rights, or domain ownership;
if RCKSTRT creates or manages a project-specific runtime or tooling account during the monthly plan term for delivery convenience, you remain responsible for the costs associated with that account and those costs may be invoiced separately or forwarded to you as pass-through charges;
you grant RCKSTRT access credentials and authorization only for the purpose of building and configuring the integration; and
RCKSTRT is not responsible for the availability, performance, pricing changes, or policy changes of third-party services.

4. Intellectual Property

4.1 Client Materials

You retain ownership of all materials, content, and assets you provide to RCKSTRT for use in the project. By providing these materials, you grant RCKSTRT a limited license to use them solely for the purpose of performing the project work.

4.2 Project Deliverables

Ownership of project deliverables is governed by Section 4 of the Terms of Service. During an active monthly plan, you receive a limited software license. Ownership transfers upon satisfaction of the conditions in the applicable project or partnership agreement.

4.3 Open-Source Components

Project deliverables may incorporate open-source software, libraries, and frameworks. These components remain subject to their respective open-source licenses (such as MIT, Apache 2.0, GPL). RCKSTRT will disclose material open-source components in the project agreement or technical specification documentation.

You are responsible for understanding and complying with open-source license obligations applicable to how you deploy and distribute the delivered software. RCKSTRT does not warrant that all open-source components included in a project will remain compatible with your intended use or business model over time.

4.4 RCKSTRT Platform and Internal Tools

RCKSTRT retains all rights to its platform, internal tools, design systems, workflow templates, reusable code libraries, and other internal assets, even where these are used in the delivery of your project. These assets are not assigned or transferred to you as part of a project deliverable.

4.5 Pre-existing Work

Any code, tools, or frameworks developed by RCKSTRT prior to or outside of your specific engagement ("Background IP") that are incorporated into your project deliverables are licensed to you on a non-exclusive basis for use with the delivered software. Background IP is not assigned or transferred to you.

5. Confidentiality

5.1 Obligations

Each party may receive confidential information of the other party in connection with a project engagement ("Confidential Information"). Each party agrees to:

use Confidential Information only for the purposes of performing or receiving the Service;
maintain the confidentiality of the other party's Confidential Information with at least the same degree of care used for its own confidential information, but no less than reasonable care;
not disclose Confidential Information to any third party without the other party's prior written consent, except to employees, contractors, or service providers who need to know it for project purposes and are bound by confidentiality obligations at least as protective as those in this Section; and
notify the other party promptly upon becoming aware of any unauthorized disclosure or use of Confidential Information.

5.2 Exceptions

Confidentiality obligations do not apply to information that:

is or becomes publicly available through no fault of the receiving party;
was already known to the receiving party before disclosure;
is independently developed by the receiving party without use of Confidential Information;
is received from a third party who is not under a confidentiality obligation; or
must be disclosed pursuant to applicable law, regulation, or court order (provided that the disclosing party gives the other party prompt notice and cooperates with any efforts to seek a protective order, to the extent permitted by law).

5.3 Duration

Confidentiality obligations survive the termination of the project engagement for a period of 3 years, except for trade secrets, which remain protected for as long as they qualify as trade secrets under applicable law.

6. Warranties

6.1 RCKSTRT Warranties

RCKSTRT warrants that:

project deliverables will be developed with reasonable care and skill;
RCKSTRT has the right to enter into this Agreement and to perform the services described herein;
RCKSTRT will not knowingly incorporate third-party materials into project deliverables in a way that infringes the rights of the third party; and
RCKSTRT will perform services in compliance with applicable law.

6.2 Warranty Period and Remedy

RCKSTRT will address material defects (bugs or functional failures against the agreed specifications) that are reported within 30 days of final delivery at no additional charge, subject to the following:

the defect must be reproducible and traceable to the delivered work;
you must report the defect through the platform workspace or by email to hi@rckstrt.com within the warranty period; and
the warranty does not cover defects caused by your modifications, third-party software changes, infrastructure changes outside RCKSTRT's control, or scope items not included in the original confirmed deliverables.

After the warranty period, defect remediation may be billed as Change Order or support work.

6.3 Disclaimer of Other Warranties

EXCEPT AS EXPRESSLY STATED IN SECTION 6.1 AND 6.2, PROJECT DELIVERABLES AND THE SERVICE ARE PROVIDED "AS IS." RCKSTRT DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT, EXCEPT AS REQUIRED BY APPLICABLE LAW.

7. Support and Maintenance

7.1 Post-Delivery Support

Post-delivery support and maintenance — including hosting management, security updates, dependency updates, performance monitoring, and ongoing development — are not included in the base project price unless explicitly agreed in a separate support arrangement or stated in the project agreement.

If you require post-delivery support, RCKSTRT may offer ongoing support arrangements at rates and terms to be agreed in writing.

7.2 No Ongoing Obligation

In the absence of a post-delivery support agreement, RCKSTRT has no ongoing obligation to maintain, update, or support project deliverables after the warranty period expires. You are responsible for maintaining your infrastructure, dependencies, and security posture after delivery and ownership transfer.

8. Suspension and Termination of Services

8.1 Suspension for Non-Payment

RCKSTRT may pause or suspend active project work if payment obligations are not met, as described in the Payment and Refund Policy. Work will resume upon resolution of the payment issue.

8.2 Termination for Cause

Either party may terminate a project engagement for cause if the other party:

materially breaches the project agreement and fails to cure the breach within 14 days of written notice; or
becomes insolvent, files for bankruptcy, or makes an assignment for the benefit of creditors.

8.3 Effect of Termination

Upon termination of a project engagement:

RCKSTRT will cease performing work on the project;
you remain responsible for payment of all amounts due for work performed up to the date of termination;
RCKSTRT may retain ownership of project deliverables until all outstanding amounts are paid unless otherwise required by applicable law; and
work product that has been completed and paid for will be made available to you in a reasonable format subject to the payment and ownership conditions in the Terms of Service.

9. Limitation of Liability

Liability in connection with project engagements is subject to the limitations set out in Section 12 of the Terms of Service, including the cap on RCKSTRT's total liability and the exclusion of indirect, incidental, and consequential damages. These limitations apply regardless of the theory of liability.

10. Dispute Resolution

Disputes arising from a project engagement are subject to the dispute resolution process in Section 16 of the Terms of Service, including informal resolution, binding arbitration, and the class action waiver. Project-specific written agreements may specify alternative dispute resolution procedures, which will control if they conflict with the Terms of Service dispute resolution provisions.

11. General

11.1 Relationship of the Parties

RCKSTRT is an independent contractor. Nothing in this Agreement creates an employment, partnership, joint venture, or agency relationship between RCKSTRT and you.

11.2 Subcontractors

RCKSTRT may use subcontractors, employees, or independent contributors to perform project work. RCKSTRT remains responsible for work performed by its subcontractors under this Agreement.

11.3 Governing Law

This Agreement is governed by the laws of the State of Delaware, United States, consistent with the Terms of Service.

11.4 Entire Agreement

This Agreement, together with the Terms of Service, Privacy Policy, Payment and Refund Policy, Acceptable Use Policy, and the applicable project-specific agreement, constitutes the entire agreement between the parties with respect to project services and supersedes all prior discussions, proposals, and understandings regarding the same subject matter.

12. Contact Information

For questions about this Agreement or project service terms:

RCKSTRT Email: hi@rckstrt.com Support: hi@rckstrt.com Website: rckstrt.com

By using RCKSTRT and engaging in a project, you acknowledge that you have read, understood, and agree to this Service Agreement.