Terms of Service
Trading Tech SolutionsLast updated: October 3, 2026
Clear terms for website use and remotely delivered software development and IT services.
1. About these Terms
These Terms of Service govern the use of the Trading Tech Solutions website and provide the general framework for remotely delivered software development and IT services. Trading Tech Solutions provides services to businesses through online communication and digital delivery. References to “we,” “our” and “us” mean Trading Tech Solutions; references to “you” and “the client” mean the person or organization using this website or engaging our services.
A specific project requires a written proposal, statement of work or service agreement accepted by both parties. That document identifies the contracting party, scope, deliverables, fees, timing and any additional conditions. If a signed project agreement conflicts with these general Terms, the project agreement controls for that engagement. Browsing this website or completing the project form does not by itself create a paid service contract.
2. Eligibility and authority
You must be at least 18 years old, or the age of legal majority where you live if higher, to enter a service agreement. When acting for an organization, you confirm that you have authority to communicate its requirements, grant appropriate access and accept the applicable proposal. We may request reasonable information to verify that authority before accessing systems or beginning work.
Information you provide must be accurate and lawful to share. You are responsible for keeping your contact and billing details current during an engagement. We may decline work that cannot be properly authorized, falls outside our capabilities or would require unlawful activity.
3. Services and remote delivery
Services may include custom software development, web application development, API development and integration, business process automation, database design and optimization, cloud application setup, software maintenance, troubleshooting, legacy software modernization, third-party integrations, CRM configuration, internal business tools, data migration, performance optimization and technical software audits.
All services are provided remotely. Deliverables are supplied through agreed digital channels, such as a repository, secure file transfer or approved project workspace. There is no physical product shipment or requirement for an in-person meeting. Hardware purchase, physical installation, on-site support and continuous monitoring are excluded unless separately agreed in writing.
4. Enquiries and the website form
The project form currently validates the information entered in your browser and displays an on-page acknowledgement. It does not send that information to Trading Tech Solutions, create an order, reserve development time or authorize a charge. To communicate a project enquiry, use the email address listed at the end of these Terms.
An acknowledgement displayed by the website is not acceptance of a project. Work starts only after the requirements, commercial terms and any necessary access arrangements have been agreed. Do not place passwords, financial account information, sensitive personal records or confidential source code in an initial enquiry.
5. Scope, assumptions and changes
The written scope defines the functionality, integrations, supported environments, deliverables and exclusions for each project. Estimates depend on the information available when the proposal is prepared. Requirements that have not been expressly included are outside the agreed scope, even where they relate to the same application or business process.
If requirements change, we discuss the effect on price and scheduling before carrying out additional work. A change request should identify the requested adjustment and be confirmed in writing by authorized representatives. Discovery of undocumented dependencies, inaccessible systems or materially different data may also require a revised proposal.
6. Client responsibilities and access
You provide the requirements, materials, decisions and authorized access reasonably needed for the work. You must have the rights to all code, data, accounts and other materials you ask us to use. Third-party access permissions and licenses remain your responsibility unless the proposal specifically assigns them to us.
Where production access is necessary, the parties agree an appropriate method and level of access. You should maintain suitable backups and avoid sharing credentials through insecure channels. Delays in access, approvals, information or third-party responses may change the schedule. We are not responsible for a failure caused solely by inaccurate instructions or unauthorized materials supplied by the client.
7. Prices, proposals and payment
Website prices are starting budgets in United States dollars for a defined minimum engagement. They are not fixed quotes for every project. The accepted proposal confirms the total fee or applicable billing method, the payment schedule and any required deposit. There is no automatic checkout or payment collection through the project form.
Third-party software subscriptions, cloud usage, external services and applicable taxes are additional unless expressly included. Invoices state their due dates and the approved payment instructions. Do not rely on a change to payment instructions without verifying it through an established contact channel. Work may be postponed or suspended for overdue undisputed payments after reasonable notice.
8. Scheduling and communication
Project schedules depend on the scope, complexity, dependencies and availability of client feedback. Dates in a proposal are estimates unless the agreement expressly identifies a binding deadline. When a material delay becomes apparent, the parties should discuss the revised schedule and practical options.
Updates, approvals and requests are handled online through agreed communication channels. Emergency response, weekend work, guaranteed response times and round-the-clock availability are not included unless specifically stated in the service agreement. No general website description constitutes a service-level agreement.
9. Testing, review and acceptance
Completed work is tested against the agreed scope and delivered for review in the specified environment. You should report any apparent non-conformity with sufficient information to reproduce it, including the affected functionality, expected result and relevant conditions. The project agreement defines the review period and acceptance procedure.
A reproducible issue within the agreed scope is considered separately from a request for new functionality or a change to the original requirements. Known limitations and any outstanding items should be recorded at handover. No software can be assumed to be free of all defects or compatible with every untested environment.
10. Ownership, source code and licenses
Ownership of specifically commissioned deliverables, source code access and any transfer of rights are defined in the project agreement. Unless that agreement states otherwise, a transfer of agreed rights becomes effective after full payment of the relevant fees. You retain ownership of materials that you supplied and authorized us to use.
Pre-existing tools, reusable libraries, development methods and general know-how remain the property of their respective owners. Open-source packages and third-party products remain subject to their own license terms. You do not receive ownership of those materials merely because they are used in a deliverable. Any required license permissions should be documented in the project handover.
11. Confidentiality and project information
Each party should treat non-public business, technical and account information disclosed for a project as confidential, use it for the agreed engagement and limit access to people who need it for that purpose. These expectations do not apply to information that is already public through no breach, independently developed, lawfully obtained elsewhere or required to be disclosed by law.
Additional confidentiality requirements, retention limits and permitted subcontracting should be addressed in a written agreement. Client names, confidential project details and private deliverables should not be published as marketing material without the client’s written permission. Confidentiality does not prevent either party from keeping records reasonably necessary for billing, legal compliance or resolving a dispute.
12. Client data, migrations and backups
Data access and migration activities are limited to the agreed scope. The proposal should identify the data sources, intended destination, validation approach, cutover procedure and responsibilities for backup and rollback. You remain responsible for the lawfulness of the data supplied and for authorizing any transfer between systems.
A successful trial does not eliminate every risk associated with a production migration. Unexpected format differences, existing corruption or restrictions imposed by another provider may affect the outcome. We do not promise zero downtime or zero data loss for every engagement. Any particular continuity or recovery commitment must be documented in the project agreement.
13. Third-party platforms and audit limitations
Services may depend on third-party APIs, hosting platforms, CRM systems or licensed software. Their availability, prices, limits and behavior are controlled by their providers and may change. Fees for external accounts are your responsibility unless the proposal states otherwise. Changes made by another provider after delivery may require additional maintenance.
A technical audit evaluates the accessible materials and agreed areas at the time of review. It is not a guarantee that every vulnerability, defect or performance issue has been identified. Audits do not constitute a certification, legal opinion or promise that a system cannot be compromised. Recommendations should be prioritized in the context of the client’s business and technical requirements.
14. Maintenance and ongoing work
Maintenance is a separate engagement unless it is expressly included in a project. The starting monthly package includes a defined allowance of 16 engineering hours, with the work priorities and any exclusions agreed in the maintenance proposal. Additional hours, carry-over rules, availability and response expectations must be specified in that agreement.
An ongoing maintenance arrangement does not make us responsible for systems or services that are outside its scope. Major new features, full redesigns and repairs caused by unauthorized changes may require a separate quote. Any renewal, notice period or price change for a continuing service should be clearly stated in the accepted agreement.
15. Cancellation, refunds and unused payments
You may request cancellation in writing using the project’s established contact channel. The financial effect depends on the accepted proposal, the work already completed and any non-cancellable external commitments approved for the engagement. Completed and properly documented work remains payable. A cancellation does not automatically entitle the client to a refund of all fees.
Unless a different lawful rule is agreed in writing, prepaid amounts allocated to work that has not been performed are reconciled against completed work and approved non-recoverable costs. Any resulting refundable balance is returned through an appropriate payment method within 30 days after the reconciliation is agreed, subject to payment-provider processing. If we cancel an engagement without client fault, the same principle applies to unearned prepaid fees. Statutory rights that cannot lawfully be excluded remain unaffected.
16. Acceptable use
You must not misuse the website or request work involving unauthorized access, malware, fraud, infringement, unlawful surveillance or deliberate disruption of another system. You must not attempt to bypass access controls or use another person’s identity or credentials without permission. Materials you supply must not violate another person’s rights.
We may restrict access to the website or decline or suspend an engagement where reasonably necessary to address unlawful activity, security concerns or a material breach of the agreement. Any financial reconciliation on termination is handled according to the applicable project terms and mandatory law.
17. Warranties and limits of liability
We undertake to perform agreed services with reasonable professional care. Any specific warranty, correction period or service-level commitment must be set out in the project agreement. To the extent permitted by law, general website information is provided without a guarantee of uninterrupted availability, complete accuracy or suitability for a particular project.
To the extent permitted by applicable law and unless a project agreement provides otherwise, neither party is liable to the other for indirect or consequential losses, including lost anticipated profits, arising from the engagement. Our aggregate liability for a service-related claim is limited to the fees paid for the affected engagement during the 12 months preceding the event giving rise to that claim. These limits do not exclude fraud, willful misconduct or any liability or remedy that the law does not allow to be limited.
18. Governing law, disputes and changes
Unless the project agreement provides otherwise, these Terms are governed by the laws of Wyoming, United States, without overriding mandatory protections that apply to you. The parties should first attempt to resolve a dispute through written discussion. Subject to any mandatory jurisdiction rules, disputes that cannot be resolved informally may be brought before a court of competent jurisdiction in Wyoming.
We may update these Terms to reflect changes to the website or our services. The current revision date is displayed above. A website update does not retrospectively change a signed project agreement; amendments to an existing engagement require the procedure stated in that agreement. If any provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law.
