Terms of Service and rules of cooperation
This is a translation provided for convenience. The Russian version of the document is the main one: if the texts diverge, it prevails.
About this document
Version 1.0. Updated 24 May 2026.
This document sets out the basic terms of dealing between Brick Agency (the "agency") and the client: how work starts, payment, refunds, revisions, delivery of results, warranty support and the responsibilities of each side.
The agency is an independent project team providing services in design, development, project management and adjacent digital fields. In particular cases cooperation may be formalised through an individual agreement, contract, bill, invoice or another written form agreed by the parties.
Individual terms take precedence
If for a particular project the parties have separately agreed other terms in writing, those individual terms take precedence over the general rules set out in this document.
1. General
1.1. The agency provides services both separately and as full project support. The exact set of services, deadlines, cost, stages and result are agreed individually before work on the project begins.
1.2. The work of the agency rests on written arrangements: a brief, correspondence, a proposal, a specification, a project plan, an invoice, an agreement or another agreed form. Verbal arrangements are best put in writing so that no reading of them is left open to dispute.
1.3. Before work begins the parties settle: the client’s task, the expected result, the scope of work, the deadlines, the cost, the order of payment, the form of communication, the approval stages and the list of materials the client is to provide.
1.4. The agency may decline cooperation or a particular task if the project runs against the team’s principles, creates excessive legal, technical, reputational or payment risk, or calls for resources that were not agreed in advance.
2. Services of the agency
2.1. The agency may provide services in several directions. The exact list of work is always defined individually, since different projects call for different amounts of design, development, management, communication and preparation of materials.
2.2. Design
- UI/UX design of websites, applications, Telegram Mini Apps, user accounts, CRM systems, admin panels and other digital interfaces.
- Design of landing pages, multi-page websites, presentations, promotional materials, banners, visual concepts and individual interface elements.
- Preparation of page and screen structure, user scenarios and visual solutions within the agreed scope of work.
- Delivery of the final design layouts in Figma, unless another form of delivery is agreed separately.
Design work does not include endless changes of concept, preparation of an unlimited number of options, development of a brand book, copywriting, illustration, 3D, video, animation or deep UX research, unless such tasks were agreed separately.
2.3. Development
- Development of websites, landing pages, web applications, Telegram Mini Apps, interfaces, admin panels and adjacent digital products.
- Frontend and backend development within the agreed specification, structure, layouts or project plan.
- Integration of APIs, payment systems, CRM systems, analytics, databases, admin panels, Telegram tools and third party services.
- Delivery of the project source code after payment in full, unless agreed otherwise.
Development is carried out within the agreed scope. New features, extra integrations, a change to the logic of the product, moving it to another platform, extending the architecture or reworking approved solutions all count as additional work.
2.4. Project management
- Preparation of the project structure, basic specifications and project plans, and control over the completion of stages.
- Defining the roles needed, forming the project team and distributing areas of responsibility for the particular tasks of the project.
- Creating and setting up the working structure of the project for later launch, running or scaling.
- Establishing the processes between the participants, including the client’s staff, contractors and representatives of the agency.
- Drawing up working plans, delivery strategies, road maps and stages of the project’s growth.
- Setting tasks, prioritising work and keeping track of deadlines, interim results and agreed stages.
- Watching for risks, delays, blockers and points of dispute during the work.
- Support of the project until the agreed scope of work is complete.
Project management is aimed at organising the completion of the agreed tasks. It does not include full operational management of the client’s business, financial management, legal support or strategic decisions taken on the client’s behalf, unless that is agreed separately.
3. Starting work
3.1. Work begins once the task, the cost, the deadlines, the form of the result and the order of payment have been agreed and the necessary materials received from the client.
3.2. The necessary materials may include: texts, images, logos, access credentials, documents, references, data, technical requirements, brand materials, access to hosting, a domain, a repository, Telegram bots, advertising accounts, CRM systems or other services.
3.3. If the client has not provided the necessary materials, access, approvals or answers, the deadlines may be moved. The agency is not responsible for delays caused by the absence of information or action on the client’s side.
3.4. If before work begins the client refines the task without changing its scope, complexity, deadlines and the resources needed, such refinements may be accepted without revisiting the cost. If the changes affect the scope, the complexity, the deadlines or the make-up of the team, the agency may recalculate the cost and the deadlines.
4. Payment
4.1. Payment in advance
Work is carried out on 100% prepayment, unless another arrangement is agreed separately. Until payment is received the agency is not obliged to begin work, reserve the team, hand over results or start carrying out tasks.
4.2. Individual payment arrangements
For large, long-term or complex projects, payment by stages, payment against milestones, partial prepayment, a separate agreement or another individual arrangement is possible. Such an arrangement is to be agreed by the parties before work begins.
4.3. Additional work
Any work beyond the scope agreed at the outset is carried out only after its cost and deadlines have been agreed separately. Such work includes new pages, screens, features, integrations, concepts, scenarios, materials, the reworking of approved stages or any task that was not part of the original arrangement.
4.4. What payment records
Payment confirms the client’s agreement with the agreed terms of the task, the cost, the deadlines, the scope of work and these rules of cooperation, unless stated otherwise in a separate agreement or written arrangement.
5. Refunds
5.1. Refund for work not carried out
A refund is possible only for the part of the work that had in fact not been carried out at the moment the refund was requested. Work already done, consultations already given, materials prepared, analysis carried out and working time spent may be withheld from the refund.
5.2. Full refund before work begins
If the client withdraws from the project before work begins, and the agency has not yet carried out consultations, analysis, preparation of solutions, estimation, planning or other intellectual work, a full refund is possible.
5.3. Withholding for work carried out
If before the withdrawal there had already been consultations, analysis of the project, preparation of a structure, a specification, a proposal, a design concept, a project plan or other preliminary work, the agency may withhold the cost of the services actually provided.
5.4. Calculating the refund
The amount withheld is determined from the volume of work already done, the time spent and the terms agreed beforehand. If the work was divided into stages, the calculation may follow the stages actually completed or the resources actually spent.
5.5. Terms and currency of a refund
The agreed refund is transferred to the client within 7 working days from the moment the amount is confirmed by both parties. The currency and the means of refund are agreed individually, taking into account the currency of the original payment, the payment channels available and possible fees. Fees for transfer, conversion and payment system service may be withheld from the refund unless the parties have agreed otherwise.
6. Communication and approvals
6.1. The client is to appoint one responsible representative who takes decisions, hands over materials, approves stages and gives feedback on the client’s behalf.
6.2. If several people take part on the client’s side, the client is responsible for reconciling their opinions among themselves. Contradictory comments, different decisions from different representatives or internal disputes on the client’s side may lengthen the project.
6.3. The main channel of working communication is Telegram, unless the parties have agreed another one. All key decisions, revisions, changes of scope, approvals and sign-offs are best recorded in writing: in Telegram correspondence, a document, a task tracker, Figma, a spreadsheet or another agreed channel. Messages and confirmations in the agreed channels count as a sufficient form of written agreement for the purposes of this document.
6.4. The agency is not responsible for delays caused by lengthy approval inside the client’s team, the absence of a single decision, late feedback or a change in the client’s position after a stage has been approved.
7. Freezing a project
7.1. If after payment the client does not get in touch, does not provide materials, access, approvals, comments or feedback for more than 7 calendar days, the agency may freeze the project.
7.2. Freezing a project is not its cancellation and does not oblige the agency to refund money automatically. The amount paid stays with the client within this project, less the part of the work already done, unless the parties have agreed otherwise.
7.3. The project can resume once communication is restored and current deadlines are agreed again. If the pause has changed the scope, the cost, the availability of the team, the technical conditions or the relevance of solutions agreed earlier, the agency may recalculate the terms on which the work continues.
8. Revisions
8.1. Number of revisions
The standard cost includes one round of revisions for each agreed stage of work, unless agreed otherwise. A stage may be a design concept, an individual page, the frontend, the backend, an integration, the final build, a presentation, a promotional material or another result that the parties have singled out as a stage.
8.2. What one round of revisions is
One round of revisions is one combined list of the client’s remarks, comments and wishes for a particular stage. The client is to gather all comments on the stage and pass them over in one message, document, list, spreadsheet, set of Figma comments or another agreed way.
8.3. Time to send revisions
After a stage is demonstrated, the client has 5 calendar days to send revisions. What happens to a stage when no revisions arrive is described in section 9.
8.4. What counts as revisions
Corrections that do not change the scope, structure, concept, specification, business logic, style and direction of the project agreed earlier:
- changing text within an approved block;
- replacing an image without changing the structure;
- adjusting colour, spacing, the position of elements or visual details;
- replacing an icon, refining wording or a small adaptation of a block;
- fixing a mistake by the agency where it contradicts the agreed specification.
8.5. What does not count as revisions
Changes that in effect create a new volume of work or call for reworking a solution approved earlier are not revisions and are paid for separately:
- changing the design concept, the structure of the site, a page, an application or a user scenario;
- adding a new page, screen, feature, user role, account area, CRM section, admin panel or integration;
- changing the business logic, the specification, the target audience, the positioning or the references after work has begun;
- asking for the work to be done in a different style after the current direction has been agreed;
- reworking an approved stage or going back to a stage the client has already accepted.
9. Approval of stages
9.1. Each stage of work is demonstrated to the client separately. After the demonstration the client may approve the stage, send one round of revisions or ask for further discussion within the agreed term.
9.2. Once approved, a stage counts as accepted. If the client has given no feedback within 5 calendar days, the stage may also count as accepted, unless the parties have agreed to extend the term.
9.3. Going back to a stage approved earlier, reworking it or changing it at the client’s initiative counts as additional work and is paid for separately, unless agreed otherwise beforehand.
10. Additional work
10.1. Additional work means tasks that were not part of the scope agreed at the outset. Such work is not carried out automatically and calls for its cost and deadlines to be agreed separately.
10.2. Additional work may include: new pages, screens, features, integrations, reworking the structure, changing the concept, extra design options, moving to another platform, changing the logic, adding new materials, extending the team or support beyond the agreed term.
10.3. If during the work the client changes the task, the references, the requirements, the target audience, the business logic or the expected result, the agency may recalculate the cost and the deadlines of the project.
11. Client materials and the lawfulness of content
11.1. Materials for the project may be provided both by the client and by the agency, depending on the agreed form of work. If creating content is not part of the agreed scope, the agency is not obliged to prepare texts, images, translations, video, legal documents or other materials itself.
11.2. The client warrants that all materials, data, texts, images, video, trademarks, logos, documents, access credentials and other information they provide are used lawfully and do not infringe the rights of third parties.
11.3. The agency is not responsible for the legal consequences of using materials provided by the client, where the agency did not know and could not have known of an infringement.
11.4. If the project belongs to a field with heightened legal, payment, platform or reputational risk, the agency may agree separate terms of work, limit its liability, request additional information or decline the task.
12. Responsibility of the agency
12.1. The agency undertakes to carry out the agreed scope of work within the approved specification, brief, proposal, project plan or other written arrangement.
12.2. The agency does not guarantee the commercial outcome of a project, including sales, profit, the number of enquiries, return on investment, conversion, growth of an audience, passing moderation, investment results or other business figures, unless such guarantees have been separately recorded in writing.
12.3. Forecasts, hypotheses, calculations, recommendations and expected figures are not a guarantee of a result, unless a separate agreement states otherwise in so many words.
12.4. The agency is not responsible for failures, blocks, restrictions, changes of rules, moderation, fees, technical problems or decisions of third party platforms, payment systems, hosting providers, domains, APIs, advertising accounts, Telegram, Google, Meta, Apple, banks, crypto services and other external services.
13. Force majeure
13.1. Neither party is responsible for delays or failure to perform caused by circumstances they could not foresee and could not influence. Such circumstances include: military action, emergencies, mass outages of communications or electricity, serious failures or blocks of key services and platforms, illness of key contributors, acts of state authorities and other similar events.
13.2. The party that meets such circumstances informs the other within a reasonable time and discusses how the work proceeds: moving deadlines, redistributing tasks, a temporary pause or another agreed option.
13.3. If such circumstances make further work on the project impossible or pointless, the parties agree in good faith on the terms of ending the cooperation, including settlement for the work actually done.
14. Delivery of results
14.1. The results of the work are handed over to the client after the project has been paid in full, unless agreed otherwise. Until payment in full the agency may withhold the final files, the source code, access credentials, working materials and other results of the work.
14.2. On design projects the client as a rule receives access to the final layout in Figma. Handing over the Figma file means handing over the final design result, but does not always mean handing over all of the agency’s internal materials.
14.3. On development projects the client receives the project source code after payment in full, unless agreed otherwise. The final build, access to the repository, basic documentation and instructions for running the project may also be handed over, where they are part of the scope of work.
14.4. Internal design systems, commercial templates, component libraries, universal blanks, drafts, interim versions, internal methods and materials not directly related to the paid project are not handed over to the client unless stated separately.
15. Warranty support
15.1. For 30 calendar days after the project is delivered the agency provides free warranty support, which covers fixing errors that arose through the fault of the agency within the agreed scope of work.
15.2. Warranty fixes cover errors in the agreed functionality, elements that do not work correctly, technical mistakes in implementation or divergence from the approved result, where these arose through the fault of the agency.
15.3. Warranty support does not cover new tasks, changed requirements, extended functionality, changes of design, added pages, added materials, moving to another server, work with third party services beyond the agreed scope, and also problems that arose from the actions of the client, third parties, hosting, a domain, an API, payment systems, platforms or external services.
15.4. Once the warranty period ends, further support is provided on a paid basis.
16. Portfolio and confidentiality
16.1. The agency may use a completed project, parts of it, visual materials, a description of the tasks and the results of the work in its portfolio, presentations, social networks and commercial materials only after agreeing this with the client, unless provided for beforehand.
16.2. If the client needs confidentiality, an NDA, a ban on publishing the project, a restriction on showing materials or work without the client being named, such terms are to be agreed separately before work begins.
16.3. The agency undertakes not to disclose closed information of the client, where such information has been expressly passed as confidential or the parties have separately agreed a regime of confidentiality.
17. Completion of work
17.1. A project counts as complete once the agreed result has been handed over, the paid scope of work carried out, the final stage approved or no substantiated revisions received within the term set.
17.2. After a project is complete, any new tasks, changes, refinements, support, consultations or maintenance are provided on a paid basis, unless they fall within the warranty period or were agreed separately.
17.3. If the client uses the materials handed over, launches the project, publishes the result, passes it to third parties or continues work on the basis of the agency’s result, this may count as confirmation that the work has been accepted.
18. Final provisions
18.1. These rules may be updated by the agency. The current version of the terms is published on the website or provided to the client before cooperation begins. Projects already begun are governed by the version of the document in force at the moment of payment, unless the parties have agreed otherwise.
18.2. The client is advised to read the rules before paying and before work begins. Payment, written consent, confirmation of the project or the start of cooperation may mean the client agrees with the terms set out here.
18.3. The parties aim to settle any dispute through negotiation and written agreement. If particular terms require legal force, the parties may draw up a separate agreement or contract.
How to contact us
For questions about cooperation and about this document, write to us on Telegram: or by email: hello@brickagency.email.
How we handle information about you is set out in the Privacy Policy. Which files the site saves in your browser is described on the Cookie Use page.