terms-2026-10-29-r8
Work terms
The terms we work under: price, stages, timelines, revisions, rights and refunds.
Status of this document
Edition terms-2026-10-29-r8. The provider has enabled payment. Review the scope, price and work terms before paying. Independent legal review has not been confirmed.
Who can order
Customers may be organisations, entrepreneurs, freelancers or private individuals. Applicable rights also depend on whether the service is purchased for business or private use. These terms do not exclude mandatory consumer rights.
Scope and price
Adaptation of a ready 3D website base costs USD 2,000. Each catalogue add-on costs USD 150 within its listed scope. Custom development starts at USD 5,000 following a separately agreed specification and contract. Final price, applicable taxes, external costs, scope and dates are confirmed before payment.
Included base
One landing page in one language, the existing 3D scene of the selected base, supplied copy, logo and colour adaptation, responsive layout and one enquiry form to an agreed destination. New models, floor plans, integrations, accounts, online stores and editor features are quoted separately.
Short request first
Choose a base and add-ons, provide a contact and a short goal. The provider confirms suitability, specification, dates, total and active terms before payment. The detailed brief follows confirmed payment and cannot increase the agreed price automatically.
Advance and stages
The agreed total is paid 100% in advance, in one payment. Its allocation is 20% brief and specification, 35% design adaptation, 30% build and 3D, and 15% testing and handover. Payment does not itself mean the stages have been completed.
Start and delivery schedule
Ready-base adaptation takes up to 14 working days from the agreed start date, after confirmed payment and receipt of the necessary materials. Time awaiting customer materials or approval is excluded from development time; the provider notifies the customer of a pause and agrees an updated schedule. Custom websites from USD 5,000: an indicative 4–8 weeks; the exact schedule depends on scope and is confirmed after specification approval, before payment. Stage dates and the impact of selected add-ons are recorded in the specification before payment. Agreed scope changes may alter the schedule only by separate agreement.
Specification and approval process
Before payment, the parties record the selected base, pages and sections, existing 3D scene, language, included assets and functions, price, dates and revision process. The detailed post-payment brief clarifies that specification. Brief answers do not automatically add work or charges. Before the build, the provider submits a design or interactive preview for approval. Any conflict between documents is clarified in writing; neither party may unilaterally replace the agreed scope.
Included ready-base revisions
The USD 2,000 ready-base adaptation includes two design revision rounds for the whole page, including the selected add-on sections. This is not two separate rounds per section. Revisions stay within the specification: colours and typography, spacing, styling and element placement within the agreed structure, and supplied copy and images of comparable scope. New pages, sections, models, functions and replacing the selected base are outside these rounds. The rounds are intended to approve the design, not to redesign an already approved stage later. For custom projects, the number and scope of rounds are agreed separately in the specification before payment.
What counts as one round
One round consists of one agreed consolidated feedback list on a delivered version and one updated version addressing it. The customer appoints a contact to consolidate stakeholder feedback. Before revising, the provider confirms the list, clarifies contradictions and separates included requests from additional work. Several messages before the list is finalized do not themselves count as several rounds. An agreed item missed or implemented incorrectly by the provider is corrected within the same round without using another round. New requests after work on the list starts are agreed for a remaining round or separate work.
Version approval and stage review
When delivering a stage, the provider identifies the version, preview link or file and the work completed. By default, the customer has five working days to approve or submit consolidated feedback; another period can be recorded in the order before payment. Working days follow the calendar of the provider country and the time zone is agreed in the order. Approval requires an explicit message through the agreed email address or messenger identifying the version, for example: “I approve design version 2.” The provider retains the correspondence. Opening a link, paying or remaining silent does not approve every stage or waive defect remedies.
Delayed feedback
If feedback is overdue, the provider sends a reminder and may pause work dependent on approval or missing materials after notifying the customer. Further dates are agreed in light of the pause and work schedule. A pause does not automatically accept the deliverable, make the entire advance non-refundable or create an unapproved extra charge.
Pre-handover review
After the build, the customer checks the site against the approved design and specification. Before handover, one consolidated list of small supplied-copy, contact-detail and link replacements is included, without changing the structure, functions, element count or agreed scope. This is not another design-change round. Broken agreed functions and other implementation defects are corrected under the provider-defect rules regardless of this list. Publication on the customer domain requires separate approval to publish.
Provider defects and new preferences
A defect is a reproducible departure from the specification, approved version or agreed deliverable: for example, a broken form, incorrectly implemented model selection, a colour different from the approved one or a typo introduced by the provider. Correcting such defects has no separate charge and does not consume preference revision rounds. The customer identifies the page, reproduction steps and problem; the parties clarify test conditions if needed. The provider acknowledges the report and agrees a correction schedule appropriate to the problem. Design-round limits and stage acceptance do not remove mandatory customer rights concerning defects.
Scope changes and additional work
Changing an approved design, replacing the base, a new structure or page, an extra section, new 3D model, animation scenario, integration or function changes the scope. Additional preference revision rounds are also quoted separately. Before starting, the provider states the extra scope, price and schedule impact; the customer explicitly approves them in writing. Without that approval, extra work is not started and no additional fee is charged. USD 150 applies only to one standard section within its catalogue scope, not to every kind of rework. Unaffected agreed parts retain their existing terms.
After handover and applicable rights
Design approval concerns a specific version; a new creative brief after handover is not automatically included in the original price. Included technical support and additional work are governed by the Technical support and additional work section. Problems after third-party code changes, migration to an unagreed environment or an external-service change require identifying the cause; these circumstances do not automatically make every request chargeable or remove responsibility for an original defect. Revision terms do not limit mandatory warranties, remedies or other rights under applicable law.
Cancellation
On cancellation, completed work and delivered results are documented. Properly performed and delivered stages are charged to the extent permitted by applicable law; the unearned advance is returned. An unfinished stage is not automatically charged in full. Mandatory consumer rights and remedies for defects or non-performance remain. Any request to start during an applicable withdrawal period is separate, explicit and never preselected.
Payment methods
Payment opens once the scope and price are agreed and the customer has confirmed the work terms. Once enabled, ready bases and extra sections are paid for with PayPal on the site or with cryptocurrency: USDT on TON, USDT on TRON (TRC20), BTC on Bitcoin or ETH on Ethereum. A PayPal payment is made on PayPal: it counts as received when PayPal has confirmed it to the site’s server; returning to the site after paying does not count as payment. For custom development, PayPal and international transfer to a Georgian bank account require a separate agreement after the scope is agreed. Work is priced in USD; if the payer’s account is in another currency, the payment provider or the payer’s bank converts it; the exact crypto amount and treatment of fees are fixed in the invoice, without assuming an automatic 1 USDT to 1 USD rate. Crypto asset, network, address, rate, invoice expiry and confirmation rules must be agreed before transfer. Georgian international bank details are shared privately after scope and contract approval. A screenshot or success-page visit does not prove payment. Provider rules and mandatory rights remain applicable.
Technical support and additional work
Development includes 30 calendar days of technical support from handover of the agreed final site version and the files specified in the order. The date is recorded in correspondence or a handover document. The provider corrects reproducible departures from the specification or approved design at no extra charge, including defects in forms, agreed functions and display in agreed browsers. Corrections do not consume revision rounds. Changes to approved design, new content replacements by preference, pages, sections, models, integrations and functions are additional work; scope, price and dates are agreed in writing before starting. Problems following third-party changes, a different environment or external-service changes are investigated first; chargeable work needs prior agreement. The support period does not limit mandatory defect remedies.
Standard usage rights
Standard rights apply unless exclusivity is expressly agreed in the order. After full payment for the agreed deliverable, the customer receives a non-exclusive right to use the delivered site for their business or project, host it, make necessary backups and modify it independently or with maintenance specialists. The right applies worldwide for the duration of the relevant economic rights; its fee is included in the order price. Source files, build and instructions are specified in the order. Reselling or distributing the base as a standalone template requires a separate agreement. The provider retains rights in pre-existing bases, reusable components and tools whose reuse is expressly provided for in the order; customer assets and confidential information are not passed to other clients. Customer logos, trademarks, photos, copy and models do not become provider property and cannot be used in other customer projects without separate permission.
Exclusive design
Exclusive design is a separate, optional, paid option. Before payment the parties agree in writing which design elements are created only for the customer’s project and will not be reused by the provider, together with the price, permitted uses, territory and term, transfer date and source files. Selecting “Exclusive design” in the form requests a proposal; it does not transfer rights or authorise an extra charge, and until the provider has approved a price it is not included in any invoice. Exclusivity of the design, rights in the ready base and rights in third-party components are different things. Exclusive rights in other parties’ fonts, libraries, 3D models and previously created common components are not transferred. Exclusivity does not automatically cover published demonstrations, rights lawfully granted earlier or elements the provider does not exclusively own. Blender source files and exclusivity require separate agreement.
Third-party assets
Fonts, libraries, photos, 3D models and other third-party assets are used within their licences. Material restrictions, paid licences and required credits are disclosed before inclusion in the agreed deliverable. Site handover does not assign exclusive rights to these assets. The customer confirms rights to the assets they supply.
Portfolio publication
Portfolio display requires separate permission and is independent of exclusivity. Only with that permission, after the site launches publicly, the provider may show agreed interface images or video, project name and link in its own portfolio. Permission excludes private accounts, client contacts, financial figures, correspondence, documents and other non-public information. It does not imply customer endorsement or verified performance. Declining does not increase the price or reduce the service. The customer may ask projects@smart-key.online to stop using the case: the provider stops new publications and removes material from resources it controls within 10 working days. Removal of copies independently published by third parties is not guaranteed. Mandatory legal requirements remain applicable.
External costs
Hosting, domains, new assets, licences, ad spend and fees are agreed separately. No lead counts or marketing outcomes are guaranteed.
Provider
Provider: Individual Entrepreneur Rinat Miftakhov, identification number 304836943. Provider details and contacts appear on this page and in the site footer. To discuss the terms: Rinat, WhatsApp +995 595 045 327, Telegram @JustTomy, projects@smart-key.online.