Terms and conditions

1. Our identity and the scope of these terms

MICROTEC2017 is the brand of Comercializadora Microtec 2017, C.A., tax identification number (RIF) J-411590681. Our address for legal correspondence is Parque Central, Caracas, Venezuela, 1010; you can also contact us at [email protected]. This document describes the conditions of our corporate website and the general matters to be addressed when contracting for software, business platforms or technology services.

The website lets you explore our offering and send inquiries. It is not a product administration portal or an automated checkout. Viewing a page, checking a price or submitting the contact form does not purchase a subscription, commission a project or authorize a charge. Nor does it, by itself, constitute consent to personal data processing that requires a specific expression of your wishes.

2. Entering into a business agreement

Before a service begins, the parties must identify the customer, verify capacity or authority and agree on the proposal, scope and applicable conditions through a legally valid acceptance process. Preliminary discussions and demonstrations do not replace that agreement. If you act for an organization, you must have authority to enter into obligations on its behalf.

The proposal and specific documents should establish deliverables, price, duration, usage rights, responsibilities and acceptance. Mandatory law takes precedence in a conflict; validly agreed specific conditions govern the particular service over general website descriptions. Updating this page does not unilaterally amend an existing contract or remove binding precontractual information where the law protects it.

3. Published products, services and examples

Our catalog presents seven existing products: an agentic suite, WhatsApp assistants, customer service, clinic management, ERP, CRM, and banking and fraud prevention solutions. The eighth service is custom software, covering new development and work on existing systems. We also offer website design, mobile applications, AI agents and automation projects, each subject to an agreed scope.

A capability described for a product family is not necessarily included in every plan. Sample screens, diagrams, laboratory scenes and walkthroughs illustrate working situations; they may contain fictional data and do not establish the features of a contracted service. Published customer identities are not testimonials, commitments to achieve results or permission to access those customers’ systems or information.

4. Project scope, dependencies and delivery

Each project should define deliverables, exclusions, the parties supplying information and access, required integrations and the review process. Customizing an existing product is quoted separately unless expressly included. Continuing work on software owned by a customer or third party requires permission to modify it and a review of its dependencies and license conditions.

Timing depends on the agreed scope and identified dependencies, including customer decisions, content, access and approvals. Published custom development ranges cover agreed scopes of up to five months; extensions require separate negotiation. This reference does not make every project a five-month engagement or establish a delivery date before assessment. The parties should identify prerequisites and record how delays affecting either party change the delivery plan.

5. Prices, proposals and offer validity

Product pages display the offers available at the time of your inquiry: starting prices, fixed amounts, ranges or an institutional quotation, as appropriate. A price must be read together with its currency, billing interval, unit, inclusions, limits, extras and tax treatment. A monthly amount should not be confused with a setup fee or the budget for a development project.

The proposal should confirm the applicable offer and its validity before purchase. Ask for clarification if information is missing or inconsistent; a missing price does not imply a free service. Correcting a public error does not authorize us to disregard acquired rights or change agreed charges. Future price adjustments are subject to the contract and applicable information and acceptance requirements.

6. Setup, users and AI usage

Where the applicable existing-product offer states it, setup includes the first month and monthly billing starts in month two. This condition does not automatically extend to custom software. Included users, modules, channels and capacity depend on the product and plan; additional capacity must be agreed and is not presumed to be free or unlimited.

In plans that distinguish these levels, an MCP connection—tools that connect agents with systems—is not the same as including bots or an external provider’s usage. Bot token allowances are shared across the account and may count input, output and context as reported by the provider. The contract should define the model, measurement, billing cycle and excess usage. A token allowance does not guarantee a fixed number of conversations or responses.

7. Payments, taxes, cancellation and refunds

The proposal should identify currency, applicable taxes, due dates, deposits or milestones, and invoicing conditions. Advertised payment methods include Pago Móvil, Venezuelan and international bank transfers, Binance Pay and stablecoins; availability and specific instructions are confirmed for each transaction. Displaying a method does not establish a bank, exchange rate, asset, network or transaction fee.

Do not send funds using instructions you have not verified through an official channel. Cancellation, renewal and refund conditions must be communicated before an agreement, taking the service and applicable law into account. This website does not impose a blanket no-refund policy or waive withdrawal rights or other mandatory protections. It also does not create automatic renewal, penalties or interest that have not been validly agreed.

8. Licenses, intellectual property and source code

Our website content, visual identity and original materials are protected by applicable intellectual property law. You may view them and share legitimate links without claiming authorship, implying company endorsement or removing rights notices. Third-party names and trademarks belong to their respective owners. Their appearance does not grant a license to reuse them beyond what the law permits.

Purchasing platform access does not automatically transfer ownership of the software or its source code. For custom development, the proposal should distinguish pre-existing materials, third-party components and new deliverables, specifying licenses, assignments, repository access and delivery conditions. The customer retains their rights in their data and materials; any permission to use them must be limited to the agreed lawful purpose.

9. Permitted use and user responsibilities

The website and services must be used lawfully and with respect for other people’s rights. Impersonation, malicious content, unauthorized access to another person’s information, evasion of security controls and deliberate interference with system availability are prohibited. Security testing that requires access or affects a service must be coordinated and authorized.

Customers must hold the necessary rights in the data, content and systems they supply, manage their access appropriately and report relevant incidents. These duties do not transfer MICROTEC2017’s responsibility for its own conduct to the customer. You may report a vulnerability responsibly through our contact email, including sufficient information to investigate it without disclosing personal data or secrets encountered accidentally. Avoid further access beyond what is needed to describe the issue safely.

10. Installation and responsibilities on customer servers

Product data is not necessarily hosted on servers managed by MICROTEC2017. Installation on customer servers is available with scope and additional charges agreed by contract; equipment and servers are not included. Before installation, we check the local infrastructure against the security, backup and data protection requirements agreed for the project. The scope and findings of this review must be documented; it does not certify compliance with every regulation or guarantee future conditions that depend on the customer’s operations.

The contract must allocate responsibilities during installation and support: administration, updates, access, connectivity, backups, recovery testing and incident handling. Once installation is complete and the infrastructure support agreement has ended, the customer assumes continuing responsibility for operating their servers and for the custody, security, backup and protection of their data, except for other obligations expressly remaining in effect. The customer must maintain the reviewed requirements, manage changes and arrange personnel or providers for those operations.

MICROTEC2017 retains its responsibilities for the installed software and licenses in effect, according to their scope, warranties, applicable agreements and the law. This allocation does not exclude responsibility for our own defects or breaches, or for actions taken during our involvement. An active license does not by itself include continuing server administration or free, indefinite support; additional maintenance or assistance must fall within contracted coverage or be separately agreed.

11. AI, automation and human oversight

AI systems may produce incomplete, inaccurate or contextually unsuitable responses. Their use requires defined information sources, permissions, controls, testing, accountable people and situations that must be escalated to a human. An automation demonstration does not establish unlimited autonomy or guarantee sales, diagnoses, correct financial decisions or the elimination of fraud.

Before connecting an agent to processes that change records, send messages, approve transactions or affect people’s rights, the project must define permitted actions and review mechanisms. The need for supervision does not replace the provider’s responsibility for its commitments. Data processing by external models, their usage conditions and sector restrictions must be assessed specifically; permission to upload confidential information to any AI tool should never be assumed.

12. Personal data, confidentiality and processing roles

The Privacy Policy explains processing connected with this website and its contact channels. A product deployed for a customer requires identifying, according to actual activities, who determines processing purposes and who processes data on another party’s behalf. The contract and, where applicable, a data processing agreement should address instructions, access, security, providers, retention, transfers and assistance with individual rights.

Do not send passwords, credentials, medical records, full payment card details or another party’s confidential documents through the contact form. If an assessment requires sensitive information, the appropriate channel and safeguards should be agreed first. Sending an inquiry does not itself create a special nondisclosure agreement, without prejudice to our legal obligations concerning privacy, confidentiality and protection of information received.

13. Healthcare, banking and other regulated activities

Clinic software can support administrative work, and banking solutions can support review and control processes. These descriptions do not make MICROTEC2017 a medical provider, financial institution or regulator. They also do not establish product certification, medical authorization or the customer organization’s full compliance with a particular regulation.

Before handling health information, financial information or other specially protected data, the parties should identify requirements relating to the country, activity, data type and contracted functions. The project must define necessary validation, controls and professional responsibilities. Purchasing technology does not replace the customer’s legal duties, nor does it exclude duties that independently apply to MICROTEC2017 as a provider or a participant in data processing.

14. Review, acceptance and scope changes

The proposal should establish how deliverables are presented, who reviews them, which criteria apply and how comments or acceptance are recorded. Disagreements should be assessed against the agreed scope and criteria. This document does not impose automatic acceptance through silence or treat every instance of test use as final approval of a delivery.

A new feature, additional integration, changed requirement or increase in volume may require budget and schedule adjustments before that work begins. Correcting a failure to meet agreed scope should not automatically be treated as a paid extension. The parties should record authorized changes and distinguish requested improvements, covered defects and incidents originating in external dependencies. A clear record helps both parties assess what remains to be delivered.

15. Support, maintenance and availability

Software support, maintenance and ongoing follow-up have their own scope: covered systems, hours, channels, effort, priorities and response conditions should be specified in the proposal or contract. Marketing information does not imply continuous coverage, unlimited work or a particular service level agreement. Availability, recovery and response commitments must be defined together with their conditions and responsibilities.

Our business inquiry hours are 9 a.m. to 6 p.m., Caracas time. A successful contact form submission confirms that the system has recorded the request, not that a person has immediately read it or that every subsequent email has been delivered. An automatic acknowledgment does not accept a project. Urgent matters concerning an existing service should use the support procedure agreed by the parties.

16. Termination, transition and the handling of data

Grounds, notice requirements and effects of termination must follow the contract and applicable law. Before purchasing a platform or project, the parties should define export formats, transition access, delivery of materials, migration assistance and any disclosed charges for additional work. This document does not create a general right to withhold customer data as a means of pressure.

Ending access does not necessarily mean immediate deletion of all information. Controller instructions, retention requirements, pending claims or backup cycles may need assessment. Personal data requests follow the process on our data deletion page; information belonging to an organization using a product also requires identification of its responsible organization and the relevant agreement. Any necessary retention should remain limited to its lawful purpose.

17. Liability, warranties and remedies

Responsibility depends on the contracted service, the commitments made, the circumstances and applicable law. The website does not promise a complete absence of errors, interruptions or incidents, and it does not impose a blanket exclusion of liability in MICROTEC2017’s favor. Any applicable commercial warranties, liability limits and correction procedures must be clear, proportionate and validly incorporated into the relevant agreement.

Nothing on this page excludes liability or rights that cannot lawfully be limited, or seeks to protect intentional wrongdoing, fraud or breaches for which an exclusion would be invalid. Customers retain their applicable legal actions and remedies. Following an incident, the parties should supply reasonably necessary information, take steps to reduce harm and assess available solutions without requiring an advance waiver of mandatory rights.

18. Applicable law, consumers and disputes

MICROTEC2017 operates from Venezuela. Applicable law and dispute resolution mechanisms for an engagement must be determined with regard to the agreement, the parties’ locations, the activity and conflict-of-laws rules. This page does not impose exclusive courts, mandatory arbitration or a waiver of access to a competent authority.

Although our offering is directed at organizations, that focus does not remove protections available to a person who legally qualifies as a consumer. Mandatory rules in their jurisdiction may apply when their requirements are met, including rules on information, warranties, withdrawal, unfair terms and jurisdiction. Access from Latin America, the Caribbean, the United States or Spain does not mean all their laws apply simultaneously or establish universal certification of compliance.

19. External services, links and website continuity

Integrations with WhatsApp, AI providers, payment gateways, cloud services and other platforms may depend on those providers’ accounts, permissions, licenses and fees. Relevant dependencies should be identified before committing to features. Provider changes or incidents can affect an integration, but do not automatically release MICROTEC2017 from its contractual or legal duties to provide information, exercise appropriate care or address a problem.

External links and social profiles provide access to other services with their own terms. Including a link does not imply control over its content or acceptance of its practices on a visitor’s behalf. Check the destination and the conditions of a platform before providing information or carrying out a transaction.

We may correct content, reorganize pages or maintain the website. We aim to keep relevant information understandable and accessible; these activities do not change existing contractual obligations. If you encounter an accessibility barrier, inaccurate information or a broken link that prevents you from exercising a right, contact us by email so that we can review the issue and provide an appropriate way to communicate.

20. Updates, versions and contact

The update date identifies this version. Changes will be published on this page and communicated through appropriate channels when they affect an existing relationship or the law requires it. Publishing a revision does not apply it retroactively to an agreement or replace express acceptance when required. The Spanish and English versions are intended to have the same scope, respecting the language and conditions validly agreed for each engagement.

For commercial clarification, complaints or questions about these terms, email [email protected], identifying the product or service and describing the issue sufficiently. Do not include unnecessary sensitive information. Direct communication is intended to help resolve matters and is not a prerequisite to your right to complain to a competent authority or dispute resolution body.