Terms of engagement

This page describes how Надир Абдурахманов (the "Contractor") works with clients. It is not a public offer and creates no obligations on its own: the terms of a specific project are fixed in a separate agreement signed by both parties.

Where the agreement differs from this page, the agreement prevails.

The scope is written down before work starts: what is included, what is not, and what counts as delivered. Anything absent from that list is out of scope.

Requests that appear after the scope is agreed are handled separately, with their own timeline and price. This is not a refusal to help — without this rule, the quote and the deadline stop meaning anything.

The price is named after the task is analysed and fixed in the agreement. A quote is valid for 14 calendar days; after that the scope may have moved and the estimate has to be repeated.

Work runs in stages with each stage paid up front. If payment is late, work pauses and the delivery date shifts by the length of the pause.

Third-party costs — hosting, domains, paid APIs, app stores — are paid by the client and are not part of the quote unless stated otherwise.

Exclusive rights to the code and materials pass to the client upon full payment for the relevant stage. Until payment, the rights remain with the Contractor.

Repository and infrastructure access is handed over from day one — but access is not a transfer of rights.

The Contractor keeps the right to reuse general technical solutions and know-how in other projects. This does not extend to your data, texts, branding or business logic specific to your company.

Access, data, texts and answers are provided within agreed timeframes. Every day of waiting moves the delivery date by the same day.

The client is responsible for the legality of the materials and data they supply: texts, images, personal data of their customers, rights to the brands used.

If work is halted at the client’s initiative for more than 30 days, the project is treated as suspended: resuming it is negotiated again and re-priced against current availability.

The Contractor is responsible for the system working as described in the agreed scope. Defects found within 30 days of delivery are fixed at no cost.

A defect is a deviation from what was agreed. A new request is not a defect and is quoted separately.

No business outcome is guaranteed: revenue growth, search positions, number of enquiries, or the profitability of a trading strategy. Those depend on the market and on the client’s decisions, not on code quality.

The Contractor is not responsible for outages or changes in third-party services: hosting, payment systems, messengers, model providers, exchanges, app stores. Their failure is not a breach of contract.

The Contractor is not responsible for the system after other people have modified it.

The Contractor’s liability for any losses is limited to the amount actually received under the agreement. Lost profit is not compensated.

Either party may end the work by written notice. The volume actually completed at the moment of notice is paid for, and its result is handed to the client.

The Contractor may decline a project if the task goes beyond what was agreed, requires breaking the law, or if cooperation has become impossible for reasons outside their control.

Access is requested at the minimum: only what the work cannot proceed without, and only for as long as the work lasts. Administrator rights, production databases and customer correspondence are requested solely when the task actually demands them.

Passwords, keys and tokens are never sent in plain text over messengers or email — only through a secret store or a one-time link. No secrets are left in the code or the repository: if something slips in, the key is treated as compromised, revoked and reissued.

After delivery the client revokes the access granted, and the Contractor deletes their copies of data and keys. Where access is needed for ongoing support, it stays by separate agreement and in an agreed scope.

Work is done on a device with full-disk encryption, separate accounts for client projects, and two-factor authentication wherever the service supports it.

If the Contractor discovers a breach, a vulnerability or suspicious activity affecting the client’s system, they report it within 24 hours of discovery, together with what has already been done to contain it. This holds even when the Contractor turns out to be the cause.

Absolute security does not exist. The Contractor applies industry-standard measures but gives no guarantee that a system cannot be broken into — particularly once other people have modified it or third-party services have been connected.

Everything the client shares on the project is treated as confidential and is not disclosed to third parties. A separate non-disclosure agreement is signed on the client’s request — no surcharge, no argument.

Work appears in the portfolio only with the client’s written permission. Declining affects neither price, nor timeline, nor scope.

Development uses assistive tooling, including generative models. Client data is not fed into training of third-party models, and exclusive rights to the result pass to the client under section 4 regardless of which tools produced it.

The parties settle disagreements by negotiation. A claim is reviewed within 15 business days of receipt.

If no agreement is reached, the dispute is heard at the Contractor’s location unless the agreement says otherwise.