Scope
Every project starts from an approved scope, package, proposal, invoice, or written confirmation. The scope defines the pages, features, deliverables, timeline, revision allowance, and support window included in the work.
Client input
The client is responsible for providing accurate business details, brand assets, product information, content, account access, approvals, and feedback on time. Delays in required information or approvals can move the timeline.
Assets
The client confirms they have the right to use any logos, images, text, fonts, videos, product data, and outside materials supplied for the project. Approval of a design, page, or deliverable means it is accepted for the next stage unless a written issue is raised within the agreed review period.
Payments
Work begins after the required payment, deposit, or written payment arrangement is completed. Late or incomplete payments can pause delivery, support, handover, publishing, or access to final files until the account is current.
Revisions
Revision rounds cover reasonable changes within the approved scope. New pages, new features, major direction changes, outside integrations, copy rewrites, or requests made after approval may require a new estimate and can change the delivery date.
Outside tools
Domains, hosting, Shopify, payment gateways, analytics tools, email providers, databases, plugins, APIs, stock assets, licenses, and other outside services remain subject to their own terms, pricing, limits, outages, and account rules.
Provider costs
Unless agreed otherwise in writing, the client pays for domain registration, hosting, platform subscriptions, usage fees, bandwidth, storage, premium apps, payment gateway charges, and provider renewals. Rizenyte Web can help configure these services when included in the scope.
Ownership
After full payment, the client owns the final custom deliverables created specifically for their project. Third-party platforms, open-source packages, licensed assets, reusable internal methods, templates, tools, and provider-owned systems are not transferred unless clearly stated.
Support
The included support window covers launch related fixes tied to the approved scope. It does not include new features, new content, strategy changes, ongoing maintenance, platform problems, or issues caused by outside changes unless those services are part of an active maintenance agreement.
Updates
Updates requested after delivery can be handled through a maintenance scope, new quote, or separate agreement. Rizenyte Web may review the existing build, access level, and technical condition before accepting maintenance work on any site.
Cancellations
Payments cover reserved time, planning, design, development, communication, and completed work. Refunds are not guaranteed once work has started, but unresolved situations can be reviewed fairly based on the stage of delivery and the written agreement.
Liability
Rizenyte Web is not responsible for indirect losses, lost revenue, lost data, outside outages, provider failures, payment gateway issues, security incidents caused by shared or weak credentials, client side account problems, or changes made outside the agreed work.
Access
The client should protect account credentials, enable recommended security settings, and remove access that is no longer needed. Rizenyte Web may refuse unsafe requests, suspicious access changes, or work that could compromise a site, user data, or provider terms.
Privacy
Inquiry details, project notes, agreement records, invoices, and support messages are used only to respond, scope, deliver, document, and support the requested work. Rizenyte Web does not sell client contact data. Some trusted service providers may process data when needed for hosting, email, analytics, payment, security, or delivery.
Results
Rizenyte Web builds with clarity, performance, and conversion in mind, but no website can guarantee revenue, rankings, leads, approvals, platform acceptance, or sales. Results depend on the offer, market, traffic, content, pricing, follow-up, and outside factors.
Updates to these terms
These terms may be updated as services, platforms, or operating processes change. For a specific project, a signed agreement, proposal, invoice, or statement of work can add to or override these general terms.