Terms of Service

01 Who these terms are with

These terms of service (the Terms) govern the provision of software development services by IT Julian Soft SIA, a limited liability company (sabiedrība ar ierobežotu atbildību) entered in the Commercial Register of the Republic of Latvia on 31 July 2026 under registration number 40203766520, with its legal address at Dārzu iela 25, Rēzekne, LV-4601, Latvia, represented by its board member (valdes loceklis) Juliāns Molodcovs.

In these Terms, we, us and our mean IT Julian Soft SIA. You, your and the Client mean the natural or legal person who accepts a quote from us or otherwise instructs us to begin work. A Project means a single engagement described in one accepted quote. A Deliverable means the software, source code, configuration and deployment produced under that quote.

02 Acceptance

You accept these Terms when you do any of the following:

• accept a written quote we have issued, by email or in any other durable form;
• pay an invoice we have issued for a Project;
• instruct us to begin work on a Project.

These Terms apply alongside your individual project quote. The quote is the specific document: it states the scope, the execution, the result, the deliverable, the price and the timing. If the quote and these Terms conflict on scope or price, the quote prevails. On every other matter these Terms apply.

Your own purchase conditions, supplier terms or portal terms do not apply to a Project unless we have accepted them in writing.

03 The services

We deliver three defined services. Each is quoted as a fixed-scope, fixed-price engagement, and each has a published starting price. The starting price is the entry point for a straightforward brief; the figure in your quote is the figure that applies.

Each service is defined by the same four lines. These are the lines that appear on the quote and on the invoice, and they are the reference point for what is owed and what is delivered.

S/01 · E-Commerce Platform Deployment — from EUR 1 000

S/02 · Landing Page Development — from EUR 700

S/03 · SaaS Platform Custom Module & Setup — from EUR 1 500

A brief that does not fit one of the three tracks is quoted in the same fixed-price format, using the same four lines.

04 Scope, quotes and changes

Every Project is fixed-scope and fixed-price. What the quote describes is what we build; what it does not describe is not included. We would rather write a longer scope than leave an assumption in it.

Anything you ask for that falls outside the written scope is a change request. We will quote it separately as a fixed figure, and work on it starts only once you have accepted that quote in writing. Small clarifications that do not add development effort are absorbed as part of the Project.

• Quotes are valid for 30 days from their date of issue. After that we may re-quote.
• Timelines given in a quote are indicative and assume the input described in section 06 arrives when requested.
• Feedback rounds against the agreed scope are included in the price. Redesigns that replace an already approved direction are a change request.

05 Fees, invoicing and payment

Invoices are issued by IT Julian Soft SIA and settled by bank transfer to the account below. The payment reference must be the invoice number, exactly as printed on the invoice — that is how we match your payment to your Project.

• You bear your own bank charges, including any intermediary or correspondent bank fees. The amount credited to our account must equal the invoiced amount.
• Development is scheduled once the payment has cleared. If payment is not made within the 5-day window, we may hold the schedule slot and re-plan the Project against our current availability.
• Each Project is invoiced as one figure and settled by one transfer. We do not split a Project fee across installments; where a brief is large enough to need separate phases, each phase is scoped, quoted and invoiced as its own Project on these same terms.
• Prices are net figures for our own services. Third-party costs are covered in section 07.

06 Client responsibilities

A fixed price only works if the material we need arrives when we need it. You agree to provide, at the point in the schedule where it is requested:

• Content — text, images, product data, logos and brand assets, in a usable format, with the rights cleared for the use you intend.
• Access — credentials for hosting, cloud accounts, the domain registrar, DNS, any existing repository and any system we are asked to integrate with.
• Third-party accounts — set up in your own name, including the payment provider (for example Stripe or PayPal), analytics, transactional email and shipping providers, together with any verification those providers require.
• A single named point of contact — one person with authority to approve scope, review builds and sign off delivery.
• Timely feedback — responses to review requests within the window stated in the quote, or within 5 working days where no window is stated.

Where material, access or feedback is late, the schedule extends by at least the length of the delay, and we may need to re-plan the Project around other committed work. Delay caused by the Client does not change the price.

07 Third-party services and costs

Hosting, cloud infrastructure, domain registration and renewal, payment-provider fees and transaction commissions, software licenses, API charges, email-sending services and similar running costs are your own costs. They are not included in our fee, they are billed to you directly by those providers, and the accounts stay in your name so you keep the billing relationship and the root credentials.

Those services are governed by their own terms and privacy policies, which you accept directly with the provider. We configure and integrate them; we do not resell them and we do not control them. We are not responsible for a provider's outage, price change, policy change, account suspension or discontinuation of a feature we have integrated.

Open-source components used in a Deliverable remain subject to their own licenses. We use conventional, permissively licensed components and will tell you which ones are in the build if you ask.

08 Delivery, review and acceptance

During the build you get a staging link you can open at any time, so review is continuous rather than a single reveal at the end. When the Project is complete we deploy it and notify you in writing that it has been delivered.

From that notification you have a review window of 10 working days. Within that window, report any defect in writing, describing what you did, what you expected and what happened instead. We correct confirmed defects in the delivered scope at no charge.

The Deliverable is treated as accepted when the earliest of the following occurs:

1. you confirm acceptance in writing;
2. the 10 working days pass with no defect reported;
3. you put the Deliverable into commercial use — for example by taking live orders, live leads or live customer sign-ups through it.

Acceptance does not affect the defect-correction period described in section 10.

09 Intellectual property

Until the invoice for a Project is paid in full, all rights in the work remain with us and no license to use it is granted. After payment, the repository, the deployment and the right to keep developing the work are yours.

We retain ownership of our pre-existing tools, libraries, snippets, templates, methods and know-how — anything we bring to the Project rather than create for it. Where such material is embedded in a Deliverable, we grant you a perpetual, worldwide, non-exclusive, royalty-free license to use, host, modify and maintain it as part of that Deliverable. That license does not let you extract our pre-existing material and license or resell it as a standalone product.

Third-party and open-source components remain the property of their authors and are used under their own licenses, which pass to you unchanged.

You warrant that you hold the rights to any content, data, trademarks or material you supply to us, and that our agreed use of it does not infringe anyone else's rights.

10 Warranty and defect correction

For 30 days from delivery we correct, free of charge, defects in the delivered scope. A defect means the Deliverable does not materially perform as described in the accepted quote, on the environment and configuration it was delivered to.

The defect-correction period does not cover:

• changes made to the code, configuration, hosting or third-party accounts by you or anyone else after handover;
• faults caused by a third-party service — an outage, an API or pricing change, a plugin update or a discontinued feature;
• content edits, new pages, new integrations or any other new feature request;
• faults caused by material or credentials you supplied that turned out to be incorrect;
• infrastructure you administer yourself after handover, including backups, certificate renewals and platform updates.

Work outside the defect-correction period, or outside its cover, is quoted separately as a small fixed-price job. No software can be warranted to be free of every possible error; what we warrant is the delivered scope, and we fix it when it does not do what the quote says it does.

11 Limitation of liability

We are not liable for indirect or consequential loss, lost profits, lost revenue, lost savings, loss of business or goodwill, or lost or corrupted data, however caused.

Our total aggregate liability arising out of or in connection with a Project is limited to the fees actually paid to us for that Project.

Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited, including liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for intentional harm or gross negligence, or any mandatory statutory right of a consumer.

After handover you are responsible for operating the Deliverable, including keeping your own backups and applying platform and dependency updates, unless we have separately agreed to do so.

12 Confidentiality

Each party keeps the other's confidential information confidential, uses it only for the Project, and does not disclose it to anyone who does not need it for the Project. This covers business plans, commercial figures, credentials, customer data, source code and anything marked or reasonably understood as confidential.

This obligation does not apply to information that:

• is or becomes public through no breach of these Terms;
• was already lawfully known to the receiving party without a duty of confidence;
• is independently developed without use of the other party's information;
• must be disclosed by law or by a competent authority — in which case the disclosing party notifies the other where it is lawful to do so.

Confidentiality survives the end of the engagement and continues for as long as the information remains confidential.

13 Data protection

How we handle personal data as a controller — enquiries, correspondence and website visitors — is described in our Privacy Policy, and the website's own cookie use is described in the Cookies Policy.

Where a Project involves us processing personal data on your behalf — a lead database, a store's customer records, a SaaS platform's user accounts, or access to a live system during migration or support — you are the controller and we act as processor. In that case we conclude a written data processing agreement with you before the processing begins. It is available on request and sets out the subject matter, duration, nature and purpose of the processing, the categories of data and data subjects, our security measures, the position on sub-processors, and what happens to the data at the end of the engagement.

Both parties comply with Regulation (EU) 2016/679 (GDPR) and applicable Latvian data protection law. Test and staging environments are populated with anonymized or sample data wherever a Project allows it.

14 Portfolio rights

We may name the engagement and show non-confidential screenshots of the public-facing result in our portfolio, on this website and in proposals, describing the service delivered and the general nature of the work.

We never publish credentials, source code, internal screens, customer data, commercial figures or anything covered by section 12. If you would prefer us not to reference the engagement at all, tell us in writing at any time — before, during or after the Project — and we will remove it. No reason is needed.

15 Term, suspension and termination

An engagement runs from acceptance (section 02) until the Deliverable is accepted (section 08). Either party may end it earlier as follows.

• For material breach. Either party may terminate in writing if the other commits a material breach and does not remedy it within 14 days of written notice.
• Suspension by us. We may suspend work if an invoice is unpaid, if access we need has been withdrawn, or if the Project is being used for unlawful purposes. We give notice before suspending and resume once the cause is resolved.
• Cancellation by you. You may cancel a Project in writing at any time.

On termination, whatever the cause:

1. fees for work already completed up to the termination date are payable, calculated in proportion to the scope delivered;
2. anything already paid that exceeds that amount is refunded to you within 14 days;
3. we hand over the material completed and paid for, in a usable form, together with any credentials of yours we hold;
4. ownership under section 09 transfers only for work that has been paid for in full;
5. sections 09, 11, 12, 13 and 17 survive termination.

16 Force majeure

Neither party is liable for a delay or failure to perform caused by an event beyond its reasonable control — including natural events, fire, flood, epidemic, war, civil unrest, terrorism, acts of state authorities, strikes, failure of power, telecommunications, hosting or cloud infrastructure, and large-scale cyber-attacks.

The affected party notifies the other without undue delay and does what it reasonably can to limit the effect. Obligations are suspended for as long as the event lasts. If it continues for more than 60 days, either party may terminate the engagement in writing; fees for work already completed remain payable under section 15.

17 Governing law and disputes

These Terms and every Project are governed by the laws of the Republic of Latvia. The language of the contract and of correspondence is English or Latvian, as agreed.

If something goes wrong, write to us first. We commit to attempting a good-faith resolution through direct negotiation, and to responding substantively within 30 days of receiving a written complaint. Most disagreements are a scope misunderstanding and are resolved at this stage.

If negotiation does not resolve the matter, the dispute is settled by the courts of the Republic of Latvia.

Where the Client is a consumer, nothing above deprives them of the mandatory statutory rights of their country of residence, including the right to bring proceedings there. A consumer may also refer the matter to the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs) in Latvia, or use the European Union's Online Dispute Resolution platform where that platform is available to them.

18 Changes to these terms

We may update these Terms as the business changes. The version that applies to your Project is the version published on this page at the moment your quote was accepted, and it stays in force for that Project even if this page is updated later. On request we will send you a copy of the version that applied.

The version number and the date of the current text are shown at the top of this page. For anything not tied to a Project — for example use of this website — the current version applies.

19 Contact

Questions about these Terms, a quote, an invoice or an engagement go to the same place. Written notices under these Terms are valid when sent by email to the address below and may also be sent by post to our legal address.

• Email: hello@juliansoft.lv
• Phone: +371 20 000 000
• Legal address: IT Julian Soft SIA, Dārzu iela 25, Rēzekne, LV-4601, Latvia
• Registration No: 40203766520 (Commercial Register of Latvia, 31.07.2026)
• Board member: Juliāns Molodcovs

Notices and enquiries should be sent by email. The form on the contact page is not connected to a backend yet and transmits nothing, so it cannot be used to give notice under these Terms.