Terms and Conditions of Use
Version 1.0 · Effective 13 September 2026
In case of any conflict between the English and Arabic texts, the Arabic text prevails.
These terms and conditions (the "Terms") are a binding legal contract between Genius Artificial Intelligence Solutions LLC (the "Company" or "Lerix"), registered in the Sultanate of Oman under commercial registration number 1674746, with its head office in Muscat, Sultanate of Oman, and any natural or legal person who accesses the Lerix platform at lerix.dev or uses any of its services (the "Client"). By using, subscribing to or accessing the platform, the Client confirms that it has read, understood and fully and unconditionally accepted these Terms, and that it holds the legal capacity and representative authority needed to enter into this contract. If the Client does not agree to these Terms or any part of them, it must stop using the platform immediately.
1. Article One — Definitions
The following words and expressions carry the meanings set against each of them, unless the context requires otherwise:
a. Platform: the Lerix platform in all its components, available at lerix.dev and through the application programming interfaces (APIs), software development kits (SDKs) and accompanying tools.
b. Company: Genius Artificial Intelligence Solutions LLC, registered in the Sultanate of Oman.
c. Client: any natural or legal person who has entered into a subscription with the Company or who accesses the platform for commercial or professional purposes.
d. Client Account: the digital account created in the Client's name on the platform, including sub-accounts and team member accounts.
e. Service or Services: the set of tools and features the Company provides through the platform, including but not limited to real-time error tracking, application performance monitoring (APM), analytics, push notifications, and MCP protocol integration with AI agents.
f. Software Development Kit (SDK): the code, libraries and tools provided by the Company and integrated by the Client into its applications in order to send telemetry and record errors.
g. Client Data: all data and information the Client sends, or that is sent on its behalf, to the platform through the SDK, the APIs or any other means, including the end user data of the Client's applications.
h. End User: any person who uses the Client's application or service and whose data is sent to the Lerix platform through the SDK.
i. Monthly Active User (MAU): any unique end user recorded as active within the Client's application during a single calendar month, as measured by the Company's counting method.
j. Token: the unit used to measure consumption of AI resources allocated to each subscription plan.
k. MCP Integration: integration with the Model Context Protocol, which allows AI agents to read and automatically process telemetry data.
l. Subscription Plan: the pricing package chosen by the Client (free, one of the three paid tiers, or the negotiated enterprise plan).
m. Data Processing Agreement (DPA): the separate agreement referred to in Article Fifteen of these Terms, governing the processing of end user data.
n. Intellectual Property: all patent rights, copyright, trademarks, trade secrets, know-how and any other moral rights, whether registered or unregistered.
o. Regulator: the government body competent for personal data protection in the Sultanate of Oman.
p. Working Day: any day of the week other than Friday, Saturday and official public holidays in the Sultanate of Oman.
2. Article Two — Acceptance of the Terms and Eligibility
2-1. Nature of the contract: these Terms are a commercial contract between two professional parties (B2B). The platform is designed solely for commercial and professional use by developers, engineering teams and organisations; it is not intended for personal or recreational use, or for use by individual consumers acting as such.
2-2. Eligibility to subscribe: the Client confirms that it meets all of the following conditions:
a. If a natural person: that they are at least eighteen (18) years of age and are acting in a professional capacity or on behalf of a commercial establishment.
b. If a legal person (company or establishment): that the person registering the account or accepting these Terms is legally authorised to act and sign for that entity, and that the entity is lawfully incorporated and in good standing in its country of incorporation.
c. That the Client is not barred from receiving the services under any applicable law or regulation.
2-3. Electronic acceptance: clicking "I agree", "Create account" or "Subscribe", or using the platform in any form, constitutes electronic acceptance equivalent to a handwritten signature under the Electronic Transactions Law issued by Royal Decree 39/2025. The legal person confirms that the individual who accepted these Terms holds the authority to do so.
2-4. Reliance on representations: the Company reserves the right to rely on the Client's representations as to eligibility, and is released from any liability if they prove untrue.
3. Article Three — Description of the Service
3-1. Platform components: through the Lerix platform, the Company provides an integrated set of software monitoring and diagnostic services, including:
a. Real-time error tracking: detecting, classifying and displaying application errors as they occur, with technical diagnostic detail.
b. Application performance monitoring (APM): measuring and analysing application performance indicators such as response times, network transaction tracing and database performance.
c. Analytics dashboards: aggregating usage data and presenting it in customisable charts and dashboards.
d. Push notifications: sending real-time alerts through the built-in channels (email, instant messaging, webhooks) when events are detected or defined thresholds are crossed.
e. MCP integration and AI agents: allowing AI agents to query and interact with platform data through the standard MCP protocol.
f. Software development kit (SDK): code libraries for integrating the services into the Client's applications, available for multiple platforms and programming environments.
3-2. Plans and tiers: the service is offered under the following plans:
a. Free plan: with restricted limits on MAU, tokens and features.
b. Paid plans (three tiers): with expanded limits varying by tier.
c. Enterprise plan: on terms set contractually in a specific agreement.
The limits, prices and features of each plan are set out on the pricing page available on the website and form an integral part of these Terms.
3-3. Changes to the service: the Company reserves the right to improve or modify service components, add new features or discontinue existing ones as development requires, subject to Article Eight of these Terms.
3-4. Beta and early access services: the Company may make some features available in beta or early access form. These features are provided "as is" without any warranty, and the Company may discontinue or modify them at any time.
4. Article Four — User Accounts and Account Security
4-1. Creating an account: the Client must provide accurate, complete and correct information when registering an account and keep it up to date at all times. Impersonating others or providing misleading information is prohibited.
4-2. Credentials and account security: the Client alone bears full responsibility for:
a. Keeping passwords and login details confidential and not sharing them with any unauthorised party.
b. Securing API keys and access tokens and not publishing them in public code repositories or any publicly accessible platform.
c. Managing team member sub-accounts and setting permissions on the principle of least privilege.
d. All activity and operations carried out through its account, whether by the Client itself or by another party using its credentials.
4-3. Immediate notification: the Client undertakes to notify the Company immediately at [security@lerix.dev] or [support@lerix.dev] on discovering any breach or unauthorised access to its account or its API keys.
4-4. Multiple accounts: the Client may not create more than one account in order to circumvent the limits of its subscription plan. Creating multiple accounts for this purpose is an express breach of these Terms.
4-5. Limited Company liability: the Company bears no liability for losses arising from unauthorised access caused by the Client's failure to secure its account or its API keys.
5. Article Five — Acceptable and Prohibited Use
5-1. Acceptable use: this contract permits the Client to use the platform solely in order to:
a. Monitor, diagnose and improve the performance of the Client's applications.
b. Analyse error and telemetry data sent from the Client's legitimate applications.
c. Integrate the SDK into its commercial and professional applications.
d. Pursue other legitimate commercial purposes consistent with the nature of the platform.
5-2. Prohibited use: the Client is absolutely prohibited from doing any of the following:
a. Reverse engineering: disassembling, restructuring or reverse engineering the SDK, the platform's source code or any of its components, or attempting to extract its trade secrets.
b. Improper use of AI: using MCP integrations or AI agents to generate or publish harmful or misleading content, or to circumvent the ethical safeguards of AI models.
c. Sending unauthorised sensitive data: sending sensitive personal data such as health data, precise financial data, children's data or national identity data through the SDK without appropriate legal compliance measures and the necessary consents from data subjects.
d. Deliberate overloading: launching denial of service attacks or generating excessive artificial traffic intended to exhaust the Company's infrastructure.
e. Unlawful activity: using the platform to commit any crime or activity that breaches Omani law or applicable international law, including infringement of third party intellectual property.
f. Unauthorised resale: reselling the service or granting sublicences to third parties without the Company's prior written permission.
g. Competitive intelligence: using the platform for benchmarking or intelligence-gathering purposes aimed at developing directly competing products.
h. Privacy violations: collecting or processing end user data in a way that contradicts the legal notice disclosed to them, or without an appropriate legal basis for the processing.
5-3. Consequences of breach: a breach of this Article entitles the Company to suspend or terminate the Client's account immediately under Article Nine, while reserving the right to claim compensation for resulting damage.
6. Article Six — Rate Limits, Quotas and Volume of Use
6-1. Units of measurement: usage limits are measured on two main factors:
a. Monthly active users (MAU): the number of unique end users recorded as active in the Client's applications during each calendar month.
b. Token budget: the maximum monthly consumption of AI resources allocated to the subscription plan.
6-2. API limits: the Company applies rate limiting across all APIs to keep the service stable for all clients. These limits are documented in the developer documentation available on the website and may be updated with prior notice.
6-3. Exceeding quotas:
a. As the Client approaches the usage limits of its plan, the Company sends automatic alerts through the control panel and by email.
b. On reaching the set limit, the Company reserves the right to:
• Restrict or temporarily suspend the Client's access to some features until the start of the next billing cycle.
• Upgrade automatically to the higher plan on the published terms, where the Client has expressly agreed to this in advance.
• Apply overage charges at the pricing set out on the pricing page.
6-4. Unused tokens: unused tokens do not carry over from month to month on monthly plans unless the Client's plan expressly provides otherwise. Consumed tokens are non-refundable under the refund and cancellation policy.
6-5. Client responsibility: the Client is responsible for monitoring and managing its own consumption, and the Company bears no liability for charges arising from the Client exceeding the limits of its plan.
7. Article Seven — Intellectual Property and Licence
7-1. Company ownership: the Company alone owns all rights and interests in the platform, including:
a. The platform's source and compiled code and its technical architecture.
b. All SDK components provided to the Client.
c. Processing algorithms, AI technologies and the embedded machine learning models.
d. User interfaces, designs, trademarks and the Lerix logo.
e. Technical documentation and guides.
f. Aggregated, anonymised data derived from client data in a form that does not allow any person or client to be identified.
7-2. Licence granted to the Client: the Company grants the Client a non-exclusive, non-assignable, non-sublicensable licence (except within the Client's internal use), limited to the subscription term, to:
a. Access and use the platform through the web interfaces and APIs in accordance with these Terms.
b. Integrate the SDK into the Client's applications and distribute it within them for tracking and telemetry purposes.
c. Consult the developer documentation and use the code samples contained in it.
This licence is limited to the Client's internal use and the development of its own products, and does not extend to independent redistribution of the SDK or the platform.
7-3. Ownership of Client Data: the Client retains all ownership rights in its application data and end user data ("Client Data"). The Company claims no ownership of Client Data. The Client grants the Company a limited, non-exclusive licence to process Client Data only to the extent needed to deliver and develop the services under these Terms and the Data Processing Agreement.
7-4. Feedback and suggestions: if the Client sends comments, suggestions or ideas relating to the platform ("Feedback"), it grants the Company a perpetual, unlimited, royalty-free licence to use that Feedback to improve and develop the platform, with no obligation of disclosure or compensation.
7-5. Trademark use prohibited: the Client may not use the Lerix name, logos or trademarks in any marketing or advertising material without the Company's prior written permission.
8. Article Eight — Service Level and Feature Changes
8-1. Paid plans below enterprise: the Company aims to make its services available around the clock, seven days a week, but does not guarantee a specified uptime percentage for the three paid subscription plans. The Company makes reasonable efforts to limit scheduled downtime and to notify clients of it in advance.
8-2. Enterprise plan: the service level (SLA) for enterprise clients is governed by the terms of the contract concluded with them, and may include specific uptime commitments and downtime compensation mechanisms.
8-3. Scheduled maintenance: the Company notifies clients of scheduled maintenance windows that may affect service availability at least [48] hours in advance, through the control panel or the registered email address, except in cases of emergency maintenance to address security vulnerabilities.
8-4. Modifying and discontinuing features:
a. The Company reserves the right to modify, improve or replace any feature with an equivalent one without prior notice, provided this does not materially reduce the value delivered to the Client.
b. If the Company decides to discontinue a core feature permanently, it notifies affected clients at least [30] days in advance (or [90] days for enterprise clients).
c. Changes the Company makes to beta features do not count as discontinuing a core feature.
8-5. Free plan: the free plan is provided "as is" without any service level guarantee, and the Company may change its limits or terms at any time.
9. Article Nine — Account Suspension and Termination
9-1. Termination by the Client: the Client may terminate its subscription at any time under the refund and cancellation policy, through the control panel or by sending a written request to [support@lerix.dev].
9-2. Suspension by the Company: the Company may temporarily suspend the Client's account, with immediate or prior notice depending on the circumstances, in the following cases:
a. A serious suspicion of breach of the acceptable use provisions in Article Five.
b. Failure to pay amounts due on time after the payment notice period of [7] working days has expired.
c. A security risk requiring access to be cut off immediately to protect the platform or other clients.
d. A court order or a request from a competent government body.
9-3. Termination by the Company:
a. Termination for cause: the Company may terminate this contract immediately on written notice to the Client where:
• A material breach of these Terms has occurred and has not been remedied within [14] working days of notice.
• A judgment of bankruptcy is issued against the Client or a receiver is appointed over its assets.
• The Client breaches applicable law in a way that may expose the Company to legal liability.
b. Termination without cause: the Company may terminate the service for free plan clients without cause on [30] days' notice, and for paid plan clients on [60] days' notice with a refund of fees paid in advance for the unused period.
9-4. Effects of termination: on termination of the contract for any reason:
a. The Client's licence to use the platform and the SDK ends immediately.
b. The Company retains Client Data for [90] days from termination so the Client can retrieve it, after which it is permanently deleted under the Data Processing Agreement.
c. The Client remains liable to pay all amounts due up to the date of termination.
d. Articles that by their nature survive termination remain in force, including intellectual property, liability and indemnity, governing law and confidentiality.
10. Article Ten — Disclaimers and Limitation of Liability
10-1. General disclaimer: the platform's services are provided "as is" and "as available". To the extent permitted by Omani law, the Company expressly disclaims all implied warranties, including the implied warranties of fitness for a particular purpose, merchantability and non-infringement.
10-2. Exclusion of indirect damages: to the fullest extent permitted by law, the Company is in no event liable for:
a. Consequential, incidental, special, punitive or aggravated damages.
b. Loss of profits, revenue, business or business opportunities.
c. Loss of or damage to data, or inability to recover it.
d. Business interruption or disruption.
e. The cost of substitute services.
f. Damage arising from the Client's reliance on the accuracy or soundness of AI outputs.
This applies even if the Company was told in advance that such damage might occur.
10-3. Financial cap on liability: the Company's total liability to the Client arising out of or in connection with this contract, whatever its source and whatever legal theory is relied on, is capped at the lesser of:
a. The total fees actually paid by the Client to the Company during the six (6) months immediately preceding the event giving rise to liability; or
b. OMR [5,000].
10-4. Exceptions to the cap: the limits in clauses 10-2 and 10-3 do not apply to:
a. Liability for fraud or express misrepresentation.
b. Liability that Omani law does not permit to be excluded or limited.
c. A serious breach of the confidentiality provisions.
d. Infringement of the Client's intellectual property rights by a direct act of the Company.
10-5. Fair allocation of risk: the Parties acknowledge that the liability cap and disclaimers in this Article reflect a reasonable allocation of commercial risk between them, and that subscription prices were set on the basis of that allocation.
11. Article Eleven — Indemnity
11-1. Client's indemnity: the Client undertakes to indemnify, hold harmless and defend the Company, its directors, employees, representatives and affiliates from and against any claims, actions, losses, damages, fines or reasonable legal costs and expenses arising from:
a. The Client's breach of these Terms.
b. Data the Client sends through the SDK and any liability arising from it towards end users, regulators or third parties.
c. Misuse of the AI integrations and MCP tools.
d. Infringement of third party intellectual property rights through data or content the Client sends.
e. Failure to obtain the necessary legal consents from end users before collecting and processing their data.
f. Breach of the laws and regulations applicable to the Client.
11-2. Company's indemnity: the Company undertakes to indemnify, hold harmless and defend the Client from and against any third party claims alleging that the SDK or the platform itself infringes intellectual property rights recognised in the Sultanate of Oman. This obligation is subject to the liability cap in Article Ten.
11-3. Indemnity procedure: the party seeking indemnity must:
a. Notify the indemnifying party in writing as soon as it becomes aware of the claim.
b. Give the indemnifying party the right to lead the legal defence and settlement negotiations.
c. Cooperate reasonably with the indemnifying party in responding to the claim.
12. Article Twelve — Force Majeure
12-1. Definition of force majeure: events outside the affected party's will and reasonable control that could not reasonably be foreseen or guarded against, including but not limited to: natural disasters, earthquakes and floods; war and armed conflict; sanctions and government decisions; outages of major international internet networks; large-scale distributed denial of service (DDoS) attacks despite reasonable protective measures; officially declared epidemics and pandemics; and outages at major cloud infrastructure providers.
12-2. Effects and obligations: where force majeure occurs:
a. The affected party is excused from performing its contractual obligations for the duration of the event.
b. The affected party must notify the other party in writing as soon as possible and within [72] hours of becoming aware of the event, describing its nature and its estimated duration.
c. The affected party makes reasonable efforts to mitigate the effects of the event and resume performance as soon as possible.
12-3. Termination on continuation: if a force majeure event continues for more than [60] consecutive days, either party may terminate this contract on [15] days' written notice, without this counting as a contractual breach, with a refund of fees paid in advance for the unused period.
13. Article Thirteen — Third Party Services
13-1. External integrations and services: the platform may allow the Client to integrate with third party services, including:
a. Generative AI models and the cloud services associated with them.
b. Alerting and communication tools (such as Slack, PagerDuty and others).
c. Code management and repository platforms.
d. Authentication and identity management services.
e. Any other integrations the platform offers through the MCP protocol or otherwise.
13-2. Independence of third parties: third party services are governed by their own terms of use and privacy policies. The Company bears no liability for:
a. The accuracy, reliability or availability of third party services.
b. Any changes those parties make to their services that affect integration with the platform.
c. Privacy or security breaches arising within the third party's environment.
d. The outputs of external AI models and the uses made of them.
13-3. External AI models: the Client acknowledges that the platform's use of external AI models through unified programming interfaces means that data sent to those models may be subject to their providers' privacy policies, and that the Client is responsible for reviewing those policies and confirming they align with its obligations to its end users.
13-4. External links: any links to external sites contained in the platform's documentation do not constitute an endorsement of those sites, and the Company bears no liability for their content.
14. Article Fourteen — Governing Law and Jurisdiction
14-1. Governing law: this contract is governed by and construed in accordance with the laws in force in the Sultanate of Oman, in particular:
a. The Electronic Transactions Law issued by Royal Decree 39/2025.
b. The Personal Data Protection Law issued by Royal Decree 6/2022 and its Executive Regulations.
c. The Omani Civil Code and any other relevant laws in force in the Sultanate of Oman.
14-2. Amicable settlement: the Parties undertake to seek an amicable resolution first for any dispute arising out of or connected with this contract, by sending written notice of the dispute to the other party. A period of [30] days from the date of notice is allowed for good faith negotiation.
14-3. Jurisdiction: if the Parties fail to reach an amicable resolution within that period, the competent courts of the Governorate of Muscat, Sultanate of Oman, have exclusive jurisdiction over the dispute, and each party accepts the personal jurisdiction of those courts.
15. Article Fifteen — Data Processing Agreement
15-1. Automatic incorporation: the Data Processing Agreement (DPA) concluded between the Company and the Client forms an integral part of and supplements these Terms. Where no separate data processing agreement has been concluded, the standard DPA published at lerix.dev applies automatically to all processing of end user data received through the SDK.
15-2. The Company's dual role: the Parties acknowledge that the Company acts in two distinct capacities:
a. As controller: in respect of the Client's own account data, operational and billing data, and usage logs tied directly to the Client account.
b. As processor: in respect of the end user data of the Client's applications sent through the SDK, on behalf of the Client as controller.
15-3. Client responsibility: the Client bears full responsibility as controller for:
a. Obtaining the necessary legal consents from its end users before collecting their data and sending it to the platform.
b. Disclosing to its end users how their data will be used.
c. Ensuring there is a lawful basis for each processing operation under the Omani Personal Data Protection Law issued by Royal Decree 6/2022.
16. Article Sixteen — Changes to the Terms and Notification
16-1. Right to amend: the Company reserves the right to amend these Terms at any time as business needs or legal requirements dictate.
16-2. How changes are notified:
a. Material changes: the Company notifies the Client of any material change at least [30] days before it takes effect, through:
• The email address registered to the account.
• A prominent visible notice in the control panel.
b. Non-material changes: (such as correcting language errors and clarifications that do not change substantive rights) take effect on publication, with the last-updated date noted.
c. Version in force: the version of the Terms in force is always the version published at lerix.dev/terms at the time of reference.
16-3. Implied acceptance of changes: the Client's continued use of the platform after changes take effect counts as implied acceptance of them. If the Client rejects the changes, it may terminate its subscription under Article Nine.
17. Article Seventeen — General Provisions
17-1. Entire agreement: these Terms, together with the privacy policy, the refund and cancellation policy, the data processing agreement and the service level document (if any), constitute the entire agreement between the Parties concerning use of the platform, and supersede any prior agreements or understandings on the same subject.
17-2. Severability: if any clause of these Terms is held unlawful, ineffective or unenforceable, that clause is severed from the rest and the remainder stays in full force and effect.
17-3. Assignment: the Client may not assign this contract or its rights or obligations under it to any third party without the Company's prior written consent. The Company may assign this contract to any affiliate or successor by merger or acquisition, on notice to the Client.
17-4. Individual variations: no email correspondence or support conversation amends these Terms unless set out in an amended document signed or formally approved by both Parties.
17-5. Waiver: a party overlooking a breach of a clause of these Terms on a particular occasion does not count as waiving its right to enforce that clause in future.
17-6. Language of the contract: the Arabic text of these Terms is the official, authoritative text for the purposes of interpretation and any dispute. Any translation into other languages is for reference only.
17-7. Notices: all formal legal notices to the Company are sent to [legal@lerix.dev] or by registered post to the Company's head office in Muscat. Notices to the Client are sent to the email address registered to its account.