MQLDevelopers Terms and Conditions

Version: 1.0
Effective date: 7 August 2026

These Terms and Conditions (the “Terms”) govern access to and use of the MQLDevelopers website, Developer Dashboard, licensing platform, software, plans, add-ons, support and development services.

The services are provided by:

IDEA TERMINAL S.R.L.
Str. Pantei, Nr. 40
535600 Odorheiu Secuiesc, Harghita County, Romania
Tax ID: RO34843319
Trade Register: J2015000234191
Email: office@mqldevelopers.com

IDEA TERMINAL S.R.L. operates the services under the MQLDevelopers name. References to “MQLDevelopers,” “we,” “us,” or “our” mean IDEA TERMINAL S.R.L.

1. Acceptance and contractual documents

1. By creating an account, placing an order, activating a plan, requesting immediate performance, or using any Service, the Customer agrees to these Terms.
2. The Customer confirms that the Customer is at least 18 years old, has full legal capacity to enter into this agreement and, when acting for a company or other organisation, has authority to bind that organisation.
3. The Terms accepted at registration or checkout include Annex 1 – Data Processing Addendum (“DPA”). No separate DPA checkbox is required. The DPA applies only where the Customer uses MQLDevelopers to process personal data on behalf of the Customer or the Customer’s client.
4. The order confirmation, accepted quotation, product or plan description shown at checkout, and any expressly agreed project specification form part of the contract. If an accepted quotation expressly conflicts with these Terms, the quotation controls only for the specific matter stated in it.
5. The Privacy Policy and Cookie Policy explain personal-data and cookie practices but do not replace these contractual Terms.

2. Definitions

• Account: the registered MQLDevelopers user account.
• Active License: a license that has not expired, been deleted, suspended or revoked and is counted by the platform as active.
• Add-on: an optional service purchased in addition to a Plan, including custom-domain, branded-portal, integration or support services.
• Background Technology: all SDKs, frameworks, libraries, tools, modules, templates, utilities, methods, know-how, general-purpose code and reusable components owned, developed or licensed by MQLDevelopers independently of a specific Customer project.
• Business Customer: a Customer acting for purposes relating to a trade, business, craft or profession.
• Business Day: Monday to Friday, excluding public holidays observed in Romania.
• Consumer: a natural person acting for purposes outside that person’s trade, business, craft or profession.
• Customer: the person or entity accepting these Terms.
• Developer: a Customer using the licensing platform for software supplied to the Developer’s own end users.
• End User: a person whose software access or license is managed through the licensing platform.
• Plan: a prepaid licensing-service plan made available by MQLDevelopers.
• Service: any website, dashboard, API, licensing service, SaaS program, Plan, Add-on, support, custom development or related service supplied by MQLDevelopers.

3. Accounts, activation and security

1. Registration requires accurate, current and complete information.
2. Account activation is completed by setting a password through the emailed activation link. An activation or password-setting link is intended to remain valid for 24 hours. A newer link may invalidate an earlier link.
3. An unactivated Account may be deleted after 30 days.
4. The Customer must keep credentials confidential, use separate accounts for separate authorised users and promptly report suspected unauthorised access.
5. The Customer is responsible for activities performed through its Account unless caused by MQLDevelopers’ own security failure.
6. Credentials, API keys and access tokens may not be shared, sold or transferred except where a specific team-access feature expressly permits it.
7. MQLDevelopers may require additional verification where reasonably necessary for security, fraud prevention, payment verification or legal compliance.

4. Services and catalogue

1. The Developer Dashboard may display a catalogue of Plans, Add-ons and services. This catalogue may be informally described as a “shop,” but not every item is an immediately accepted order.
2. A Buy add-on, Buy service or equivalent purchasing action sends the Customer to the checkout. The final checkout step creates a payment obligation only when the Customer submits the order using the clearly labelled payment button.
3. A Request quote action is only a request for information or an offer. It does not create an order, payment obligation or obligation for MQLDevelopers to accept the project.
4. Quote-based work begins only after the parties agree the scope, price, delivery conditions and other material terms.
5. MQLDevelopers may add, modify or discontinue catalogue items, provided that already purchased fixed prepaid periods and accepted project obligations are respected subject to these Terms and mandatory law.

5. Orders and contract formation

1. An order is accepted when payment succeeds and MQLDevelopers issues an electronic order confirmation or activates the purchased Service, whichever occurs first.
2. Plans are normally activated automatically after successful payment.
3. Services requiring configuration, integration, development, branding or other manual work are not completed automatically merely because payment succeeded.
4. MQLDevelopers may reject or cancel an order affected by an obvious pricing error, technical error, duplicate order, legal restriction, security concern or reasonable fraud suspicion. Any amount collected for a cancelled and unperformed order will be returned.
5. A failed, declined, reversed or incomplete payment does not activate the Plan or Service.

6. Prices, currency, taxes and payment

1. Prices and payments are currently denominated in United States dollars (USD).
2. Unless expressly stated otherwise, displayed prices exclude applicable VAT and other mandatory taxes. The checkout should calculate and display applicable tax before the order is submitted, based on the Customer’s location, status and valid tax information.
3. The Customer must provide accurate billing, company, address and VAT information and promptly report any error.
4. The Customer’s bank, card issuer or payment provider may apply currency-conversion fees, foreign-transaction fees or other charges not imposed by MQLDevelopers.
5. Card payments are processed by Stripe. MQLDevelopers does not store the Customer’s full payment-card number.
6. A receipt, invoice or other electronic billing document will be made available through the Account or another electronic channel used for the order.
7. The Customer remains responsible for taxes that the Customer is legally required to account for, including reverse-charge obligations where applicable.

7. Current Plans and included Active Licenses

The following commercial terms apply as of the Effective Date. The price and plan description shown at checkout at the time of purchase form the binding commercial offer for that purchase.

Plan features other than the included Active License limit are described on the applicable plan page or checkout screen.

8. Prepaid term and no automatic renewal

1. Plans are purchased in advance for a fixed period.
2. Plans do not renew automatically, and MQLDevelopers does not automatically charge the Customer for a new Plan period.
3. To continue full Plan functionality, the Customer must purchase another period.
4. MQLDevelopers may display dashboard notices or send service emails before expiry. These are courtesy reminders. Failure to receive a reminder does not extend the Plan or prevent expiry.
5. Purchasing the exact same Plan before expiry extends the existing expiry date by the new standard period. It does not convert remaining time into monetary credit.
6. Purchasing the exact same Plan after expiry starts a new period at activation. Expired time has no value and generates no credit.

9. Trial

1. The Trial is available only once per Customer Account unless MQLDevelopers expressly approves otherwise.
2. It may not be extended, transferred or combined with another Trial.
3. Trial use may not exceed the included Trial license limit. Extra-license overage is not available on Trial.
4. Purchasing a paid Plan ends the Trial immediately. Unused Trial time has no monetary value and does not create credit.
5. When the Trial expires, the Account loses Plan-dependent management rights in the same manner as an expired paid Plan.

10. Effect of Plan expiry

1. At Plan expiry, the Developer loses active license-management rights, including the ability to create, modify, extend, delete, revoke, reactivate or otherwise manage licenses through the dashboard or API.
2. The Developer may retain view-only access where the platform makes it available.
3. Licenses validly issued before Plan expiry continue to operate until their own expiry dates, unless they are otherwise suspended, revoked or stopped under these Terms.
4. A new paid Plan automatically restores the available management rights, subject to the new Plan’s limits and features.
5. Plan expiry does not create a refund, cash credit or compensation for unused account capabilities.

11. Immediate Plan changes and value-based credit

1. An upgrade, downgrade or change to a different Plan code takes effect immediately after successful payment.

2. The Customer pays the full price of the new Plan period.

3. Remaining value from the previous active paid Plan is converted into additional time on the new Plan. The system preserves monetary value, not the number of remaining days.

4. The remaining credit is calculated with second-level precision:

   Remaining Credit = Old Plan Period Value × Remaining Time ÷ Total Old Plan Period

5. The new Plan’s time value is determined using:

   • 30 days for a Monthly Plan; and
   • 365 days for a Yearly Plan.

6. The additional credited time is calculated as:

   Credited Time = Remaining Credit ÷ New Plan Time-Unit Price

7. The new expiry date is:

   Purchase Time + Full New Plan Period + Credited Time

8. No whole-day rounding is required. The calculation may use seconds.

9. No credit is issued:

   • from a Trial to a paid Plan;
   • from an expired Plan;
   • where the old and new purchases use different currencies; or
   • where mandatory law or a payment restriction prevents the conversion.

10. A Monthly-to-Yearly or Yearly-to-Monthly change is a Plan change even where the Plan tier name is the same.

11. Plan credit and credited time are not redeemable for cash, transferable to another Account or withdrawable from the platform.

Illustrative examples

• Growth Monthly to Pro Monthly with 20 of 30 days remaining:
  $19.99 × 20 ÷ 30 = approximately $13.33 remaining value. At approximately $59.99 ÷ 30 per day, this produces approximately 6.67 additional Pro days. The Customer receives the full new 30-day Pro period plus the credited time.

• Pro Monthly to Growth Monthly with 20 of 30 days remaining:
  $59.99 × 20 ÷ 30 = approximately $39.99 remaining value. At approximately $19.99 ÷ 30 per day, this produces approximately 60 additional Growth days. The Customer receives the full new 30-day Growth period plus the credited time.

The examples are explanatory. The platform’s second-precision calculation controls.

12. Extra Active Licenses and automatic overage

1. When the number of Active Licenses exceeds the included Plan limit, extra-license usage begins automatically. The Developer does not need to activate overage separately.
2. Extra Active Licenses are charged monthly in arrears according to the highest concurrent number of extra Active Licenses measured during the relevant 30-day overage period.
3. The current overage rates are:

4. The Trial does not permit extra Active Licenses.
5. Overage periods are 30 consecutive days aligned to the paid Plan activation date or the latest Plan change. Purchasing the exact same Plan as a continuation does not restart the overage period.
6. A Plan change closes the current overage period. A partial period may be charged proportionately by elapsed time, and a new overage period begins under the new Plan.
7. The platform is intended to send courtesy warnings once per overage period when use reaches 50% and 75% of the permitted extra-license capacity. Failure or delay in an alert does not increase the capacity or waive the charge.
8. At 100% of the permitted extra-license capacity, creation of additional licenses is blocked. Existing valid licenses continue to operate.
9. Agency extra-license capacity is not subject to a fixed contractual maximum, although reasonable technical, security and fair-use controls continue to apply.

13. Overage settlement and reduction of remaining Plan time

1. The overage fee for a completed period is:

   Peak Extra Active Licenses × Applicable Monthly Overage Rate

2. Overage fees may be collected through an invoice, checkout or the next Plan purchase.

3. Unless separately paid, an overage fee may be settled at the end of the 30-day period by converting the amount into the equivalent value of the Customer’s current Plan and bringing the Plan expiry date forward.

4. The time deduction is calculated using the actual pre-tax service price paid for the current Plan period, excluding VAT, bank fees and payment-provider charges:

   Time Deduction = Overage Fee ÷ Current Plan Time-Unit Price

5. The current Plan time-unit price is based on 30 days for a Monthly Plan and 365 days for a Yearly Plan. The calculation may use seconds.

6. MQLDevelopers will make the resulting fee, time deduction and revised expiry available through the dashboard, email or another electronic notice.

7. If the remaining Plan time is insufficient to settle the full amount, the Plan may expire and the unpaid balance remains due.

8. Any outstanding overage balance may be added automatically to the Customer’s cart at the next Plan purchase or renewal and must be settled before full Plan rights are restored.

9. An overage amount converted into Plan time is not refundable or redeemable for cash.

14. Manual Add-ons and services

1. Plans activate automatically, but manual Add-ons and services require work by MQLDevelopers.
2. Unless a different period is shown or agreed, manual work will normally be completed within 10 Business Days after both:
   • successful payment; and
   • receipt of all information, files, access rights, approvals and cooperation reasonably required from the Customer.
3. MQLDevelopers aims to complete work earlier where reasonably possible.
4. The delivery period is suspended while required Customer information, access, approval, testing or cooperation is outstanding and resumes when the required item is provided.
5. If an unexpected circumstance, technical dependency or temporary unavailability makes the original period impracticable, MQLDevelopers will provide a revised reasonable delivery estimate without undue delay.
6. If MQLDevelopers cannot complete a paid item within the revised period, the Customer may cancel the unperformed part and receive a refund for that unperformed part, without limiting mandatory Consumer rights.

15. Custom domain services

1. The Customer owns, registers, pays for and renews the domain name.
2. The Customer must provide the DNS access, records, approvals and cooperation reasonably necessary for configuration.
3. Custom Domain Setup covers the initial technical setup required to connect the Customer’s domain to the Service.
4. Managed Custom Domain covers operation of the licensing portal on the configured custom domain and management or renewal of the relevant SSL certificate. It does not include purchase or renewal of the domain name.
5. Later DNS, domain or routing changes are normally separately chargeable unless MQLDevelopers chooses to perform a minor request without charge. A discretionary waiver does not create an ongoing entitlement.
6. MQLDevelopers is not responsible for downtime caused by domain expiry, registrar action, incorrect Customer-controlled DNS changes or missing Customer access.

16. Branded licensing portal

1. A Branded Licensing Portal is the standard MQLDevelopers licensing portal supplied in personalised white-label form.
2. MQLDevelopers names, logos, links, domain references and other visible branding are removed from the customer-facing portal where the service description promises full white labelling.
3. The standard portal structure and functionality remain substantially the same. New functions or material structural changes are custom development and may require a separate quotation.
4. The Customer supplies its brand name, logo, colours and other approved brand assets and warrants that it has the right to use them.
5. The Customer is responsible for its own portal text, product descriptions, legal notices and communications with its End Users.
6. MQLDevelopers may remove or refuse content that appears unlawful, infringing, deceptive, harmful or technically unsafe.

17. Support

1. Standard support is available through email or the authenticated ticket system. No fixed response time is guaranteed, but MQLDevelopers aims to respond within a reasonable period.
2. Priority Support is available only with an active eligible Plan.
3. Priority Support provides an initial response within one Business Day. It does not guarantee resolution within one Business Day and is not a 24/7 service.
4. Support does not include custom development, new integrations, project changes, strategy consulting or work reported after the custom-project acceptance period unless expressly agreed.
5. Support may request logs, test results, files, temporary access or other information reasonably required to investigate a problem.

18. Custom development and integrations

1. Custom work is governed by the accepted specification or quotation.
2. A deviation from the accepted specification is a defect. A new feature, changed requirement, new environment or request outside the accepted specification is a change request.
3. The Deliverables are considered delivered when MQLDevelopers sends the completed files, access or other agreed delivery item to the Customer.
4. The Customer must report specification defects within 14 days after delivery. Properly reported specification defects will be corrected without an additional development fee.
5. For Business Customers, a matter first reported after the 14-day period is treated as a change request and is subject to separate agreement and pricing, even where the Customer describes it as a defect.
6. The 14-day commercial acceptance period does not exclude any mandatory Consumer conformity or remedy rights that cannot lawfully be limited.
7. Platform support or maintenance fees do not automatically cover later custom-project modifications.
8. Change requests, additional revisions and later development are priced and scheduled by separate agreement.

19. Intellectual property in custom work

1. Upon full payment, the Customer owns the project-specific business logic source code expressly identified as a Customer Deliverable.
2. Background Technology remains the exclusive property of MQLDevelopers or its licensors.
3. The Customer does not receive source code for the SDK, framework, libraries, general modules, tools or other Background Technology.
4. The Customer may provide its own business-logic source code to another developer for modification, provided that no MQLDevelopers Background Technology, confidential material or proprietary source is disclosed.
5. The Customer may sell or distribute the compiled final program to its own customers where the accepted project permits this.
6. MQLDevelopers grants the Customer a non-exclusive right to distribute Background Technology only as inseparably embedded in the compiled Deliverable and only as necessary for authorised use of that Deliverable.
7. The Customer may not disclose, extract, publish, sell, sublicense or distribute Background Technology separately, and may not attempt to obtain its source code except to the limited extent mandatory law expressly permits and does not allow contractual exclusion.
8. MQLDevelopers may reuse its Background Technology, general knowledge, techniques and non-customer-specific components in other projects.
9. Customer-supplied materials remain the Customer’s property. The Customer grants MQLDevelopers the rights necessary to use them for the project and warrants that their use does not infringe third-party rights.

20. MQLDevelopers SaaS programs

1. MQLDevelopers-owned EA, indicator and other program offerings are supplied as time-limited SaaS or licensed access, not as perpetual software sales, unless an offer expressly states otherwise.
2. Access and use end immediately when the paid access period expires, even if a program file remains stored on the Customer’s device.
3. The Customer may store any number of backup copies of supplied files. Actual execution and use remain subject to a valid license and applicable account, machine or activation limits.
4. The Customer receives a limited, non-exclusive and non-transferable right to use the program during the valid license period.
5. The Customer may not resell, rent, lend, sublicense or provide the program files or access credentials to another person.
6. Reverse engineering, decompilation, extraction of protected components and circumvention of license controls are prohibited except to the minimum extent mandatory law expressly permits.
7. Minor corrections and updates may be included without an additional charge. MQLDevelopers does not promise that every update, feature or future major version will be included.
8. A major upgrade, material new development level or separate product generation may require a new purchase. MQLDevelopers may offer existing customers a discount but is not obliged to do so.
9. For custom-programmed software, later updates and modifications are governed by the project agreement rather than this SaaS update policy.

21. External platforms and compatibility

1. MQLDevelopers does not control MetaTrader 4, MetaTrader 5, cTrader, brokers, operating systems, hosting providers, payment systems or other third-party platforms.
2. Third-party updates, policy changes, outages, restrictions or technical changes may cause temporary failure or incompatibility.
3. MQLDevelopers may attempt reasonable compatibility corrections, but a material redesign or adaptation may be separately chargeable unless expressly included in the applicable SaaS offer.
4. Compatibility is limited to the systems, versions and conditions described for the relevant Service. The Customer is responsible for checking its own broker, account type, operating environment and third-party restrictions.

22. Customer responsibilities and prohibited use

The Customer must not, and must not permit another person to:

1. use the Service for unlawful, fraudulent, deceptive or abusive purposes;
2. attack, probe, scan, overload, disrupt or interfere with the website, API, licensing infrastructure or another user;
3. introduce malware, harmful code or automated traffic that creates unreasonable load;
4. bypass security, authentication, Plan limits, license controls, usage restrictions or payment mechanisms;
5. access data or systems without authorisation;
6. process personal data without a valid legal basis, required notices or other applicable compliance measures;
7. infringe intellectual-property, confidentiality, privacy or other rights;
8. share or resell Account access, API credentials or Services unless expressly authorised;
9. use the Service to support sanctions violations, criminal activity or prohibited products; or
10. misrepresent an affiliation with MQLDevelopers.

The Customer is responsible for its End Users, products, licensing rules, customer-service decisions, legal notices and the lawfulness of data submitted to the platform.

23. Trading and financial risk

1. MQLDevelopers is a software and technology provider. It is not the Customer’s broker, investment adviser, portfolio manager, fiduciary or trade-execution agent.
2. Software, examples, documentation, signals, tests and support do not constitute investment advice or a guarantee of any financial result.
3. Trading involves risk, including the risk of losing all deposited funds. The Customer and End User make their own decisions and trade entirely at their own risk.
4. Past performance, backtests, simulations and examples do not guarantee future results.
5. The Customer should independently test software, including on a demo environment, and maintain appropriate risk controls before using it with real funds.
6. To the maximum extent permitted by law, MQLDevelopers is not liable for trading losses, account losses, margin calls, missed trades, slippage, broker action, lost opportunity or lost profit.

24. Availability, maintenance and force majeure

1. MQLDevelopers aims to provide a stable and secure Service but does not guarantee uninterrupted availability or a particular uptime percentage unless a separate written SLA expressly states otherwise.
2. The Service may be unavailable because of maintenance, deployment, security work, technical failure, third-party outage or events outside reasonable control.
3. Where reasonably possible, significant planned maintenance will be announced in advance.
4. A longer outage directly attributable to MQLDevelopers may, at MQLDevelopers’ discretion, result in additional Plan time or service credit. No automatic cash refund is created, without limiting mandatory rights.
5. Force-majeure events include, without limitation, server or network failure outside reasonable control, power outage, cyberattack, governmental or regulatory action, war, civil disorder, natural disaster, telecommunications failure and material third-party service disruption.
6. The Customer should maintain its own copies of source files, configuration, reports and other information needed for its business.

25. Suspension and termination by MQLDevelopers

1. For a non-urgent and reasonably curable breach, MQLDevelopers may provide notice and seven days to correct the breach before restricting or terminating the Account.
2. MQLDevelopers may suspend access immediately where reasonably necessary to protect users, data, infrastructure, payments or legal compliance.
3. Immediate action may be taken for serious abuse, API attack, harmful load, fraud or reasonable fraud suspicion, payment dispute or chargeback risk, unlawful personal-data processing, security compromise or a serious violation of these Terms.
4. Suspension may include blocking dashboard access, API access, Plan management and new license creation.
5. In a serious-abuse case, MQLDevelopers may also stop licenses already issued through the affected Account, including licenses that would otherwise remain valid.
6. In ordinary Plan expiry or ordinary Account closure without serious abuse, already issued licenses continue until their own expiry dates.
7. Termination does not remove amounts already due, confidentiality duties, intellectual-property restrictions, liability provisions or other clauses intended to survive.

26. Customer-requested closure

1. The Customer may request Account deletion through support or email.
2. If the Customer requests deletion before the end of a prepaid Plan, the Account and active Plan access may end immediately.
3. Unused Plan time is not refunded, converted into cash or transferred to another Account.
4. Licenses already validly issued continue until their own expiry dates unless serious abuse or another valid suspension ground applies.
5. Personal-data export and deletion are handled under the Privacy Policy and, where applicable, the DPA.

27. Consumer withdrawal, corrections and refunds

27.1 Immediate performance

1. Current Plans and many digital services provide access immediately after payment.
2. Where required, the Consumer will be asked through a separate, unchecked checkout acknowledgement to expressly request performance before the end of the 14-day withdrawal period.
3. For a service, a Consumer who withdraws after requesting immediate performance may be required to pay a proportionate amount for the service supplied before withdrawal. The right of withdrawal may be lost after the service has been fully performed where the legal requirements for that loss are satisfied.
4. For digital content not supplied on a tangible medium, the right of withdrawal may be lost when supply begins if the Consumer gave prior express consent, acknowledged the resulting loss of the withdrawal right and received the legally required confirmation.
5. Nothing in these Terms removes a mandatory Consumer right where the required consent, acknowledgement, information or confirmation was not validly obtained.

27.2 Voluntary 24-hour purchase correction

1. If the Customer accidentally purchases the wrong Plan tier or period, the Customer should contact MQLDevelopers within 24 hours.
2. This is a voluntary correction policy, not an additional statutory refund right.
3. MQLDevelopers will normally attempt a Plan correction, value transfer or account credit first.
4. A cash refund may be approved where correction is not reasonably possible or MQLDevelopers expressly agrees.

27.3 Other refund rules

1. Plan credit, credited time and overage time adjustments cannot be redeemed for cash.
2. No voluntary refund is provided merely because the Customer changes its mind, stops using the Service, requests Account deletion or fails to use available Plan capacity.
3. If MQLDevelopers cannot supply a paid manual Add-on or service, the unperformed portion will be refunded.
4. Refunds, price reductions, contract termination and conformity remedies required by mandatory Consumer law remain available and are not excluded.
5. Any approved refund is normally returned through the original payment channel where practicable. Appropriate billing correction, credit-note or cancellation documentation may be issued.

28. Confidentiality

1. Each party must protect the other party’s non-public technical, business, commercial and security information using reasonable care.
2. Customer business logic, non-public project materials and confidential business information are Customer Confidential Information.
3. Background Technology, non-public SDK and framework information, system architecture, security information and proprietary methods are MQLDevelopers Confidential Information.
4. Confidentiality does not apply to information that the receiving party can demonstrate:
   • is public without breach;
   • was lawfully known without confidentiality duty;
   • was independently developed without use of the confidential information; or
   • was lawfully received from a third party without restriction.
5. A party may disclose information where legally required, after giving advance notice where law permits.
6. Trade secrets remain protected for as long as they qualify as trade secrets. Other confidentiality obligations continue for five years after the relevant disclosure or termination, whichever is later.
7. Access may be given to personnel, professional advisers and contractors who need the information and are bound by confidentiality.

29. Data protection

1. MQLDevelopers processes Account, order, payment, support and service-administration data as described in the Privacy Policy.
2. Where a Developer submits or causes the processing of End User personal data through the licensing platform, the Developer acts as controller, or as a processor authorised to appoint MQLDevelopers as subprocessor, and Annex 1 applies.
3. The Developer is responsible for the lawfulness of its instructions, End User notices, legal bases, retention decisions and responses to its End Users.
4. The Developer must not submit special-category data, passwords, full payment-card information or other unnecessary sensitive information through the licensing API or support channels unless expressly agreed in writing.

30. Communications and notices

1. The Account email address and Developer Dashboard are official communication channels for the Service.
2. MQLDevelopers may send operational messages relating to activation, security, orders, payments, invoices, Plan status, expiry, overage, licenses, support, incidents and material contractual changes.
3. Operational messages are not marketing merely because they relate to an existing Service.
4. The Customer must keep its email address current and review relevant dashboard and email notifications.
5. Failure to read a properly sent operational notice does not by itself extend a Plan, remove a charge or prevent a security action.

31. Changes to prices, Services and Terms

1. Price changes apply only to future purchases, Plan changes and renewals. They do not alter a period already paid for.
2. MQLDevelopers may change these Terms by publishing the updated version.
3. Material changes will normally be notified by email at least 14 days before they take effect.
4. A change required urgently for law, security, fraud prevention or protection of the Service may take effect immediately, with notice as soon as reasonably practicable.
5. Continued use after an effective change constitutes acceptance where permitted by law. Where mandatory law requires fresh express acceptance, MQLDevelopers will request it.

32. Warranties and disclaimers

1. MQLDevelopers will supply Services with reasonable professional care and skill.
2. Except for express commitments in these Terms, an accepted quotation and mandatory law, Services are provided on an “as available” basis.
3. MQLDevelopers does not warrant that every Service will be uninterrupted, error-free, compatible with every external platform or suitable for every Customer strategy or business purpose.
4. The Customer is responsible for independent testing, backups, configuration, End User support and deciding whether the Service is suitable.
5. Mandatory Consumer conformity rights are not excluded.

33. Limitation of liability

1. To the maximum extent permitted by law, MQLDevelopers is not liable for indirect, incidental, special, exemplary or consequential loss, lost profit, lost revenue, lost opportunity, loss of goodwill, loss of anticipated savings, trading loss or loss caused by a third-party platform.
2. To the maximum extent permitted by law, the aggregate liability of MQLDevelopers arising from or relating to an affected Service will not exceed the total amount actually paid by the Customer for that affected Service during the 12 months immediately preceding the event giving rise to the claim.
3. The cap applies to all related claims in aggregate, not separately to each allegation.
4. Where the affected Service was supplied free of charge, liability is limited to the minimum amount required by mandatory law.
5. Nothing excludes or limits liability that cannot lawfully be excluded or limited, including liability arising from fraud, intentional misconduct, gross negligence, death or personal injury where applicable, and mandatory Consumer rights.
6. A refund of an unperformed service, correction of a billing error or mandatory conformity remedy is not a payment for trading loss and does not create responsibility for the Customer’s market activity.

34. Governing law and disputes

1. These Terms are governed by Romanian law, without excluding mandatory rights that apply to a Consumer under the law of the Consumer’s country of residence.
2. The parties should first attempt to resolve a dispute through written support communication.
3. For disputes with a Business Customer, the competent courts having jurisdiction over the registered office of IDEA TERMINAL S.R.L. have jurisdiction, unless mandatory law requires otherwise.
4. A Consumer retains the right to bring or defend proceedings before the courts available under mandatory consumer-jurisdiction rules and may contact the competent consumer-protection authority.

35. Miscellaneous

1. If a provision is invalid or unenforceable, the remaining provisions remain effective, and the invalid provision will be applied to the maximum lawful extent.
2. Failure to enforce a provision is not a waiver.
3. The Customer may not transfer this agreement or Account without prior written approval. MQLDevelopers may transfer the agreement as part of a merger, reorganisation, sale of business or transfer to an affiliate, subject to applicable law.
4. These Terms, accepted quotations, order confirmations and incorporated annexes constitute the agreement for the relevant Service.
5. Electronic acceptance, logs recording the accepted version and electronic communications may be used to evidence the agreement.
6. Headings are for convenience and do not change interpretation.

Consumer Withdrawal Information and Model Form

This section applies only where the Customer is a Consumer and a statutory withdrawal right exists.

Withdrawal period

The Consumer normally has 14 days from conclusion of a service or digital-service contract to withdraw without giving a reason, subject to the exceptions and consequences described in Section 27.

To exercise the right, the Consumer must send an unambiguous statement before the period expires to:

IDEA TERMINAL S.R.L.
Str. Pantei, Nr. 40, 535600 Odorheiu Secuiesc, Harghita County, Romania
Email: office@mqldevelopers.com

Email is sufficient. The Consumer may use the model below but is not required to do so.

Model withdrawal form

To: IDEA TERMINAL S.R.L., Str. Pantei, Nr. 40, 535600 Odorheiu Secuiesc, Harghita County, Romania; office@mqldevelopers.com

I hereby give notice that I withdraw from my contract for the following service or digital content:

• Service / digital content:
• Order number:
• Ordered on:
• Consumer name:
• Consumer address:
• Consumer email:
• Date:
• Signature (only if submitted on paper):

Annex 1 – Data Processing Addendum

This Data Processing Addendum (“DPA”) forms part of the Terms. It is intended to satisfy Article 28 of Regulation (EU) 2016/679 (“GDPR”) where MQLDevelopers processes personal data on behalf of a Developer.

DPA 1. Parties, scope and roles

1. The Customer accepting the Terms is the Controller for this DPA, or is a processor that has authority from its own controller to appoint MQLDevelopers as a subprocessor.
2. IDEA TERMINAL S.R.L. is the Processor for personal data processed through the licensing platform on the Controller’s behalf.
3. Account, billing, fraud-prevention, security and direct customer-relationship processing performed by MQLDevelopers for its own purposes is governed by the Privacy Policy and falls outside this DPA to the extent MQLDevelopers acts as an independent controller.
4. This DPA applies automatically when the Controller uses the Service to process End User personal data.

DPA 2. Subject matter and duration

1. The subject matter is the hosting, validation, management, security, support and operation of software licenses and related technical services for the Controller’s End Users.
2. Processing continues for the duration of the relevant Service and for the limited retention periods described below.
3. The nature, purpose, data categories and data subjects are described in Schedule A.

DPA 3. Documented instructions

1. The Processor will process Controller Personal Data only on documented instructions from the Controller, including these Terms, the Controller’s dashboard configuration, API requests and written support instructions.
2. The Processor may process data where required by EU or Member State law. Where legally permitted, the Processor will inform the Controller before that processing.
3. If the Processor believes an instruction infringes data-protection law, it will inform the Controller and may suspend the affected operation until the issue is resolved.
4. The Processor is not required to perform an unlawful instruction.

DPA 4. Controller obligations

The Controller must:

1. have a valid legal basis for the processing and provide all required notices to End Users;
2. ensure that instructions are lawful, accurate and proportionate;
3. collect only data necessary for the licensing purpose;
4. avoid submitting special-category data, passwords, full payment-card data or other unnecessary sensitive data;
5. configure appropriate license, retention and access rules;
6. respond to End User requests and supervisory-authority enquiries; and
7. ensure that it is authorised to appoint the Processor and any approved subprocessors.

DPA 5. Confidentiality and authorised personnel

1. Access to Controller Personal Data is limited to personnel who need access for their duties.
2. Authorised personnel are bound by confidentiality obligations.
3. The Processor uses separate administrative accounts and will remove access when it is no longer required.
4. Access rights are reviewed periodically in a manner proportionate to the Service and risk.

DPA 6. Security

1. The Processor will maintain appropriate technical and organisational measures taking account of the state of the art, implementation cost, processing context and risk.
2. Current core measures are described in Schedule B.
3. The Controller acknowledges that no system can be guaranteed completely secure and must use the Controller-side security features, credential protection and configuration options made available.

DPA 7. Subprocessors

1. The Controller gives general written authorisation for the subprocessors listed in Schedule C.
2. The Processor will impose data-protection obligations on subprocessors that are no less protective, in substance, than the relevant obligations in this DPA.
3. The Processor remains responsible to the Controller for performance of the subprocessor obligations as required by GDPR Article 28.
4. Before adding or replacing a subprocessor that will process Controller Personal Data, the Processor will provide at least 14 calendar days’ notice by email or another durable electronic channel.
5. The Controller may object during that period on reasonable, documented data-protection grounds.
6. The parties will attempt in good faith to resolve a valid objection. If no reasonable alternative is available, either party may terminate the affected processing Service in accordance with the Main Terms and mandatory law.
7. Emergency replacement may occur sooner where necessary to protect security, continuity or legal compliance. The Processor will provide notice as soon as reasonably practicable.

DPA 8. International transfers

1. Primary hosting is intended to take place in the EEA, with the production region located in Frankfurt, Germany.
2. Personal data will be transferred outside the EEA only where necessary and where a valid legal mechanism applies, such as an adequacy decision, approved Standard Contractual Clauses or another mechanism permitted by Chapter V GDPR.
3. The Processor will apply supplementary safeguards where reasonably required by applicable law and the transfer risk.

DPA 9. Data-subject requests

1. The Controller remains responsible for responding to End User access, correction, deletion, restriction, objection, portability and other data-protection requests.
2. Taking account of the nature of processing, the Processor will provide reasonable technical assistance to the Controller.
3. The Processor will not disclose Controller Personal Data directly to an End User without the Controller’s authorisation unless legally required.
4. If the Processor receives a request directly, it will normally refer the requester to the Controller and notify the Controller where appropriate.
5. Reasonable assistance is included in the Service. Exceptional, repetitive or substantial manual work may be separately chargeable after advance notice and agreement, except where charging would conflict with mandatory law.

DPA 10. Assistance with compliance

Taking account of the nature of processing and information available, the Processor will reasonably assist the Controller with:

1. security obligations;
2. personal-data-breach assessment and notification;
3. data-protection impact assessments;
4. prior consultation with a supervisory authority; and
5. information reasonably required to demonstrate compliance.

DPA 11. Personal-data breaches

1. The Processor will notify the Controller without undue delay after becoming aware of a personal-data breach affecting Controller Personal Data.
2. The notice will include, to the extent known:
   • the nature of the breach;
   • affected data and data-subject categories;
   • likely consequences;
   • measures taken or proposed; and
   • a contact point for follow-up.
3. Information may be provided in stages as the investigation develops.
4. Notification is not an admission of fault or liability.
5. The Controller remains responsible for deciding whether notification to a supervisory authority or End Users is legally required.

DPA 12. Return, export, deletion and retention

1. On termination, the Controller may request export of Controller Personal Data before deletion is completed, using the available platform or support process.
2. Active identifiers will then be deleted or anonymised according to the Service’s deletion workflow.
3. Soft-deleted End User identifiers may remain for up to 90 days for recovery, security, fraud prevention and operational integrity.
4. Limited non-identifying audit information may be retained for up to five years.
5. Backup copies may remain for up to 12 months and are used only for disaster recovery or restoration. If restored, data scheduled for deletion will be removed again through the ordinary deletion process.
6. Data may be retained longer where EU or Member State law, a binding authority request or an actual legal dispute requires it. Processing during that period will be restricted to the relevant purpose.
7. The Processor will securely delete data when the applicable retention period ends.

DPA 13. Audits and information rights

1. The Processor will make available information reasonably necessary to demonstrate compliance with Article 28 GDPR.
2. Verification will normally begin with documents, questionnaires, policies, reports and remote explanations.
3. A technical or on-site audit may be requested only where reasonably justified by a material data-protection concern, incident, supervisory-authority requirement or insufficient documentary evidence.
4. Audits require reasonable advance notice, confidentiality, appropriate scope and measures protecting the security and confidentiality of other customers.
5. The Controller and its auditor may not access another customer’s data, unrelated source code, security secrets or information whose disclosure would create an unreasonable security risk.
6. The Controller bears reasonable audit costs unless the audit identifies a material breach by the Processor, in which case reasonable allocation will be agreed or determined under applicable law.
7. Nothing limits a competent supervisory authority’s lawful powers.

DPA 14. Suspension and inability to comply

1. If the Processor cannot comply with this DPA, it will inform the Controller without undue delay.
2. The Controller may require the affected processing to be suspended until compliance is restored.
3. A material or persistent breach may allow termination of the affected Service, subject to the Main Terms and mandatory law.

DPA 15. Liability and precedence

1. Liability under this DPA is subject to the limitation-of-liability provisions in the Main Terms to the maximum extent permitted by law.
2. Nothing limits data-subject rights or regulatory powers under the GDPR.
3. If this DPA conflicts with the Main Terms on processing of Controller Personal Data, this DPA controls for that conflict.

Schedule A – Processing details

Data subjects

• End Users of software licensed by the Developer;
• authorised Customer personnel whose identifiers appear in licensing or support records; and
• other individuals whose technical identifier is submitted by the Controller for the licensed purpose.

Categories of personal data

• Account ID or other identifier selected and supplied by the Controller or the licensed software;
• Machine ID generated client-side by the licensing module;
• license, product and Developer identifiers;
• license status, activation status, expiry, suspension and deletion information;
• IP address;
• timestamps, API endpoint, request status, response status and error information;
• masked token references and security/audit events; and
• support information voluntarily submitted by the Controller.

The external Developer licensing API is not designed to collect End User names, email addresses, billing data, full payment-card information or passwords.

Nature and purpose

• create, validate, challenge, verify, activate, suspend, expire and administer software licenses;
• enforce license limits and product rules;
• provide dashboard and API functionality;
• secure the Service, detect abuse and investigate errors;
• provide support and operational audit records; and
• meet legal obligations applicable to the Service.

Frequency and duration

Processing occurs when the Controller or licensed software uses the dashboard, API or license-validation functions. Duration follows the Service term and the retention rules in DPA 12.

Schedule B – Current technical and organisational measures

• HTTPS encryption for data in transit;
• role-based and need-to-know access controls;
• separate administrative user accounts;
• password hashing for Account authentication where applicable;
• logging of relevant security, API and administrative events;
• masking of license tokens and avoidance of full secrets in ordinary logs;
• backups for disaster recovery;
• software, operating-system and dependency updates;
• access removal when no longer required;
• incident investigation and response procedures; and
• physical and infrastructure protections supplied by the hosting provider.

The measures may evolve where security improves, provided that the overall protection is not materially reduced.

Schedule C – Approved subprocessors

Stripe, analytics and general website providers are not listed here merely because they serve MQLDevelopers. They are included in this DPA only if they actually process Controller Personal Data for the external Developer licensing purpose.