Terms of service

1. Who provides Maatriks

Maatriks is provided by Riverin OÜ, an Estonian private limited company registered in the Estonian Commercial Register under code 17031097. Our registered address is Ida-Viru maakond, Lüganuse vald, Lüganuse alevik, Papli tn 5c, 43301, Estonia. You can contact us at info@maatriks.ai.

These Terms describe the conditions under which Riverin OÜ provides Maatriks to organizations and their authorized users. Maatriks is intended for business use. The organization that arranges access is the customer; its administrators and employees are authorized users. A person arranging the service for an organization must have authority to act for that organization.

The customer's written onboarding or service agreement establishes when the service begins and which terms apply. These Terms apply when incorporated into that agreement. An individually agreed provision takes precedence over a conflicting provision here. An employee's Microsoft sign-in establishes their identity and access; it does not by itself represent that the employee has signed an agreement for their employer.

2. What the service does

Maatriks connects compatible AI agents and customer applications to external services that the customer's administrators connect. Administrators manage Connections, individual access, blocked requests, organization API keys, and Usage and Admin-change records in the Console. Employees use their existing compatible agent and sign in with a Microsoft work identity.

Each Connection uses the customer's own account and key with either a preconfigured provider or another HTTPS API described by an administrator. The agent or application sends that service's own requests through Maatriks, which adds the customer's key and returns the service's response. What is actually available depends on the customer's Connections, the user's current access, the Connection's blocked requests, the permissions of the customer's key, and provider availability. New API Connections default to All active people in the organization, including people who sign in later. Administrators can choose Selected people to restrict access; existing Connections preserve their individual selections. Separately granted Development access provides a personal remote development environment.

Initial organization setup is assisted by Maatriks. The public website does not offer self-service organization registration. Features described as deferred or unavailable in the Usage docs are not included merely because they appear in a provider's own product. Microsoft sign-in does not grant access to an employee's mailbox.

3. Customer administration and account security

The customer is responsible for deciding which people may administer Maatriks, which Connections each person may use, and which requests each Connection blocks. Administrators should grant only the access needed, prefer provider keys limited to the permissions the customer needs, review access as responsibilities change, and disable users who should no longer have access.

Keep Microsoft accounts and provider accounts secure. Do not share authentication sessions, bypass access controls, or submit credentials that the customer is not authorized to use. Enter provider credentials only through the designated Connection controls. Employees do not need to receive the organization's provider keys.

Disabling a person blocks their Maatriks access but preserves configured grants and history. Reactivating the person can restore the access still configured for them. Disconnecting a Connection removes it from active use and revokes its active grants. It does not close the account at the external provider. If a provider key is compromised, the customer should also revoke or replace it at that provider.

4. External providers and charges

The customer's chosen AI agent, Microsoft identity service, and connected providers are separate services. Their own agreements, policies, account limits, and availability continue to apply. The customer must maintain any account permissions, subscriptions, and provider credit needed for its chosen services.

Requests made through a Connection by an employee's agent, an organization API key, or a Development project may create charges on the customer's account with that service. Granting access is separate from making a request. A successful Connection check does not guarantee available quota or that later requests will succeed.

A failed, cancelled, timed-out, or uncertain Maatriks result does not necessarily mean that the provider performed no work or charged nothing. Check the original result and provider account before repeating a potentially paid request. Maatriks Usage records contain available usage measurements and, for preconfigured providers, cost estimates; they are not provider invoices or a guaranteed calculation of final charges.

Any fee payable to Riverin OÜ must be agreed with the customer in writing. These Terms do not establish a subscription price, automatic renewal, refund schedule, or service credit. Provider fees remain governed by the customer's arrangement with that provider.

5. Content and permitted processing

The customer and its users retain the rights they already hold in the prompts, files, and other material they supply. They must have the rights and permissions necessary to submit that material and instruct the requested processing, including any rights relating to personal data, copyrighted material, voices, and likenesses.

The customer authorizes Riverin OÜ to receive, process, temporarily store, transmit, and return the submitted material to the extent necessary to provide the requested Maatriks operation, protect the service, and meet applicable legal obligations. This permission includes sending the required material to the provider selected through the customer's configured Connection. It does not give Riverin OÜ ownership of the customer's material.

Rights in generated output may depend on applicable law and the selected provider's terms. Maatriks does not promise that output is unique, protectable by intellectual property rights, or free from third-party rights. The customer remains responsible for deciding whether and how it may use or publish output.

6. Responsible use

Use Maatriks lawfully and within the permissions granted by the customer. Do not:

• attempt to access another person's or organization's credentials, files, or records;

• circumvent identity checks, access grants, blocked-request rules, quotas, or other security controls;

• submit malicious files, interfere with service operation, or attempt unauthorized probing;

• use content, voices, likenesses, or provider accounts without the necessary rights;

• use the service for unlawful deception, impersonation, or other unlawful activity; or

• present generated material as verified fact or authorized human speech when that would mislead another person or violate applicable law.

Maatriks checks identity, access, and blocked-request rules for each request made through a Connection. It does not review what a permitted request asks the connected service to do. The customer remains responsible for the permissions of the keys it connects and the rules it sets.

7. Reviewing AI output

AI-generated text, images, audio, and video can contain errors, misleading information, or unsuitable material. Review output before relying on it, sending it to others, or using it in decisions that affect people. The appropriate level of review depends on the consequences of an error and the customer's obligations.

The customer's agent decides how to orchestrate its workflow and which requests to send. Maatriks checks authorization for each request; that does not make the agent's wider workflow or every generated answer correct.

8. Content passing through Maatriks

Maatriks relays requests and responses between the user's agent or application and the connected service without storing their bodies, uploaded files, or generated media. Save any output the customer needs in the agent's environment or the customer's own systems. Files and links kept by a connected service follow that service's terms.

Connection tokens issued to an employee's agent expire 15 minutes after they are issued and work only for that person and one Connection. Removing the person's access or ending their Maatriks session stops the token working before it expires.

Usage and Admin-change evidence, including the caller, Connection, method, a redacted endpoint, status, size, timing, and cost estimates for preconfigured providers, is retained separately from the work content, normally for 365 days under the current service configuration. Access disablement, disconnection, and expiry do not imply immediate erasure of every related record or backup. See the Privacy policy for the distinctions and the Usage docs for working limits and recovery steps.

9. Availability and changes

Availability depends on Maatriks, Microsoft identity, the customer's network and agent, and any connected external service. A Connection may be unavailable because of changed access, blocked requests, provider restrictions, retired models, insufficient quota, or service failures.

Riverin OÜ may maintain, correct, or update the service and its preconfigured providers. Where a planned change materially affects an agreed service, we will communicate the change to the customer's designated contact with reasonable notice when practicable. Urgent security or legal changes may require faster action. Any particular availability commitment or support response time must be agreed separately in writing.

10. Suspension and ending service

Riverin OÜ may restrict access where reasonably necessary to address a security risk, unlawful use, a material breach of the applicable agreement, or a binding legal requirement. Where practicable, we will explain the reason to the customer and give an opportunity to resolve it. Immediate action may be needed to prevent harm.

The customer's written agreement governs the service term and ordinary termination. Customers may contact us to arrange an end to service. Before access ends, save anything needed from Development projects. Ending Maatriks access does not cancel third-party subscriptions or recover charges already incurred with providers.

11. Privacy and customer data

The Privacy policy explains the data processed through the website and service, the role of administrators and providers, and relevant retention periods. Where Riverin OÜ processes personal data on the customer's instructions, the parties must put an applicable data processing agreement in place. These Terms and the public Privacy policy do not replace that agreement.

12. Responsibility and mandatory rights

Each party is responsible for its obligations under the applicable agreement and law. Descriptions of provider dependency, output uncertainty, and pass-through processing explain the service's practical limits; they do not exclude obligations or remedies that the law does not permit the parties to exclude.

These Terms do not set a financial liability cap, impose an indemnity, or waive statutory rights. Any separately negotiated limitation must comply with applicable law. Nothing here excludes liability that cannot lawfully be excluded or restricted.

13. Applicable law and disputes

These Terms are governed by the law of Estonia. The parties should first try to resolve a dispute by contacting each other through their designated business contacts. Disputes that cannot be resolved will be determined by the competent Estonian courts, subject to any mandatory jurisdiction rules and any valid individually agreed provision. Nothing in this clause removes protections that applicable mandatory law preserves.

14. Changes and contact

The date at the beginning of this page identifies this version. A revised webpage does not retrospectively change an existing agreement. Material contractual changes will be communicated and take effect through the mechanism agreed with the customer.

For questions about these Terms, contact Riverin OÜ at info@maatriks.ai or at the registered address above.