Website terms of use and starting an engagement

1. Definitions

• IranCoders or We refers to the operator of the website irancoders.com . Legal entity details have not been finalized in the website's current information, and no invented details are provided.
• User means anyone who visits the website, submits a form, or uses a customer account.
• Client means an individual or legal entity entering into an agreement or contract to receive services.
• Customer account means the private website area for accessing project information, status, reports, invoices, or communications.
• Project contract means any written document agreed by both parties, including a contract, work order, accepted proposal, or addendum.
• User content means information, text, data, or documents lawfully provided to IranCoders by a user.

2. Who can use the website?

Contracted services are available to people with the necessary legal capacity or valid authority to act for an organization. If you act for a company or organization, you are responsible for having the authority to provide information, create an account, and accept the relevant documents.

3. What is website content for?

Articles, guides, service descriptions, examples, and educational material are published for general information and initial decision-making. This material:

• Is not legal, financial, tax, or investment advice.
• Is not a final technical specification for a particular project.
• Is not a quotation or guaranteed delivery date.
• Does not guarantee that a solution suits every business.
• May be updated as technology, markets, or services change.

Important decisions require a separate assessment of the project's actual circumstances.

4. What does submitting a consultation form mean?

Submitting a form or message:

• Records only a request for initial assessment and discussion.
• Does not mean IranCoders has accepted the project.
• Does not create a payment obligation for the user.
• Does not create a service obligation, guaranteed response time, or capacity reservation.
• Does not create a contractual or agency relationship.

Work begins when the required scope and terms are agreed in writing. Form information should be as accurate as possible and must not include passwords, access keys, unlawful information, or unauthorized third-party data.

5. Customer accounts

Public account registration is available through the registration page, but creating an account does not automatically mean a project is accepted or an engagement has begun. A new account will not become active until ownership of the email address is verified using the time-limited link sent to it. Secure password recovery is available through the registered email address, and signed-in users can change their password in account settings.

An account can be used to view project status, reports, milestones, and invoices, and to submit support messages. File uploads and online payments are not available in the current account system. Details of account data processing are provided in the Privacy policy .

Account users must:

• Keep registration and profile information accurate.
• Keep passwords confidential and not share the account with unauthorized people.
• Report suspicious activity and manage access for colleagues who are no longer authorized.
• Use the account only for the engagement and lawful purposes.

6. Prohibited uses

Users must not:

• Access unauthorized accounts, data, or areas, or bypass security or authentication.
• Submit malicious code, malware, or harmful content.
• Use the website to harass, deceive, impersonate, or violate others' rights.
• Submit unlawful content or content that infringes intellectual property rights.
• Impose abnormal loads, automated attacks, or bulk data extraction on the infrastructure.
• Use the IranCoders name or brand to suggest an official relationship or endorsement without permission.
• Sell or transfer their account or make it available to unrelated parties.

These restrictions do not prevent normal use by search engines or accessibility tools.

7. Content you submit

Ownership of information and content you lawfully provide remains with you or its lawful owner. By submitting content, you grant IranCoders only the limited permission needed to respond, assess an engagement, prepare a proposal, perform a contract, store and display information in the account, provide support, maintain security, and meet legal obligations.

This permission does not transfer ownership or authorize public publication. You are responsible for having the permissions necessary to provide and use the content. Retention and deletion requests are explained in the Privacy policy . Current forms and accounts do not allow file uploads.

8. Confidentiality of requests and projects

Initial request information is accessed on a restricted basis and used to assess that request, but the public website form does not itself create a specific confidentiality agreement. If your project requires one, raise the request before sending highly confidential details.

The precise confidentiality terms for project information, exceptions, duration of obligations, authorized recipients, and return or deletion of information are defined in the contract or confidentiality agreement.

9. Intellectual property in website content

Unless stated otherwise, the website design, text, graphics, brand, custom structure, and content produced for IranCoders belong to IranCoders or the relevant license holder. Ordinary personal use for reading and reference is permitted.

Without permission, you must not republish or sell substantial portions of the content, present the website design or identity as your own, use the brand to imply an official relationship, or remove third-party restrictions or attribution. Short quotations with attribution and a link are permitted within the law and customary use.

10. Conceptual case studies

Any example explicitly labeled “conceptual”:

• Is not a real customer project and does not present real customer results, statistics, or testimonials.
• Was prepared to explain an approach to analysis, design, and solution definition.
• Does not guarantee that a future project will achieve the same outcome.

If real case studies are published in the future, publication permission, information scope, and the accuracy of claims must be confirmed separately.

11. Third-party links and services

The website may link to other services, resources, app stores, or websites. IranCoders does not have full control over their content, security, availability, or terms, and their use is governed by the provider's own terms. A link does not mean complete endorsement or acceptance of responsibility for that service's performance.

12. Project proposals, estimates, and contracts

Any price, timeline, or solution discussed initially is approximate and nonbinding until confirmed in a valid written document. A project contract should define the main terms appropriate to the work, including:

• Scope, exclusions, and each stage's deliverables.
• Timeline, dependencies, and responsibility for providing information and approvals.
• Price, tax, invoicing, and payment methods.
• Change management and deliverable acceptance criteria.
• Confidentiality, security, intellectual property, and the timing of its transfer.
• Third-party tools and licenses, deployment, training, and handover.
• Bug fixes, support, maintenance, suspension or termination of the engagement, and dispute resolution.

If this page differs from the project contract, the project contract takes precedence within the scope of that project.

13. Project scope and changes

Evolving and refining requirements is normal in software projects, but a new request is not necessarily part of the original scope. Change requests must be assessed for their effect on deliverables, timing, price, architecture, security, dependencies, and any new service or license.

Out-of-scope changes are implemented after written agreement. Silence or a verbal mention alone does not constitute acceptance of a change.

14. Client responsibilities

Project progress may depend on the client's cooperation, including:

• Providing accurate information and identifying a decision-maker or authorized representative.
• Providing the necessary content, access, and data with valid permission.
• Reviewing and approving deliverables within the agreed time.
• Paying on time and complying with third-party service terms.
• Securing cooperation from the relevant people in the organization.

Delays in essential inputs or decisions may affect the timeline, and their impact must be communicated clearly.

15. Pricing, payments, and third-party costs

Pricing, taxes, invoicing, and payment methods are defined only in the project proposal or contract. The current website has no online payment gateway, and the account area only displays invoice status.

Third-party costs may be separate from development fees, including domains and hosting, SMS and email, payment gateways and fees, software licenses, app store accounts, APIs, cloud services, analytics, monitoring, or licensed content. The contract must identify who pays, who owns each account, and how each service is renewed.

No universal refund policy is announced on the website. Each case is governed by the contract for that engagement.

16. Project delivery, acceptance, and ownership

Delivery may include source code, design files, documentation, server access, a runnable version, data, or training, and must be defined in the contract. Ownership of materials and content provided by the client remains with the client or its lawful owner.

Transfer or licensing of custom deliverables, its timing, and its relationship to payment are governed solely by the contract. Tools, libraries, know-how, general-purpose components, and pre-existing assets are not necessarily transferred unless expressly agreed. Open-source and third-party components remain subject to their own licenses. Domains, infrastructure accounts, and transferable access must also be defined in the contract.

17. Open-source software and third-party components

A software product may use libraries, frameworks, fonts, APIs, or tools licensed by third parties. Rights in these components are governed by their own licenses; transferring a project's custom deliverables does not transfer ownership of those components.

Material limitations or significant costs of a third-party service should reasonably be disclosed before use.

18. App publishing and third-party services

Mobile or integrated-service projects may depend on approval by an app store, payment gateway, API provider, or other third party. IranCoders can assist with preparation and technical issues, but does not guarantee store or gateway approval, search engine rankings, uninterrupted API availability, or third-party decisions.

19. Support, bug fixes, and maintenance

Project delivery does not mean unlimited support. The contract should define the bug-fix period, the distinction between a bug and a new feature, response channels and times, any service level, infrastructure maintenance, security updates, future development, and service costs after the initial period.

Future changes to operating systems, browsers, APIs, third-party services, or infrastructure may require new work.

20. Website availability and performance

We work to keep the website and customer accounts stable and secure, but do not guarantee uninterrupted or error-free access. Parts of the service may be temporarily unavailable for maintenance, security, infrastructure changes, or events beyond our control.

21. Limitation of liability

To the extent permitted by applicable law:

• Public website content is provided using available information and does not replace a project-specific assessment.
• IranCoders is not responsible for decisions based solely on a general article without reviewing the project's circumstances.
• Responsibility for events caused by third-party services, unauthorized use, inaccurate user information, or actions beyond reasonable control is assessed under the law and contract.
• No provision excludes liability that cannot lawfully be excluded.

This page does not set a financial liability cap or an absolute disclaimer. Project-specific limitations must be defined in the individual contract after legal review.

22. Suspension or termination of access

A user's account or access may be restricted because of security risks, unauthorized use, serious breaches of the terms, the end of a contract or access need, a valid legal order, nonpayment under the contract, or the need to protect others' information.

Where possible and there is no immediate risk, the reason or a way to follow up will be communicated. Closing an account does not mean all data is immediately deleted; retention or deletion is governed by the Privacy policy, the contract, and legal requirements.

23. Governing law and dispute resolution

These terms are interpreted within the framework of applicable laws of the Islamic Republic of Iran. If a dispute arises over use of the website, the parties will first try to resolve it through discussion and correspondence. If unresolved, the competent authority will be determined by law or the individual contract.

No particular city, court, or arbitration mechanism has been confirmed in the website's current information, so no invented authority is named.

24. Changes to terms

These terms may be updated as website features, service models, or legal requirements change. A new version applies from publication on this page. Changes do not alter binding obligations in signed contracts without the parties' agreement. The last-updated date appears at the top of the page.

25. Severability and no waiver

If a competent authority finds part of these terms unenforceable, the remaining provisions remain valid as far as possible. Failure to enforce a right immediately does not permanently waive it.

26. Contact

Use the contact page to ask about these terms or start a conversation. A separate official legal email or address has not been confirmed in the project's current information, so no invented details are provided.

Contact IranCoders →