DDS / AGREEMENT BETWEEN THE PARTIES

First, a clear agreement.

Before payment, you will receive a service agreement and a schedule defining your final project scope. Both parties must accept the same version.

Informational draft: describes the topics the agreement will cover. It is not ready to sign and does not record acceptance. Project terms must be completed and legally reviewed before use.

Version: 2026-10-14-delivery-draft

1. Parties and project agreement

The agreement will identify the provider and client, contact details and, where applicable, tax identification and an authorized representative. DDS is the service’s trading name; the provider will be the individual identified in the legal notice, not an assumed separate company.

2. Scope and deliverables

A project schedule will specify the selected tier, base components, four agreed patterns, additional patterns, states, responsive behavior, files, repository, technology, documentation and exclusions. “Other pattern” requests will be assessed before pricing. No configurator estimate replaces that schedule.

3. Price and payment

The document will specify the total amount, taxes, currency, payment method and any currency conversion rule. Full payment is planned at contracting, after both parties have accepted the same agreement and schedule version. PayPal and Mercado Pago are planned integrations; payments are not currently processed.

4. Schedule and collaboration

Availability, start date, milestones and delivery date will be agreed in writing. Starting work requires an accepted contract, confirmed payment and the agreed materials and access. Website timeframes are indicative. Scope changes or delays will be communicated and revised dates confirmed in writing.

5. Communication, revisions and delivery acceptance

Work will be primarily asynchronous, with written updates and clarifications and occasional calls when agreed. One consolidated round of adjustments within scope is included. The schedule will define verifiable acceptance criteria and a review period. Defects against the agreed scope will be corrected without treating them as new features; changes in direction or scope need approval and a quote.

6. Files, intellectual property and confidentiality

The agreement will distinguish client-specific work from existing tools, libraries and third-party resources. It will define which rights are assigned or licensed, when, under which conditions and which files are delivered. Each party must hold the necessary rights to supplied materials. Confidential information will be used to perform the project; publishing a case study requires separate permission.

7. Cancellation, non-performance and support

Before contracting, the grounds and procedure for cancellation, work already performed, applicable refunds, response times and post-delivery support will be defined. Full payment does not automatically waive refunds or legal rights. Mandatory consumer rights are not excluded where applicable.

8. Acceptance and copies for both parties

The contracting process must allow both parties to read and retain the complete version and schedule, identify who accepts and record their acceptance, version and date. The client will receive a copy. Accepting the privacy notice does not replace accepting the agreement. This site does not yet implement contract signing or acceptance records.

9. Scope changes and dependencies

The quote covers only the approved schedule. New requests require written confirmation of price and timing before execution. The client warrants that materials may be shared and appoints one contact to consolidate feedback. DDS will report missing inputs or blockers; any suspension and rescheduling will be documented without adding unapproved charges.

10. Use of work and third-party resources

As a proposed baseline, the client may use and modify project-specific deliverables once the full price is paid. The schedule will specify the applicable assignment or license. Third-party rights and ownership of DDS pre-existing tools or libraries are not transferred; necessary licenses will be identified. No reservation allows reuse of the client’s confidential information or exclusive assets.

11. Early termination and refunds

Either party may request termination in writing. For a remediable breach, the issue will be reported and a reasonable correction period agreed. Unless mandatory law requires otherwise, closure will account for work actually performed and evidenced, previously authorized non-recoverable costs and the balance to refund. Full forfeiture of payments and automatic penalties are not presumed. Applicable consumer rights and remedies remain available.

12. Responsibility and service boundaries

DDS is responsible for delivering the agreed scope. Commercial results, the absolute absence of defects and operation of third-party services outside its control are not guaranteed. Changes made by the client or third parties after delivery require assessment before attributing a defect to DDS’s work. These boundaries do not exclude responsibilities that cannot legally be limited.

13. Confidentiality, access and closure

Confidentiality continues after the service ends. Access is limited to those who need it and are bound by equivalent obligations. Confidential materials will not be shared with external AI tools or collaborators without specific permission. The schedule will define delivery location, download availability and working-copy deletion, including backups where applicable; legal retention duties or justified claims permit retaining only the minimum necessary information with restricted access.

View legal notice and contact →

Your delivery, from start to finish

A downloadable package for your plan

Delivery will use a private link to the agreed package: audit slides and documents; Design with editable Figma files and components; Design + repo with the complete repository; Build with the application foundation; Govern AI with the repository, guidelines, rules and .mdc files prepared for working with AI design and development agents in the agreed tools. The project schedule lists the specific formats, versions and contents.

What we need to get started

At contracting, we complete a brief covering goals, product, brand, users, technology, approval contacts and Figma links, websites or references. Access is limited to necessary materials with minimum permissions; do not submit passwords in the form. The client must be authorized to share the materials. We check that the scope can be delivered with those inputs before starting.

4 to 8 business days, depending on scope

Standard plans have an indicative execution window of 4 to 8 business days; the most comprehensive plan is estimated at approximately 8. The delivery agreement sets the start date and timeline for each project. The clock does not start when the form is sent: it requires an accepted contract, confirmed payment, a complete brief and access. Custom patterns, expanded scope or delayed approvals may require revised dates.

Working sessions when useful

Work combines written communication with meetings when needed for the plan. Their number, duration, participants and review points are agreed in the project schedule before payment. No sales call is required, and unlimited meetings are not included.

Private link, review and closure

The agreement specifies where deliverables will be hosted, who can access them and the download availability period. We prefer a client-controlled workspace. If DDS temporary storage is used, expiry and deletion dates are agreed. The client confirms access and keeps a copy; closure includes the agreed review and adjustments. Indefinite hosting or custody is not included.

Confidentiality and deletion of working copies

Project materials and information are used only to provide the service. They are not published or reused in portfolios, other clients’ work or external AI tools without specific permission. After delivery and agreed adjustments are closed, working copies controlled by DDS will be deleted and access revoked. The agreement will set the date and handling of third-party backups. Only the minimum records required for legal obligations or claims will be retained with restricted access. This planned policy requires a closure procedure; the site does not yet automate deliveries or file deletion.