These terms govern all services provided by RuutDev. Please read them carefully before engaging with our services.
These Terms & Conditions ("Terms") govern the relationship between RuutDev ("we," "us," "RuutDev") — operated by Johan Tovar — and any individual or business ("Client," "you") that engages our services, whether through our website, email, WhatsApp, or any other channel.
By requesting a demo, signing a proposal, or making a payment, you agree to be bound by these Terms. If you do not agree with any part of these Terms, do not engage our services.
These Terms apply to all services including, but not limited to: website development, software and web application development, AI integrations, automations, hosting, technical support, and monthly maintenance plans.
RuutDev provides the following categories of services:
The exact scope of any project is defined in a written proposal provided to the Client before work begins. Work is governed by the scope in the accepted proposal.
RuutDev offers a complimentary working demo of a proposed website or project, delivered within approximately 48 hours of the initial consultation. The demo is provided at no cost and with no obligation to proceed.
All project costs are quoted in US dollars (USD) and confirmed in a written proposal. Payments are split into milestones based on project value:
| Plan | Project Value | Payment Schedule |
|---|---|---|
| Plan A | Under $800 | 50% deposit to start · 50% on launch |
| Plan B | $800–$2,000 | 40% deposit · 30% at delivery · 30% on launch |
| Plan C | Over $2,000 | 33% deposit · 33% at delivery · 34% within 30 days of launch |
Accepted payment methods: Zelle, PayPal, and bank transfer (USD only). Credit/debit card payments via Stripe may be available for select clients upon request. Payment method availability will be confirmed in the written proposal.
Late payments: A 10% late fee applies to invoices unpaid after a 14-day grace period.
Deposits are non-refundable once work has commenced. Once RuutDev begins development — including research, design, or architecture work — the deposit is earned and will not be refunded, regardless of whether the project is completed.
Project commencement: Work begins only after the Client has signed or accepted the written proposal and the deposit has cleared.
RuutDev offers optional monthly maintenance plans for ongoing care of websites, software, and advanced systems. These plans are separate from and independent of the one-time project cost.
Pricing may vary based on scope. The exact plan and price will be confirmed in writing before the plan begins.
Maintenance plans bill monthly on the same date each month. Plans automatically renew each billing period unless cancelled with proper notice (see Section 6). The Client is responsible for ensuring payment is made on time each cycle.
Important: Monthly maintenance payments are payment for services rendered during that billing period. They are not credits toward project ownership, and they do not reduce, replace, or substitute for any buyout fee. See Section 7.
The Client may cancel a maintenance plan at any time by providing 30 days' written notice via email or WhatsApp. The plan will remain active through the end of the current billing period and will not renew after the cancellation date. No refunds are issued for the current billing period.
If a Client cancels a project after work has begun:
If a payment (project milestone or maintenance) is more than 14 days past due, RuutDev reserves the right to:
RuutDev will provide written notice before suspension. Services will be restored promptly upon receipt of all outstanding payments plus any applicable late fees.
In some arrangements — particularly for software, dashboards, or systems under a monthly maintenance or licensing model — full ownership of the project deliverables may be contingent on a separate buyout payment.
Monthly maintenance fees do not constitute payment toward project buyout. Prior monthly payments are not credited, deducted from, or applied toward any buyout amount, unless explicitly stated in writing in the original project agreement.
If a buyout option is available, it will be documented in the Client's written proposal or contract, including the buyout amount and conditions. Absent such written documentation, no buyout option exists by default.
Until a buyout is completed and confirmed in writing, RuutDev retains intellectual property rights as described in Section 10.
The typical project lifecycle consists of the following stages:
Any modifications to scope after the proposal is accepted may require a revised proposal and additional charges.
The number of included revision rounds is defined in the Client's proposal. As a general guideline:
A "revision round" consists of a consolidated set of feedback submitted in a single communication. Each round of revisions must be submitted before the next begins. Revisions that change the original scope may be billed as additional work.
Revisions requested after launch or after the included rounds are exhausted will be billed at RuutDev's hourly or project rate.
Upon receipt of all project payments in full, RuutDev transfers to the Client all rights to the custom-built deliverables specific to that project, including design files, code, and content created by RuutDev for the Client.
Until final payment is received, RuutDev retains full ownership of all work products, including the right to withhold delivery of source code, files, access credentials, and domain/hosting control.
RuutDev reserves the right to display completed work in its portfolio, case studies, and marketing materials, unless the Client requests confidentiality in writing.
Projects may incorporate third-party libraries, frameworks, fonts, icons, stock images, or APIs that are governed by their own licenses. RuutDev will disclose the major third-party components used, but the Client is responsible for reviewing and complying with those licenses independently.
The Client agrees to:
RuutDev may integrate or recommend third-party services including but not limited to: Stripe, PayPal, Vercel, Cloudflare, Google services, Zapier, Make, OpenAI, and others.
RuutDev is not responsible for the availability, performance, pricing changes, policy changes, or outages of third-party services. These services operate under their own independent terms and conditions.
If a third-party service becomes unavailable, changes pricing, or discontinues a feature, RuutDev will work with the Client to identify alternatives, but any additional development cost to replace or migrate to a new service is not included in the original project price.
Clients are encouraged to review and accept the terms of any third-party services used in their project.
To the maximum extent permitted by applicable law, RuutDev's total liability to the Client for any claim arising from or related to these Terms or any service provided shall not exceed the total amount paid by the Client to RuutDev in the 90 days preceding the claim.
RuutDev shall not be liable for:
RuutDev builds professional, high-quality digital products. However, RuutDev does not guarantee any specific business outcome, including but not limited to: increased traffic, leads, sales, revenue, search engine ranking, or return on investment.
Business results depend on many factors outside RuutDev's control, including market conditions, competition, the Client's products or services, pricing, marketing efforts, and other operational factors.
Any projections, estimates, or examples discussed during the sales process are illustrative only and not contractual commitments.
Filing a chargeback or payment dispute without first contacting RuutDev to attempt resolution is considered a breach of these Terms.
If a Client initiates a chargeback in bad faith — particularly after work has been delivered, approved, or launched — RuutDev reserves the right to:
Clients with legitimate payment disputes are encouraged to contact RuutDev directly first at helloruutdev@hotmail.com or via WhatsApp at +1 (407) 694-6371.
Support availability and response times depend on the Client's plan:
Emergency issues (site down, critical security breach) are addressed as quickly as possible regardless of plan level. RuutDev operates primarily Monday–Friday during standard US Eastern business hours.
These Terms and any disputes arising from them shall be governed by and construed in accordance with the laws of the State of Florida, United States of America, without regard to its conflict of law provisions.
Any legal action or proceeding shall be brought exclusively in the courts of Florida. Both parties consent to the personal jurisdiction of such courts.
RuutDev reserves the right to amend these Terms at any time. Changes will be communicated via the website and via direct notice to active Clients. Continued use of services after changes are posted constitutes acceptance.
For questions about these Terms, please contact:
RuutDev shall not be liable for any failure or delay in performing its obligations where such failure or delay results from causes beyond its reasonable control, including but not limited to: acts of God, natural disasters, pandemic or public health emergencies, government actions or restrictions, internet or infrastructure outages, failure of third-party services or platforms, or other events outside RuutDev's reasonable control ("Force Majeure Events").
In the event of a Force Majeure Event, RuutDev will notify the Client as soon as reasonably practicable. Project timelines affected by a Force Majeure Event will be extended by a reasonable period, and no penalties or fees shall apply for delays caused by such events.
If a Force Majeure Event continues for more than 30 consecutive days, either party may terminate the affected project agreement in writing. In such case, the Client shall be entitled to a prorated refund for any undelivered milestone, less any work already performed.
These Terms & Conditions, together with any written proposal or project agreement signed or accepted by the Client, constitute the entire agreement between RuutDev and the Client with respect to the subject matter herein, and supersede all prior and contemporaneous communications, representations, proposals, negotiations, or agreements — whether written or oral — relating to the same subject matter.
No amendment or modification of these Terms shall be binding unless made in writing and agreed to by both parties. If any provision of these Terms is found to be unenforceable, the remaining provisions shall continue in full force and effect.