Introduction

Revolutionizing Turbomachinery Predictive Analytics

Welcome to Turbomechanica, where cutting-edge technology meets unparalleled innovation in Predictive Analytics. Turbomechanica is not just a product; it's a testament to our commitment to excellence and continuous improvement.

Imagine a world where complex engineering challenges are tackled with ease, where data-driven insights pave the way for unprecedented efficiency, and where reliability and performance are not just goals but guarantees. That's the world we're creating with Turbomechanica.

We're committed to continuous innovation, with ongoing developments in diagnostics, simulation, and dynamic rule management. With Turbomechanica, you're not just getting a product; you're getting a promise—a promise of reliability, efficiency, and unparalleled support every step of the way.

Join us in revolutionizing Predictive Analytics with Turbomechanica.

Data Ingestion

Turbomechanica facilitates data ingestion through the following two methods:

1. Pull Mechanism:

   With this approach, Turbomechanica actively retrieves data from external sources for a specific period as needed. For instance, it might pull data from various sources such as databases or APIs based on a scheduled interval or upon request. This method allows Turbomechanica to fetch data on-demand, optimizing resource usage and ensuring real-time or near-real-time data availability.

2. Push Mechanism:

   In contrast, Turbomechanica's servers passively receive data pushed by external systems, such as a facility data warehouse, at predefined intervals. For example, the facility data warehouse might push data to Turbomechanica servers periodically, such as every hour or once a day. This method simplifies integration with systems that generate data continuously or periodically, ensuring that Turbomechanica stays updated with the latest information without the need for frequent polling.

Push Mechanism

Turbomechanica's servers passively receive data pushed by external systems, such as a facility data warehouse, at predefined intervals. For example, the facility data warehouse might push data to Turbomechanica servers periodically, such as every hour or once a day. This method simplifies integration with systems that generate data continuously or periodically, ensuring that Turbomechanica stays updated with the latest information without the need for frequent polling.

The primary methods for pushing data include:

1. Uploading CSV files using HTTPS.
2. Uploading JSON files using HTTPS.
3. Streaming data to Azure Event Hub.

Batch Requests

This document provides an overview of the Batch Request API endpoints for managing and fulfilling batch data requests.

1. Retrieve Pending Batch Requests

Endpoint

GET https://$ORG_BASE_URL/batch-requests?status=1

Description

This endpoint retrieves a list of batch requests that require fulfillment. The response includes batch requests currently marked as PENDING.

Response Format

[
  {
    "request_id": "b0b48ae3-bfe8-480e-a9ca-424b9b4e0662",
    "start_time": "2024-04-18T11:40:27.874Z",
    "end_time": "2024-04-18T13:50:27.874Z",
    "status": "PENDING"
  },
  {
    "request_id": "532a5e22-da28-4b4e-8b7d-6d81f0f47079",
    "start_time": "2024-04-18T11:40:27.874Z",
    "end_time": "2024-04-18T14:50:27.874Z",
    "status": "PENDING"
  }
]

Success Response

Status Code: 200 OK

Error Responses

• 401 Unauthorized: Authentication credentials are missing or invalid.
• 500 Internal Server Error: An unexpected error occurred.

Example Usage (Using curl)

curl --location "https://$ORG_BASE_URL/batch-requests?status=1" \
--header "Authorization: Bearer <YOUR_ACCESS_TOKEN>"

2. Update Batch Request Status

Endpoint

PATCH https://$ORG_BASE_URL/batch-requests/{request_id}

Description

This endpoint allows updating the status of a batch request.

Request Body Format

{
  "status": "IN_PROGRESS"
}

Status Options

• PENDING - The batch request has not yet been picked up.
• IN_PROGRESS - The batch request is currently being processed.
• COMPLETED - The batch request has been successfully fulfilled.
• FAILED - The batch request could not be completed.

Success Response

Status Code: 200 OK

{
  "request_id": "532a5e22-da28-4b4e-8b7d-6d81f0f47079",
  "start_time": "2024-04-18T11:40:27.874Z",
  "end_time": "2024-04-18T13:50:27.874Z",
  "status": "IN_PROGRESS"
}

Error Responses

• 400 Bad Request: The provided status is invalid.
• 404 Not Found: The specified batch request does not exist.
• 401 Unauthorized: Authentication credentials are missing or invalid.
• 500 Internal Server Error: An unexpected error occurred.

Example Usage (Using curl)

curl --location --request PATCH "https://$ORG_BASE_URL/batch-requests/532a5e22-da28-4b4e-8b7d-6d81f0f47079" \
--header "Content-Type: application/json" \
--header "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
--data '{ "status": "IN_PROGRESS" }'

Authentication & Security

• All API requests must include a valid authentication token in the Authorization header.
• Unauthorized requests will return a 401 Unauthorized response.
• API keys or tokens should be securely stored and never exposed publicly.

Notes

• Clients must ensure that a batch request is processed only once to prevent duplicate processing. This can be managed by promptly updating the batch request status to IN_PROGRESS after claiming it.
• All FAILED requests will automatically revert to PENDING after a predefined backoff period, handled by the backfill pipeline.
• The system employs a late acknowledgment strategy by default. Any IN_PROGRESS requests will be automatically reset to PENDING after a specified TIME_LIMIT. This setting is configurable at the system level based on client's requirements.
• Status transitions must follow the correct sequence: PENDING → IN_PROGRESS → COMPLETED or FAILED.

Upload CSV API

This API endpoint allows uploading CSV files with specific format validation.

Endpoint

https://$ORG_BASE_URL/upload-csv (POST)

Request Body

The request body should be a multipart form data containing a single file named "file". Only CSV files are accepted.

Content-Type: multipart/form-data

Form Body Example:

"file": (file object)
"start_time": Date
"end_time": Date
"request_id": Optional[String]

Expected CSV Format

The uploaded CSV file should have the following format:

Code snippet

UTC,Sensor_1,Sensor_2,Sensor_3
2024-04-18T11:40:27.874Z,22.54,45,OFF
2024-04-18T11:55:27.874Z,22.54,45,ON

Maximum File Size

The maximum allowed file size is 30 MB. Files exceeding this limit will be rejected.

Response

Success Response:

JSON

{
  "message": "CSV file uploaded successfully."
}

Error Response:

In case of any errors during upload or validation, an error response with a detailed message will be returned. The error code will depend on the specific error:

• 401 (Unauthorized): Invalid Auth Token
• 400 (Bad Request): Invalid file format (not CSV), invalid data type in CSV, or other validation errors.
• 413 (Payload Too Large): File size exceeds the maximum limit.

Example Usage (using curl):

Bash

curl --location https://$ORG_BASE_URL/upload-csv \
--header 'Authorization: Bearer ••••••' \
--form 'file=@"/path/to/file"' \
--form 'start_time="2024-02-02T13:30:00.000Z"' \
--form 'end_time="2024-02-02T13:31:00.000Z"' \
--form 'request_id="slug"'

Replace your_file.csv with the path to your CSV file and $ORG_BASE_URL with the URL given by the Administrator.

Depending on the type of authentication used, additional headers may be necessary for the provided API.

Upload JSON Data API

This API endpoint allows uploading data in JSON format with specific schema validation.

Endpoint

https://$ORG_BASE_URL/upload-json (POST)

Limitations

• Maximum payload size: 30MB

Expected JSON Format:

{

    "start_time": Date,
    "end_time": Date,
    "request_id": Optional[String],
    "data": {
        "Sensor_Id | Sensor_Name": [
            {
                "timestamp": Date,
                "value": Float | String | Boolean
            },
            ...
        ],
        ...
    }
}

Request Body

The request body should be valid JSON data conforming to the following schema:

JSON

{
  "start_time": "2024-04-18T11:40:27.874Z",
  "end_time": "2024-04-18T11:40:57.874Z",
  "request_id": "slug",
  "data": {
    "Sensor_1": [
      {
        "timestamp": "2024-04-18T11:40:27.874Z",
        "value": 22.234
      },
      {
        "timestamp": "2024-04-18T11:40:42.874Z",
        "value": 498575.234
      },
      {
        "timestamp": "2024-04-18T11:40:57.874Z",
        "value": "ON"
      }
    ],
    "Sensor_2": [
      {
        "timestamp": "2024-04-18T11:40:27.874Z",
        "value": 44.543
      },
      {
        "timestamp": "2024-04-18T11:40:42.874Z",
        "value": 537955.235
      },
      {
        "timestamp": "2024-04-18T11:40:57.874Z",
        "value": "OFF"
      }
    ]
  }
}

Response

Success Response:

JSON

{
  "message": "Data uploaded successfully."
}

Error Response:

In case of any errors during upload or data parsing, an error response with a detailed message will be returned. The error code will depend on the specific error:

• 401 (Unauthorized): Invalid Auth Token
• 413 (Payload Too Large): Request payload exceeds the 30MB limit
• 422 (Unprocessable Content): Invalid JSON data or schema validation error.

Example Usage (using curl):

Bash

curl --location https://$ORG_BASE_URL/upload-json \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer ••••••' \
--data '{
  "start_time": "2024-04-18T11:40:27.874Z",
  "end_time": "2024-04-18T11:40:57.874Z",
  "request_id": "slug",
  "data": {
    "Sensor_1": [
      {
        "timestamp": "2024-04-18T11:40:27.874Z",
        "value": 22.234
      },
      {
        "timestamp": "2024-04-18T11:40:42.874Z",
        "value": 498575.234
      },
      {
        "timestamp": "2024-04-18T11:40:57.874Z",
        "value": "ON"
      }
    ],
  }
}'

Replace $ORG_BASE_URL with the URL given by the Administrator.

Depending on the type of authentication used, additional headers may be necessary for the provided API.

Stream Data to Azure Event Hub

We provide an Azure Event Hub endpoint for secure, unidirectional data ingestion. Your systems initiate outbound connections using AMQP over TLS or HTTPS and push events using send-only credentials. We cannot access your network or initiate inbound connections.

1. Sending Data

Fetch records from your data source, format them to the required schema, and send them to our Event Hub using your provided credentials.

Follow Microsoft's official guide: Send events using Python (Similar guides exist for .NET, Java, Node.js etc)

Required Fields

Regardless of the delivery method, each data record should contain the following three fields as a minimum:

• sensor_id / tag_id – a unique identifier for each tag or sensor from your upstream system.
• timestamp – the date and time the sensor reading was taken, in a consistent format of your choice in UTC timezone.
• value – the numeric measurement recorded at that timestamp. It could also be an alphanumeric or string value if needed (e.g. we sometimes get “Running” and “Stopped” as string values).

Example Payload

{
  "sensor_id": "compressor-7:vibe_x",
  "timestamp": "2025-08-19T08:30:00Z",
  "value": 42.1
}

2. Authentication

SAS Connection String (Recommended)

This is the simplest and fastest way to connect. We provide you with a SAS connection string of the form:

Endpoint=sb://{namespace}.servicebus.windows.net/;
SharedAccessKeyName=send-only;
SharedAccessKey=...;
EntityPath={event_hub_name}

• Works with all official Azure SDKs and REST
• Minimal setup required
• Recommended for almost all integrations

Python Example (SAS):

from azure.eventhub import EventHubProducerClient, EventData

connection_str = "Endpoint=sb://{namespace}.servicebus.windows.net/;SharedAccessKeyName=send-only;SharedAccessKey=...;EntityPath={event_hub_name}"
eventhub_name = "{event_hub_name}"

producer = EventHubProducerClient.from_connection_string(
    conn_str=connection_str,
    eventhub_name=eventhub_name
)

with producer:
    batch = producer.create_batch()
    batch.add(EventData('{"sensor_id":"s1","timestamp":"2025-08-19T08:30:00Z","value":42.1}'))
    producer.send_batch(batch)

Entra ID

For clients that require Azure Active Directory token-based authentication, we can provide an Entra ID (service principal) with the Azure Event Hubs Data Sender role.

We will share:

• TENANT_ID (our Azure AD tenant)
• CLIENT_ID (App Registration ID)
• CLIENT_SECRET (secret/password for the service principal)

Python Example (Entra ID):

from azure.identity import ClientSecretCredential
from azure.eventhub import EventHubProducerClient, EventData

tenant_id = "<TENANT_ID>"
client_id = "<CLIENT_ID>"
client_secret = "<CLIENT_SECRET>"

credential = ClientSecretCredential(tenant_id, client_id, client_secret)

producer = EventHubProducerClient(
    fully_qualified_namespace="{namespace}.servicebus.windows.net",
    eventhub_name="{event_hub_name}",
    credential=credential
)

with producer:
    batch = producer.create_batch()
    batch.add(EventData('{"sensor_id":"s1","timestamp":"2025-08-19T08:30:00Z","value":42.1}'))
    producer.send_batch(batch)

3. FAQ

• Which option should I use? Use the SAS connection string unless your security policies require Entra ID.
• How large can a message be? Default up to 1 MB per event.
• Is this push or pull? You push data into our Event Hub. We consume it. One-way only.
• Detailed FAQ documentation Azure Event Hubs FAQ

Pull Mechanism

The implementation of the pull mechanism varies depending on the policies of individual facilities and their preferred methods for storing information. We generally lean towards the pull approach over push, as it offers greater control, particularly in back-fill scenarios.

We securely fetch data from your Web API endpoint, normalize it into our internal format ({sensor_id, timestamp, value} for timeseries), and ingest it into our data pipeline.

What We Need From You

1. Base API URL

   Example: https://your-api.com/api/v1/data

2. Authentication Details

   • API key, token, OAuth credentials, or Basic Auth
   • Any required headers

3. Endpoint(s) to Hit

   • List of endpoints with example payloads
   • Documentation or OpenAPI (Swagger) spec if available

4. Query Parameters / Payload Specs

   • Required parameters (e.g., start_time, end_time, sensor_id)
   • Pagination method (e.g., cursor, page/limit, link-based)

5. Frequency & Range

   • How often we should poll or pull data
   • Historical backfill duration (e.g., past 7 days, full dump)

Supported Features

• Support for GET/POST-based APIs
• Token, API Key, and OAuth authentication
• Pagination handling (token-based, link-based, offset)
• JSON/CSV/XML payload parsing
• Time-based filtering and delta fetches

Integrations

Turbomechanica facilitates a wide range of integrations, enabling events and alerts generated within the system to be exported to other platforms. Additionally, it supports functionalities such as raising service requests, managing work orders, and much more.

Currently supported integrations:

1. Service Requests Management using Maximo

Sending Alerts to External CMMS

Overview

This document outlines how Turbomechanica forwards alerts to an external CMMS system and how updates to service requests (SR) can be handled when changes occur on the CMMS side.

1. Sending an Alert to CMMS

When an alert is triggered in our system, it can be forwarded to the external CMMS system as a service request.

Request Payload

The API sends the following JSON payload when an alert is forwarded:

Required Fields:

• ALERT_ID (string): Unique identifier for the alert triggering the service request.
• FACILITY_ID (string): Facility ID associated with the service request.
• USER_EMAIL (string): Email address of the user reporting the issue.
• ALERT_LEVEL (string): Severity level of the alert (e.g., Critical, High, Medium, Low).
• ALERT_IDENTIFIER (string): Unique identifier related to the specific alert type.
• CUSTOMER_ASSET_ID (string): Unique identifier of the customer asset requiring service.
• SR_REQUEST_DATE (string, UTC format): Date and time the service request is submitted.
• ALERT_INSIGHT (string): Additional details or insights related to the alert.
• MECHADEMY_URL (string): Link to Alert on Turbomechanica platform.

Example Request

{
  "ALERT_ID": "ABC123",
  "FACILITY_ID": "FAC001",
  "USER_EMAIL": "user@example.com",
  "ALERT_LEVEL": "Critical",
  "ALERT_IDENTIFIER": "SENSOR_FAILURE",
  "ALERT_INSIGHT": "Sensor XYZ reports abnormal readings.",
  "CUSTOMER_ASSET_ID": "ASSET-1234",
  "SR_REQUEST_DATE": "2024-04-19T10:00:00.000Z",
  "MECHADEMY_URL": "https://next.turbomechanica.ai/facility/1/equipment/5/events/3"
}

Expected Response

Upon successfully creating a service request, the external system will return a response confirming the request status.

Success Response

{
  "ALERT_ID": "ABC123",
  "ORG_ID": "12345",
  "SR_TICKET_ID": "SR-98765",
  "STATUS": "Success"
}

Response Fields:

• ALERT_ID: The original alert identifier provided in the request.
• ORG_ID: The organization ID associated with the service request. (Optional)
• SR_TICKET_ID: The unique ID of the created service ticket. (Optional)
• STATUS: "Success" indicating successful service request creation.

  Valid Values for STATUS:

  • Success: Indicates the service request was successfully created.
  • Failure: Indicates the service request creation failed.
  • Queued: Indicates the service request is queued for processing.

Failure Response

{
  "ALERT_ID": "ABC123",
  "STATUS": "Failure",
  "STATUS_REASON": "Invalid customer asset ID"
}

Response Fields:

• ALERT_ID: The original alert identifier provided in the request.
• STATUS: "Failure" indicating unsuccessful service request creation.
• STATUS_REASON: A descriptive message explaining the reason for failure.

2. Updating an Alert When SR is Updated in CMMS

When the service request is updated on the external system, our system must be notified to update the corresponding alert.

Update Request Payload

The update request allows modification of various SR fields:

{
  "SR_TICKET_ID": "SR-98765",  // Optional
  "SRSTATUS": "IN_PROGRESS",
  "SRFINISHDATE": "2024-04-20T15:30:00.000Z",
  "WORKLOGS": [
    {
      "LOGID": "LOG001",
      "LOGCREATEDDATE": "2024-04-19T11:00:00.000Z",
      "LOGDESCRIPTION": "Technician assigned.",
      "LOGLONGDESCRIPTION": "Technician John Doe has been assigned to inspect the sensor issue."
    }
  ],
  "SROWNER": "JohnDoe",
  "SRREPORTEDPRIORITY": 2,
  "WONUMBER": "WO-56789",
  "WODESCRIPTION": "Replace faulty sensor"
}

Valid Values for SRSTATUS

• FAILED: Indicates that the service request update has failed.
• ACKNOWLEDGED: Indicates that the service request has been acknowledged by the responsible party.
• RESOLVED: Indicates that the service request has been resolved.
• IN_PROGRESS: Indicates that the service request is currently being worked on.
• DISCARDED: Indicates that the service request has been discarded and will not be processed further.
• QUEUED: Indicates that the service request update is queued for processing.

Update API Endpoints

Update Using SR ID

PATCH https://$ORG_BASE_URL/service-requests/external/{external_sr_ticket_id}

Update Using ALERT ID

PATCH https://$ORG_BASE_URL/service-requests/external/alert/{alert_id}

Authentication

The API requires authentication using either of the following methods:

• AuthBearer
• JWTAuth

Response Schema

The API returns a response confirming whether the update was successful or failed.

Success Response

{
  "id": 0,
  "alert": 0,
  "name": "string",
  "description": "string",
  "external_id": "string",
  "status": 0,
  "created_at": "2025-02-24T06:41:08.194Z",
  "acknowledged_at": "2025-02-24T06:41:08.194Z",
  "dispatched_at": "2025-02-24T06:41:08.194Z",
  "resolved_at": "2025-02-24T06:41:08.194Z",
  "logs": {},
  "work_orders": {},
  "updated_at": "2025-02-24T06:41:08.194Z",
  "asset_id": "string",
  "insights": "string",
  "level": 0,
  "owner": "string"
}

Failure Response (Alert Not Found)

{
  "detail": "Not Found"
}

A 404 Not Found response is returned if no alert is found for the given external_sr_ticket_id or alert_id, following the standard Django Ninja response pattern.

Authentication & Security

• All API requests must include a valid authentication token in the Authorization header.
• Unauthorized requests will return a 401 Unauthorized response.
• API keys or tokens should be securely stored and never exposed publicly.

Authentication using External IdP

Turbomechanica supports external Identity Providers (IdPs) which allows integration with existing systems responsible for managing user identities and access permissions. Instead of maintaining its own authentication system, Turbomechanica can leverage external IdPs such as OAuth providers (like Google, Facebook, or Microsoft) or corporate identity management solutions (like Active Directory or LDAP).

Currently supported external IdP:

1. Okta as SAML Identity Provider
2. Okta Workforce

Additionally, through Auth0, we support various other providers such as OIDC, LDAP, and Microsoft AD.

Okta as SAML Identity Provider

1. Setup App Integration in Okta

1.1. Prerequisites

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Integrations > Click on info icon on the top right corner > Select integration type as Okta Saml

3. Note the identity provider Single Sign-On URL and Audience URI (SP Entity ID) ; these will be used in later steps to create app integration.

1.2. Create App Integration

1. Log in to the Okta Developer Console, go to Okta Admin Dashboard.

2. Go to Applications > Applications > Create App Integration and choose SAML 2.0 from the options.

3. Click Next.

4. Provide the general information for the integration and then click Next.

5. Provide the necessary SAML settings information for your integration. (See Application Integration Wizard SAML field reference for descriptions of individual fields.)

• Configure the following settings:

Select Use this for Recipient URL and Destination URL

6. In Attribute Statements section, add following attributes :

7. Optional. Click <> Preview the SAML Assertion to view the XML generated from the SAML settings that you provided.

8. Click Next.

9. Provide configuration information about your app integration to Okta:

• Select I'm an Okta customer adding an internal app.
• Select This is an internal app that we have created.

10. Click Finish. Your integration is now created in your Okta account.

11. After you create your SAML app integration, the SAML Signing Certificates section appears on the Sign On tab.

12. Go to Sign On tab, in Saml 2.0 section click on more details and note the Identity Provider Single Sign-On URL, click on Download to obtain a copy of the currently active X.509 certificate.

2. Setup SAML Integration in Turbomechanica.

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Integrations > Click on Add Integration on the top right corner.

3. Follow the steps and provide the following mandatory configuration settings for this connection:

4. Click Save. Your integration is completed. Well Done !

3. Test the Integration

1. To test the user login process, create a test user with your company's email domain (email domain should match with value added in Domain Aliases in above section) in your Okta account.

• Log in to the Okta Developer Console, go to Okta Admin Dashboard.
• Go to Directory > People
• Click the Add Person button.
• Fill in User Details
• Activate User

2. Assign test user with permissions to access the newly created app.

3. Go to your Turbomechanica domain. This time, try logging in with Okta credentials for test user and you should be redirected to OKTA SSO page for login.

Note: If you face any issues regarding redirection, make sure to check your email address domain matches with Domain Alias field added in previous steps.

4. Assign Users to App

1. Log in to the Okta Developer Console, go to Okta Admin Dashboard.

2. Go to Applications > Applications > Click Assign Users to App.

3. Select the app created in the above steps and assign it to people or groups.

4. Click Next and Confirm Assignments.

Request Template

<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
@@AssertServiceURLAndDestination@@
    ID="@@ID@@"
    IssueInstant="@@IssueInstant@@"
    ProtocolBinding="@@ProtocolBinding@@" Version="2.0">
    <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">@@Issuer@@</saml:Issuer>
</samlp:AuthnRequest>

IdP-initiated SSO

Reference: Configure Okta as SAML Identity Provider

Okta Workforce Identity Provider

1. Setup App Integration in Okta

1.1. Prerequisites

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Integrations > Click on info icon on the top right corner > Select integration type as Okta Workforce.

3. Note the identity provider Sign-in Redirect URI ; this will be used in later steps to create app integration.

1.2. Create App Integration

1. Log in to the Okta Developer Console, go to Okta Admin Dashboard.

2. Go to Applications > Applications > Create App Integration and choose OIDC - OpenID Connect from the options.

3. Choose the type Web Application and then click Next.

4. Provide the necessary settings information for your integration. (See Application Integration Wizard OIDC field reference for descriptions of individual fields.)

• Configure the following settings:

5. In Assignments section, select Skip group assignment for now and click Save.

6. After you create your OIDC app integration, client credentials and client secrets appear on the General Tab.

7. Note the identity provider Client ID and Client Secret.

8. Click Finish. Your integration is now created in your Okta account.

2. Setup Okta Workforce Integration in Turbomechanica.

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Integrations > Click on Add Integration on the top right corner.

3. Follow the steps and provide the following mandatory configuration settings for this connection:

4. Click Save. Your integration is now complete. Well Done !

3. Test the Integration

1. To test the user login process, create a test user with your company's email domain (email domain should match with value added in Domain Aliases in above section) in your Okta account.

• Log in to the Okta Developer Console, go to Okta Admin Dashboard.
• Go to Directory > People
• Click the Add Person button.
• Fill in User Details
• Activate User

2. Assign test user with permissions to access the newly created app.

3. Go to your Turbomechanica domain. This time, try logging in with Okta credentials for test user and you should be redirected to OKTA SSO page for login.

Note: If you face any issues regarding redirection, make sure to check your email address domain matches with Domain Alias field added in previous steps.

4. Assign Users to App

1. Log in to the Okta Developer Console, go to Okta Admin Dashboard.

2. Go to Applications > Applications > Click Assign Users to App.

3. Select the app created in the above steps and assign it to people or groups.

4. Click Next and Confirm Assignments.

IdP-initiated SSO

Reference: Configure Okta Workforce

Microsoft Azure Active Directory Identity Provider

1. Setup App Integration in Azure AD

1.1. Prerequisites

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Organization > Integrations > Click on info icon on the top right corner > Select integration type as Azure AD.

3. Note the identity provider Sign-in Redirect URI ; this will be used in later steps to create app integration.

1.2. Create App Integration

1. Log in to the Azure AD Portal.

2. In the left panel click on Manage > Click the App Registrations button in the side menu.

3. In Azure AD App Registrations, create a New Registration.

4. Enter the name Turbomechanica for your application.

5. Select Accounts in this organizational directory only - Single Tenant.

6. Under Redirect URI field, select Web and add following value as mentioned in Step 7.

7. Follow the steps and provide the following mandatory configuration settings for this connection:

8. Click “Register”.

9. You should now see the newly created app on Overview screen. Copy the Application Application (client) ID from the overview screen of your newly created app registration, we'll need this later.

1.3. Create The Client Secret In Azure AD

1. In the left panel click on Manage > Select the “Certificates & Secrets” area from the App registration side menu.

2. Click the “New client secret” button in the “Client secrets” section.

3. You should now see the Client Secret creation dialog. Enter the name for the description, select expiry as per your security preference.

4. Click the “Add” button.

5. Copy the Application Client Secret value, we'll need this later. (Client secret values cannot be viewed, except for immediately after creation. Be sure to save the secret when created before leaving the page.)

6. You should now see the new client secret listed in the “Client Secrets” section.

1.4. Configure API Permissions

1. On overview screen of newly created App, on the left panel under Manage tab > click on the API permissions.

2. On API permissions screen, click on Add a permission.

3. On the Microsoft APIs, click on the Microsoft Graph.

4. Click on Delegated permissions.

5. In the search text field under the “Select Permissions” heading enter the text "Directory.Read.All'. Tick the checkbox next to the “Directory.Read.All” permission.

6. Click the “Add Permissions” button.

7. You should now see Directory.Read.All and User.Read permissions under Microsoft Graph.

2. Setup Azure AD Integration in Turbomechanica.

1. Login to your Turbomechanica account with user email provided by Mechademy.

2. On the Turbomechanica dashboard, in the left panel click on Settings Icon > Organization > Integrations > Click on Add Integration on the top right corner.

3. Add Integration Name as 'AzureAD', select Integration Type as 'Azure AD' and click Next.

4. Follow the steps and provide the following mandatory configuration settings for this connection:

4. Click Save. Your integration is now complete. Well Done !

3. Test the Integration

1. To test the user login process, create a test user with your company's email domain (email domain should match with value added in Domain Aliases in above section) in your Microsoft Azure AD account.

2. Assign test user with permissions to access the newly created app.

3. Go to your Turbomechanica domain. This time, try logging in with Azure AD credentials for test user and you should be redirected to Azure AD SSO page for login.

Note: If you face any issues regarding redirection, make sure to check your email address domain matches with Domain Alias field added in previous steps.

IdP-initiated SSO

Reference: Configure Microsoft Azure Active Directory Identity Provider

TURBOMECHANICA TERMS OF SERVICE

Last Updated: February 24, 2025

NOTICE:

THIS IS A LEGALLY BINDING AGREEMENT BETWEEN THE RECIPIENT OF THE PRODUCTS (THE "CUSTOMER") AND MECHADEMY INCORPORATED ("MECHADEMY").

PLEASE REVIEW THESE TERMS BEFORE USING OUR SERVICES, AS THEY MAY HAVE CHANGED SINCE YOUR LAST VISIT TO THIS SITE.

MECHADEMY PROVIDES THE PRODUCTS ON THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT AND ON THE CONDITION THAT CUSTOMER ACCEPTS AND COMPLIES WITH THESE TERMS AND CONDITIONS.

IF YOU SIGN THE AGREEMENT AND/OR CLICK THE "I ACCEPT" BUTTON AND/OR USE ANY PRODUCT YOU ARE LEGALLY BOUND BY THE BELOW TERMS AND CONDITIONS.

IF YOU DO NOT AGREE WITH THE TERMS OF THIS AGREEMENT, DO NOT CLICK "I AGREE" AND DO NOT USE ANY PRODUCT.

TURBOMECHANICA GENERAL TERMS AND CONDITIONS

MECHADEMY refers to Mechademy Incorporated - an engineering consulting firm bringing together globally renowned turbomachinery subject matter experts to provide the oil and gas industry with engineering consulting services, commissioning and start-up services as well as remote monitoring and troubleshooting services.

1. DEFINITIONS

“ADDENDA” means two or more ADDENDUM.

“ADDENDUM” means any schedule, terms, conditions, policies, declarations, tables, lists, or document/s appended to the AGREEMENT and shall be deemed to form an integral part of the AGREEMENT.

“AFFILIATES” means any entity that, directly or indirectly, CONTROLS or is CONTROLLED by any PARTY or is under common CONTROL of any PARTY.

“AGREEMENT” means collectively (i) these TURBOMECHANICA GENERAL TERMS AND CONDITIONS, (ii) TURBOMECHANICA PRIVACY POLICY, (iii) DATA PROCESSING ADDENDUM, and (iv) each PURCHASE AGREEMENT executed by the PARTIES and entered into in accordance with these TURBOMECHANICA GENERAL TERMS AND CONDITIONS.

“CLOUD SERVICES” mean the web/cloud-based data management platform and software, developed by MECHADEMY and offered to the CUSTOMER under the terms of this AGREEMENT.

“CONTROL, CONTROLS or CONTROLLED” means the power to direct or influence the management, functioning, or policy building of an entity, through ownership interest, voting rights, contractual terms, or otherwise.

“CONFIDENTIAL INFORMATION” has the meaning set forth in Section 5.1 (CONFIDENTIAL INFORMATION).

“CUSTOMER” means the individual or organization who has contracted with MECHADEMY for the use of the PRODUCTS.

“CUSTOMER CONTENT” means all content and material provided by the CUSTOMER or its USERS or received by MECHADEMY on behalf of the CUSTOMER.

“DISCLOSING PARTY” has the meaning set forth in Section 5.1 (CONFIDENTIAL INFORMATION).

“EFFECTIVE DATE” means the calendar date on which the CUSTOMER accepts the AGREEMENT either by physical or digital signing or by accepting the terms on the TURBOMECHANICA PLATFORM.

“INTELLECTUAL PROPERTY RIGHTS” mean all property rights of human intellect including creativity concepts, inventions, industrial models, trademarks, symbols, names, brands, and other intellectual property, including without limitation all patents, copyrights, and trademarks.

“PARTIES” means collectively the CUSTOMER and MECHADEMY, and each of the CUSTOMER and MECHADEMY is a “PARTY.”

“PRODUCT(S)” means the PRODUCTS and/or Services offered by MECHADEMY on the TURBOMECHANICA PLATFORM.

“PURCHASE AGREEMENT” refers to the agreement between the PARTIES covering the purchase of PRODUCTS. The CUSTOMER may be subject to additional terms included in the PURCHASE AGREEMENT, which are hereby made an ADDENDA to this AGREEMENT.

“RECEIVING PARTY” has the meaning set forth in Section 5.1 (CONFIDENTIAL INFORMATION).

“THIRD-PARTY PRODUCTS” means any software, content, PRODUCT, or service incorporated, associated, or utilized in the PRODUCTS provided by any entity other than the PARTIES.

“TURBOMECHANICA” or “TURBOMECHANICA PLATFORM” means MECHADEMY's cloud-based big data platform designed for industrial machines and processes.

“USER” means any individual who accesses the TURBOMECHANICA PLATFORM using an authorized account with access credentials provided by MECHADEMY.

2. GENERAL PROVISIONS AND USE OF PRODUCTS

2.1. By accepting the AGREEMENT or using the PRODUCTS, the CUSTOMER:

• Represents and warrants to have read this AGREEMENT and agrees that the CUSTOMER is legally bound by its terms and conditions.
• If the CUSTOMER is a business organization, the person accepting the AGREEMENT has the authority to bind the organization.

2.3. Right to Use: MECHADEMY grants the CUSTOMER a non-exclusive, non-transferable, limited right to use the PRODUCTS as specified in the PURCHASE AGREEMENT, subject to compliance with all contractual obligations.

2.4. Evaluation of PRODUCTS and Free PRODUCTS: For evaluation or free trials, MECHADEMY offers no warranties, maintenance, or support services.

3. PAYMENTS AND INVOICING

3.1. Invoicing:

MECHADEMY shall provide the CUSTOMER with an invoice specifying the fees for the PRODUCTS in accordance with the invoicing schedule set forth in the PURCHASE AGREEMENT.

3.2. Payment:

The CUSTOMER shall pay MECHADEMY for all invoices in accordance with the payment schedule set forth in the PURCHASE AGREEMENT.

3.3. Taxes:

Unless otherwise agreed to in the PURCHASE AGREEMENT, the CUSTOMER will pay all applicable sales, value-added, or other similar taxes imposed on the PRODUCTS.

If MECHADEMY is required to pay any such taxes, CUSTOMER shall reimburse MECHADEMY for such amounts.

If CUSTOMER is required by law to make any tax withholding from amounts paid or payable to MECHADEMY under the AGREEMENT:

• The amount paid or payable shall be increased to ensure MECHADEMY receives a net amount equal to what it would have received without any tax withholding.
• The CUSTOMER shall provide proof of such withholding to MECHADEMY.

3.4. Non-Refundable Fees:

CUSTOMER accepts and agrees that one-time fees for setup, installation, software purchase, deployment, site visits, etc., will be non-cancellable and non-refundable, unless otherwise expressly stated in the PURCHASE AGREEMENT.

4. INTELLECTUAL PROPERTY RIGHTS

4.1. MECHADEMY Ownership:

MECHADEMY shall be the sole owner of the INTELLECTUAL PROPERTY RIGHTS to all processes, algorithms, designs, PRODUCTS, knowledge, insights, and derivative works related to the PRODUCT.

4.2. CUSTOMER CONTENT:

MECHADEMY shall have no ownership rights in any CUSTOMER CONTENT. The CUSTOMER grants MECHADEMY a global, royalty-free, irrevocable, nonexclusive license to use CUSTOMER CONTENT for service provision.

4.3. Non-Assertion of Rights:

The CUSTOMER agrees not to assert any claims against MECHADEMY regarding INTELLECTUAL PROPERTY RIGHTS in the PRODUCTS and DOCUMENTATION.

4.4. Suggestions and Residual Knowledge:

MECHADEMY retains the right to use any feedback from the CUSTOMER to enhance its PRODUCTS. Additionally, MECHADEMY is free to use its general knowledge, skills, and experience derived from performing the AGREEMENT.

5. CONFIDENTIALITY

5.1. CONFIDENTIAL INFORMATION:

During the term of the AGREEMENT, confidential or proprietary information may be disclosed orally or physically by either PARTY (the “DISCLOSING PARTY”) to the other PARTY (the “RECEIVING PARTY”).

“CONFIDENTIAL INFORMATION” refers to all information made available by the DISCLOSING PARTY to the RECEIVING PARTY that is either marked as confidential or is reasonably considered confidential in either PARTY’s line of business.

CONFIDENTIAL INFORMATION may include information in the form of, but not limited to, technical documentation, process methodologies, design data, concepts, product specifications, operational data, business listings, or other documents, including confidential or proprietary information of a THIRD-PARTY.

CONFIDENTIAL INFORMATION shall not include any information, which is:

• In the RECEIVING PARTY’S possession prior to its receipt from the DISCLOSING PARTY
• Independently developed by the RECEIVING PARTY without use of the CONFIDENTIAL INFORMATION,
• Acquired by the RECEIVING PARTY from a THIRD-PARTY which was not, to the RECEIVING PARTY’S knowledge, under an obligation to the DISCLOSING PARTY not to disclose such information,
• Becomes publicly available through no breach of this AGREEMENT by the RECEIVING PARTY.

5.2. Confidentiality Obligations:

Ownership of the CONFIDENTIAL INFORMATION shall be retained by the DISCLOSING PARTY or the THIRD-PARTY whose CONFIDENTIAL INFORMATION was disclosed.

RECEIVING PARTY agrees to:

• Protect the DISCLOSING PARTY’s CONFIDENTIAL INFORMATION with reasonable care and in a manner no less than that used to protect the RECEIVING PARTY’s own CONFIDENTIAL INFORMATION;
• Use the DISCLOSING PARTY’S CONFIDENTIAL INFORMATION solely for the purpose outlined in the AGREEMENT;
• Not disclose any of the DISCLOSING PARTY’S CONFIDENTIAL INFORMATION to any entity without the DISCLOSING PARTY's prior written consent;
• Disclose the DISCLOSING PARTY’S CONFIDENTIAL INFORMATION to only those AFFILIATES, employees, contractors, or agents who need to know CONFIDENTIAL INFORMATION in order to support the RECEIVING PARTY's obligations pursuant to the AGREEMENT. Such an entity must be instructed to comply with the obligations of confidentiality contained in the AGREEMENT. The RECEIVING PARTY will be responsible for any breach of this Section 5 (Confidentiality) by any such person or entity;
• Return or destroy all CONFIDENTIAL INFORMATION upon termination of the AGREEMENT or upon written request by the DISCLOSING PARTY; and
• In any event, MECHADEMY shall not be required to return or destroy any of CUSTOMER’S CONFIDENTIAL INFORMATION whose return, or destruction is impractical or technically infeasible or adversely affects the functioning of the PRODUCTS.

The confidentiality obligations stated herein will expire three (3) years after the termination or expiration of the AGREEMENT.

The RECEIVING PARTY may disclose CONFIDENTIAL INFORMATION if and as required by applicable law, or by an order of a court or governmental agency, provided the RECEIVING PARTY shall first, to the extent permitted by applicable law, notify the DISCLOSING PARTY of the requirement and offer the DISCLOSING PARTY an opportunity to seek a protective order relating to such disclosure at its expense.

The CUSTOMER hereby authorizes MECHADEMY to collect, use, disclose, and modify, in perpetuity, information or data (including, but not limited to, general usage information and measurements) that is provided by CUSTOMER in connection with the use or receipt of the PRODUCTS (or generated or created in the course of MECHADEMY providing the PRODUCTS) for the purposes of developing, improving, optimizing, and delivering PRODUCTS; provided, however, that any disclosure of such data shall only include information or data that MECHADEMY develops or derives from such collected data or information (but such disclosure will not include any CONFIDENTIAL INFORMATION of CUSTOMER).

5.3. Press Releases and Client List Reference:

Neither PARTY shall issue any press release concerning the relationship of the PARTIES or the other PARTY's work without the other PARTY's prior written consent.

Notwithstanding the foregoing, MECHADEMY may identify CUSTOMER as a client of MECHADEMY and use CUSTOMER’S name and logo and release an announcement regarding the existence of the AGREEMENT and MECHADEMY is hereby granted a license for the term of the AGREEMENT to use CUSTOMER’S name and logo for this purpose.

MECHADEMY may generally describe the nature of the work pursuant to the AGREEMENT in MECHADEMY's promotional materials, presentations, case studies, qualification statements, and proposals to other current and prospective clients.

6. DATA PROTECTION

6.1. CUSTOMER CONTENT:

The CUSTOMER is responsible for providing accurate, good-quality, reliable and legally permissible CUSTOMER CONTENT, delivered in a manner suitable for its use in the PRODUCTS.

CUSTOMER has sole responsibility for securing all rights and permissions for the performance, receipt or use of the CUSTOMER CONTENT.

MECHADEMY shall advise the CUSTOMER on the format, structure, delivery mode and periodicity of the CUSTOMER CONTENT for its use in the PRODUCTS.

6.2. Security:

MECHADEMY will maintain reasonable security standards for the use of the PRODUCTS by USERS. CUSTOMER will provide reasonable assistance in connection with the provision of the PRODUCTS and the support by MECHADEMY. CUSTOMER acknowledges and agrees that CUSTOMER’S reasonable assistance is a necessary precondition for MECHADEMY's correct performance of its obligations under the AGREEMENT.

CUSTOMER is solely responsible for determining the suitability of the PRODUCTS for CUSTOMER’S business processes and for complying with all applicable legal requirements regarding CUSTOMER CONTENT and its use of the PRODUCTS.

7. DISCLAIMER OF WARRANTIES:

MECHADEMY disclaims all warranties, representations, or statements, express or implied, except for the express representations and warranties set forth in the AGREEMENT, including the PURCHASE AGREEMENT, or any warranties implied by law that cannot be validly waived. Without limiting the foregoing, MECHADEMY disclaims any warranties of merchantability or fitness for a particular purpose.

No oral or written statement by MECHADEMY or its representatives shall in any way increase the scope of the warranties set forth in the AGREEMENT or the PURCHASE AGREEMENT.

MECHADEMY does not warrant:

• The functionality of the PRODUCTS beyond the scope of work set forth in the PURCHASE AGREEMENT;
• The compatibility of the PRODUCTS with THIRD-PARTY PRODUCTS and services other than those specified in MECHADEMY's DOCUMENTATION (as applicable);
• Uninterrupted or error-free operation of the PRODUCTS due to reasons including but not limited to transmission errors, delivery failures, delays and other limitations inherent to internet and electronic communications; or
• Risks to the CUSTOMER’S systems, software, data and equipment against security threats, internet threats or other threats or interruptions.

8. LIMITATION OF LIABILITY

8.1. No Consequential Damages:

MECHADEMY shall have no liability for any indirect, incidental, consequential, exemplary, special, punitive or similar damages arising out of or related to the AGREEMENT (including, without limitation, loss of business, profits, revenue, loss, corruption or destruction of data, business interruption, or downtime), regardless of the cause of action or basis of liability (whether in contract, tort, indemnity, or otherwise), and even if advised of the possibility of such damages.

8.2. Damages Cap:

Notwithstanding the basis of any liability (breach of contract, tort, negligence, misrepresentation, breach of statutory duty, breach of warranty or claims by THIRD PARTIES), the aggregate liability of MECHADEMY to the CUSTOMER for any loss or damage in relation to the AGREEMENT shall not exceed the fees paid by CUSTOMER pursuant to the applicable PURCHASE AGREEMENT for the specific PRODUCT giving rise to such liability in the twelve (12) month period preceding the date of the incident giving rise to the claim.

9. INFRINGEMENT CLAIMS AND INDEMNIFICATION

9.1. Infringement Claims:

In the event of any valid claim by any THIRD-PARTY that CUSTOMER’S use of the PRODUCTS in accordance with the terms and conditions of the AGREEMENT constitutes an infringement or misappropriation of a patent, copyright, or trade secret of a THIRD-PARTY, MECHADEMY shall, in its discretion:

• Modify the applicable PRODUCTS to be non-infringing, or
• Procure for CUSTOMER the right to continue using the PRODUCTS or replace or modify the PRODUCTS to be non-infringing without a material decrease in functionality, or
• Terminate the applicable portion(s) of the Purchase Order and refund any amounts prepaid by CUSTOMER.

This obligation of MECHADEMY shall not apply if the alleged infringement or misappropriation arises from:

• Use of the PRODUCTS in conjunction or combination with any other software, services, or any PRODUCT, data, item, or apparatus that MECHADEMY did not provide (including any THIRD-PARTY PRODUCTS);
• Anything CUSTOMER provides or designs including configurations, instructions, or specifications (including any PRODUCTS that were provided pursuant to CUSTOMER’S designs, drawings, or specifications);
• Modification of the PRODUCTS other than with MECHADEMY's prior written consent;
• CUSTOMER’S failure to use the latest release or version of a PRODUCT (including any corrections or enhancements) where such use would have prevented the infringement or misappropriation claim;
• Any use, storage, distribution, reproduction, or maintenance not permitted by the AGREEMENT.

If MECHADEMY believes, in its reasonable opinion, that a claim under this Section 9.1 could or is likely to be made, MECHADEMY may cease to offer or deliver such PRODUCTS and terminate any applicable PURCHASE ORDER.

The provisions of this Section 9.1 set forth the sole, exclusive, and entire liability of MECHADEMY to CUSTOMER, and comprise CUSTOMER’S sole remedy, with respect to THIRD-PARTY claims covered by Section 9.1.

9.2. Indemnification by CUSTOMER:

CUSTOMER shall defend, indemnify, and hold harmless MECHADEMY and its AFFILIATES (and each of their licensors) and each of their respective officers, directors, contractors, agents, and employees ("MECHADEMY INDEMNITEES") against claims brought against MECHADEMY INDEMNITEES by any THIRD-PARTY arising from or related to:

• Any use of the PRODUCTS by CUSTOMER in violation of the AGREEMENT or any applicable law or regulation;
• Any CUSTOMER CONTENT; or
• An allegation that the CUSTOMER CONTENT or other material provided by the CUSTOMER or use of the PRODUCTS by the CUSTOMER in violation of the AGREEMENT or applicable law or regulation, violates, infringes, or misappropriates the INTELLECTUAL PROPERTY RIGHTS of a THIRD-PARTY.

The foregoing shall apply regardless of whether such damage is caused by the conduct of CUSTOMER and/or its NAMED USERS or by the conduct of a THIRD-PARTY using CUSTOMER’S access credentials or in any other circumstance.

10. TERM AND TERMINATION

10.1. Term:

The Term of the AGREEMENT shall commence on the EFFECTIVE DATE and shall continue thereafter until the later of the termination of each Purchase Agreement or five (5) years.

10.2. PURCHASE AGREEMENT Term:

The term of each PURCHASE AGREEMENT shall commence on the EFFECTIVE DATE specified in the PURCHASE AGREEMENT and continue thereafter until:

• the end of the term of the PURCHASE AGREEMENT as specified in the PURCHASE AGREEMENT; or
• if no term is specified, until delivery of the PRODUCTS and fulfillment of all obligations of the PARTIES in accordance with the PURCHASE AGREEMENT.

10.3. Evaluation Term:

If CUSTOMER is using the PRODUCT on an evaluation basis or as a free trial, then the term for such PRODUCT will be specified in the PURCHASE AGREEMENT.

If no such term is specified, the term shall be forty-five (45) days from the date the PRODUCT is delivered.

10.4. Termination for Material Breach:

Either PARTY may terminate the AGREEMENT or a PURCHASE AGREEMENT for cause if the other PARTY commits a material breach of the AGREEMENT or PURCHASE AGREEMENT (including, without limitation, a delay in CUSTOMER’S payment of any money due under this AGREEMENT or any PURCHASE AGREEMENT) and fails to cure such breach within thirty (30) days (or with respect to CUSTOMER’S payment failure, within ten (10) days) of delivery of notice of default by the other PARTY.

10.5. Termination for Financial Deterioration:

Either PARTY may terminate the AGREEMENT or any PURCHASE AGREEMENT immediately upon notice to the other if the other PARTY files for bankruptcy, ceases or threatens in writing to cease carrying on business, becomes insolvent, or makes an assignment for the benefit of creditors.

11. INSURANCE

For so long as any PURCHASE AGREEMENT remains in effect, MECHADEMY shall maintain, at its sole cost and expense, commercial general liability, workers' compensation, employer’s liability and professional liability insurance in an amount not less than $1 million USD in aggregate or in such other amount as may be specified in the PURCHASE AGREEMENT.

Additionally, MECHADEMY will maintain, at its sole cost and expense, any additional insurance as is required by applicable laws.

12. THIRD-PARTY PRODUCTS

12.1. THIRD-PARTY PRODUCTS:

Unless otherwise agreed in writing by MECHADEMY, if THIRD-PARTY PRODUCTS are supplied by MECHADEMY to CUSTOMER, such THIRD-PARTY PRODUCTS are provided on a "pass-through" basis only and are subject to the terms and conditions of the THIRD-PARTY vendor, including but not limited to warranties, licenses, indemnities, limitation of liability, prices and changes thereto.

13. TRAINING

MECHADEMY provides its standard training, e-training for PRODUCTS.

Any fees required for such training will be set forth in the applicable PURCHASE AGREEMENT.

14. MISCELLANEOUS

14.1. Assignment:

The AGREEMENT shall extend to and be binding upon the PARTIES to the AGREEMENT, their successors, and permitted assigns, provided, however, that neither PARTY may assign or transfer the AGREEMENT (including any PURCHASE AGREEMENT) without the other PARTY's prior written consent, which shall not be unreasonably withheld, delayed or conditioned.

Notwithstanding the foregoing limitation, MECHADEMY may assign or transfer the AGREEMENT, in whole or in part, without obtaining the consent of CUSTOMER to an AFFILIATE, or in connection with the transfer or sale of all or substantially all of its business relating to the PRODUCTS, or in the event of a merger, divestiture, internal reorganization or consolidation.

14.2. Independent Contractor:

MECHADEMY is an independent contractor, and each PARTY agrees that no partnership, joint venture, agency, fiduciary, or employment relationship exists between the PARTIES.

14.3. Force Majeure:

Except for CUSTOMER’S payment obligations, neither PARTY shall be liable nor be deemed to have defaulted or breached the AGREEMENT in the event of any delay or failure of performance caused by "FORCE MAJEURE”, which shall include but not be limited to, acts or circumstances beyond the reasonable control of either Party including, without limitation, acts of God, flood, fire, earthquake, explosion, governmental actions, war, invasion or hostilities (whether war is declared or not), terrorist threats or acts, riot, or other civil unrest, national emergency, revolution, insurrection, epidemic, pandemic, lockouts, strikes or other labor disputes (whether or not relating to either Party's workforce), or restraints or delays affecting carriers or inability or delay in obtaining supplies of adequate or suitable materials, materials or telecommunication breakdown or power outage, provided notice thereof is given to the other PARTY as soon as practicable.

Any FORCE MAJEURE condition which delays or prevents a PARTY’s performance shall entitle the PARTY to an extension by a period of time equal to the period of delay incurred as a result of the FORCE MAJEURE or to any other period as the PARTIES may agree in writing.

14.4. Waiver:

The waiver (whether express or implied) by either PARTY of a breach or default of any of the provisions of the AGREEMENT (including any PURCHASE AGREEMENT) by the other PARTY shall not be construed as a waiver of any succeeding breach of the same or other provisions nor shall any delay or omission on the part of either PARTY to exercise or avail itself of any right power or privilege that it has or may have hereunder operate as a waiver of any breach or default by the other PARTY.

14.5. Notices:

All notices and other communications required or permitted under the AGREEMENT will be in writing and delivered by confirmed transmission, by courier or overnight delivery service with written verification of receipt, or by registered or certified mail, return receipt requested, postage prepaid, and in each instance will be deemed given upon receipt.

All such notices, approvals, consents and other communications shall be sent to the addresses set forth on the PURCHASE AGREEMENT or to such other address as may be specified in writing by either PARTY to the other.

14.6. Invalidity and Severability:

If any provision of the AGREEMENT (including of any PURCHASE AGREEMENT) shall be found by any court to be invalid or unenforceable, the invalidity or unenforceability of such provision shall not affect the other provisions of the AGREEMENT and all provisions not affected by such invalidity or unenforceability shall remain in full force and effect.

The PARTIES agree to attempt to substitute for any invalid or unenforceable provision a valid or enforceable provision which achieves to the greatest extent possible the economic, legal and commercial objectives of the invalid or unenforceable provision.

14.7. Survival of Provisions:

The provisions of the AGREEMENT that by their nature survive expiration or termination of the AGREEMENT will survive expiration or termination of the AGREEMENT, including, but not limited to, the following Sections:

• 3 (Payments and Invoicing)
• 4 (INTELLECTUAL PROPERTY RIGHTS)
• 5 (Confidentiality)
• 7 (Disclaimer of Warranties)
• 8 (Limitation of Liability)
• 9.2 (Indemnification by CUSTOMER)
• 10 (Term and Termination)
• 12 (THIRD-PARTY PRODUCTS)
• 14 (Miscellaneous)

14.8. Governing Law and Jurisdiction:

The validity of the AGREEMENT and the rights, obligations and relations of the PARTIES under the AGREEMENT and in any dispute between them will be construed and determined under and in accordance with the substantive laws of the State of Texas, without regard to such state's principles of conflicts of law.

Each PARTY irrevocably agrees to submit to the exclusive jurisdiction of (and waives any objection to the venue of) the federal or state courts located in Harris County, Texas to determine any controversy or matter arising out of or in connection with this AGREEMENT.

To the extent otherwise applicable, the PARTIES hereto agree that the United Nations Convention on the International Sale of Goods will not apply to this AGREEMENT.

14.9. Export Restrictions:

The PARTIES agree to comply fully with all applicable international and national export laws, regulations, orders, decrees, and lists (collectively, "EXPORT CONTROL LAWS"), including, but not limited to, the U.S. Export Administration Regulations, the Office of Foreign Asset Control Regulations, and the EU Dual-Use Regulation 428/2009 (each as amended, updated, supplemented, or otherwise modified from time to time), as well as all applicable end-use and destination restrictions issued by the U.S., foreign governments, and supranational bodies to assure that no PRODUCT (or any part thereof) is:

• exported, directly or indirectly, in violation of any EXPORT CONTROL LAWS, or
• is intended to be used for any purpose prohibited by EXPORT CONTROL LAWS.

For the avoidance of doubt, the PARTIES agree that no data, information, or materials resulting from any PRODUCT will be exported, directly or indirectly, in violation of any applicable EXPORT CONTROL LAWS.

14.10. Sanctions:

Each PARTY agrees to comply with all UN, EU, US, UK and any other applicable jurisdiction's trade and economic sanctions laws, regulations, embargoes or similar restrictive measures ("SANCTIONS LAWS").

Each PARTY shall ensure that such PARTY and any distributors appointed by it will not resell any (or incorporate the PRODUCT or any part thereof in other products or services to be sold) to persons or entities:

• in violation of SANCTIONS LAWS;
• added to US Treasury Department's Office of Foreign Assets Control's Specially Designated Nationals and Blocked Persons List (the "OFAC SDN List"); or
• added to the EU Consolidated List or any other applicable sanctions list, including the UK's Consolidated List of Financial Sanctions Targets, each as amended, updated or restated from time to time.

Each PARTY represents and warrants to the other that, to its knowledge, no member, employee, director or officer of such PARTY, any person acting on its behalf, is in violation of Sanctions Laws or designated on a UN, EU, US, UK or other applicable sanctions list (a "RESTRICTED PERSON") or CONTROLLED (directly or indirectly) by a RESTRICTED PERSON.

14.11. Waiver of Jury Trial:

Each PARTY waives, to the fullest extent permitted by applicable law, any right it may have to a trial by jury in respect of any proceedings relating to the AGREEMENT or any performance or failure to perform of any obligation under the AGREEMENT.

14.12. Waiver of Right to Class Action:

Each PARTY waives, to the fullest extent permitted by applicable law, any right it may have to participate in a class action in respect of any proceedings relating to the AGREEMENT or any performance or failure to perform of any obligation under the AGREEMENT.

Each PARTY may only bring a claim against the other in an individual capacity and not as a plaintiff or class member in any purported class or representative proceeding.

14.13. THIRD-PARTY Beneficiary:

Except as expressly set forth in the AGREEMENT, the PARTIES do not intend to create rights for any person as a THIRD-PARTY beneficiary of the AGREEMENT.

14.14. Entire Agreement; Amendments; Execution:

The AGREEMENT constitutes the entire AGREEMENT between the PARTIES relating to its subject matter and supersedes all prior or contemporaneous representations, understandings or AGREEMENTS whether written or oral, relating to its subject matter.

The AGREEMENT will prevail over any additional, conflicting, or inconsistent terms and conditions that may be contained in any purchase order or other document furnished by CUSTOMER to MECHADEMY.

The AGREEMENT may be amended or modified only by a writing that is signed by or on behalf of both PARTIES.

The AGREEMENT may be executed in counterparts, each of which will be deemed an original, but all of which together will constitute one and the same instrument.

An executed facsimile or electronic copy of the AGREEMENT shall be construed as if it were an original.

TURBOMECHANICA PLATFORM TERMS AND CONDITIONS

The TURBOMECHANICA PLATFORM TERMS AND CONDITIONS (the "TURBOMECHANICA PLATFORM TERMS AND CONDITIONS") is appended to and forms an integral part of the AGREEMENT between MECHADEMY and the CUSTOMER.

1. DEFINITIONS

Capitalized terms not otherwise defined herein have the meanings given to them in the TURBOMECHANICA TERMS AND CONDITIONS.

“ACCEPTABLE USE POLICY”

Means the then-current Acceptable Use Policy of MECHADEMY, which will be made available on the MECHADEMY website, and may be updated, modified, supplemented, or otherwise amended from time to time.

“ACCOUNT ADMINISTRATOR”

Means the personnel designated by the CUSTOMER who shall have the right to grant, revoke or edit USER access or USER roles on behalf of the CUSTOMER.

“ACCOUNT INFORMATION”

Means any information provided by the CUSTOMER to MECHADEMY to facilitate the access of a USER or an ACCOUNT ADMINISTRATOR on the TURBOMECHANICA PLATFORM. ACCOUNT INFORMATION may include, but not be limited to USER personal information, USERS CREDENTIALS, USAGE METRICS, or information on CUSTOMER’S business and AFFILIATES.

“CUSTOMER SUBMISSION”

Means any information, data (including PERSONAL DATA), software, text, image, audio, video, photograph or other content or material, in any format, that CUSTOMER or a USER posts, uploads, or otherwise submits on the TURBOMECHANICA PLATFORM.

“DATA CAPTURE RATE”

Means the minimum permissible duration between consecutive data inputs received and stored on the TURBOMECHANICA PLATFORM. Data submitted at a rate faster than the DATA CAPTURE RATE may not be stored appropriately. The PURCHASE AGREEMENT may specify DATA CAPTURE RATES agreed with the CUSTOMER.

“DATA POINT”

Means a distinct unit of data, for example – an input from a sensor to the TURBOMECHANICA PLATFORM.

“DATA SOURCE”

Means any device, equipment, sensor or system from which one or more data points originate and are delivered to the TURBOMECHANICA PLATFORM. The PURCHASE AGREEMENT may specify CUSTOMER’S DATA SOURCES from which data points are to be captured.

“DOCUMENTATION”

Means any physical manuscript or digital text supplied by MECHADEMY or a THIRD-PARTY bearing information on technical specifications or product credentials, know-how, operations, training and safety or other documentation pertaining to the PRODUCTS. DOCUMENTATION may be revised, supplemented, or amended by MECHADEMY from time to time.

“NAMED USER”

Means a specific individual identifiable by a username, who has been granted access to the TURBOMECHANICA PLATFORM by an ACCOUNT ADMINISTRATOR or by MECHADEMY. The username of a NAMED USER shall remain unique and shall be identified using one, more or all of the following:

• (i) Login credentials or other information used to grant USER access to the TURBOMECHANICA PLATFORM,
• (ii) Internet address, network address, web cookies, equipment identifier, International Mobile Equipment Identity (IMEI), or
• (iii) Other information that recognizes the device used to access the Product.

“PERMITTED THIRD-PARTY”

Means any THIRD-PARTY specified in the PURCHASE AGREEMENT. A PERMITTED THIRD-PARTY may be required to execute a joinder to the Agreement and to the applicable PURCHASE AGREEMENT if requested by MECHADEMY.

“PERSONAL DATA”

Means any information relating to an individual who can be identified, directly or indirectly, in particular by reference to a physical, physiological, genetic, mental, economic, cultural, or social identifier such as name, identification number, location data, online identifier, or to one or more factors specific to the identity of that natural person.

“PRIVACY POLICY”

Means the then-current TURBOMECHANICA PRIVACY POLICY, which will be made available on the MECHADEMY website and the TURBOMECHANICA PLATFORM, and may be updated, modified, supplemented, or otherwise amended from time to time.

“REPRESENTATIVES”

Mean any employees, officers, representatives, agents, directors, members or advisers of a PARTY.

“SERVICE LEVEL”

Means any service level for a PRODUCT that is set forth in the PURCHASE AGREEMENT Schedule for the PRODUCT.

“THIRD-PARTY CONTENT”

Means all data and information whose ownership does not reside with either PARTY and which is:

• (i) Submitted by a PARTY to the other PARTY,
• (ii) Obtained, developed, or produced in connection with the provision, receipt, or use of the PRODUCTS, or
• (iii) To which MECHADEMY has access in connection with the provision of the PRODUCTS.

“USAGE METRICS”

Means any information or data that is reasonably necessary to understand, aggregate, compute, measure, or support CUSTOMER’S use of the PRODUCTS.

“USERS CREDENTIALS”

Mean the username and password of each USER as provided by MECHADEMY to access the TURBOMECHANICA PLATFORM.

2. RESERVED

3. USE OF PRODUCTS

3.1. Use of PRODUCTS:

MECHADEMY shall grant to the CUSTOMER a non-exclusive, worldwide, non-transferable, non-sublicensable, limited, revocable right to allow the use of the TURBOMECHANICA PLATFORM provided that:

• The CUSTOMER will be allowed the use of only specific elements of the PRODUCTS for a specific period of time as specified in the PURCHASE AGREEMENT. Upon termination of the term of the PURCHASE AGREEMENT, the CUSTOMER shall not be able to access or use the PRODUCT or DOCUMENTATION;
• The CUSTOMER complies with all obligations pursuant to the PURCHASE AGREEMENT, including all payments as specified therein;
• The CUSTOMER complies with all the terms and conditions set forth in this AGREEMENT.
• The CUSTOMER shall use the PRODUCTS solely for the internal business operations of the CUSTOMER;
• CUSTOMER shall not make the PRODUCTS accessible or available for use by AFFILIATES or PERMITTED THIRD PARTIES unless expressly permitted in the PURCHASE AGREEMENT; and
• CUSTOMER will always be liable for any acts or omissions of its USERS, AFFILIATES, and PERMITTED THIRD PARTIES.

3.2. Restrictions on Use:

Copy Restrictions:

The TURBOMECHANICA PLATFORM, PRODUCT and DOCUMENTATION are subject to protection by copyright laws and international treaties.

Copying of the TURBOMECHANICA PLATFORM, PRODUCT or DOCUMENTATION in whole or in part is prohibited, unless authorized by MECHADEMY in writing.

In the event copying of any part of the TURBOMECHANICA PLATFORM, PRODUCT or DOCUMENTATION is permitted by MECHADEMY, the CUSTOMER or THIRD-PARTY authorized shall duly display all titles, trademarks, copyright and restricted rights notices on all such copies.

Use Restrictions:

The rights of use under this AGREEMENT provide the CUSTOMER restricted rights to use and access the PRODUCTS.

All other rights and privileges relating to the PRODUCTS shall belong to MECHADEMY or its licensors.

The CUSTOMER in entering this AGREEMENT shall not acquire any rights, express or implied, other than the rights specified in the AGREEMENT or the PURCHASE AGREEMENT.

CUSTOMER’S use of the PRODUCTS shall be limited to the extent specified in the AGREEMENT or the PURCHASE AGREEMENT, except to the extent applicable law provides the CUSTOMER additional rights, in which case the rights of use shall be restricted to the maximum extent permitted by applicable law.

The CUSTOMER further agrees that, unless expressly permitted by an applicable law, or duly authorized in writing by MECHADEMY, or expressly permitted in the AGREEMENT, PURCHASE AGREEMENT or DOCUMENTATION, neither the CUSTOMER nor any THIRD-PARTY authorized by the CUSTOMER shall be permitted to:

• Reverse engineer, reproduce, decompile, recompile, disassemble, merge, modify, adapt or translate the PRODUCTS or DOCUMENTATION or part thereof, or create derivative works based on the PRODUCTS or DOCUMENTATION;
• Incorporate the PRODUCTS into any other product or service or offering;
• Remove, obliterate, destroy, minimize, block or modify any logos, trademarks, copyright, digital watermarks, or other notices of MECHADEMY or its licensors that are included in the PRODUCTS;
• Work around any technical limitations in the PRODUCTS;
• Make unauthorized copies of the PRODUCTS;
• Circulate, distribute, publish, make available, transfer, sublicense, rent, lease, sell, lend, distribute, outsource, share, commercially exploit, or assign any part of the PRODUCTS;
• Transfer the PRODUCTS to another location or to other equipment;
• Input, output or store any content that is libelous, unlawful or tortious or in violation of any applicable law, privacy rights or INTELLECTUAL PROPERTY RIGHTS;
• Compromise, disclose or make available any security feature of the PRODUCTS, including but not limited to network discovery, port and service identification, vulnerability scanning, password cracking, remote access testing, or penetration testing;
• Access, use or apply the PRODUCTS in a manner inconsistent with the DOCUMENTATION, the AGREEMENT or the PURCHASE AGREEMENT; or
• Harness any portion or application of the PRODUCTS to develop, conceptualize, support or build any products or services competitive to the PRODUCTS or any other products or services of MECHADEMY.

3.3. Acceptable Use Policy:

CUSTOMER shall comply with the Acceptable Use Policy and shall not use or permit the use of the PRODUCTS in a manner that violates the Acceptable Use Policy, which is incorporated herein by reference.

3.4. Other Terms of Use:

The CUSTOMER’S use of the PRODUCTS shall also be governed by the terms of use of the various THIRD-PARTY software, tools, applications, or products which are integral to the PRODUCTS or the TURBOMECHANICA PLATFORM.

4. PROVISION OF PRODUCTS

4.1. Provision of PRODUCT:

MECHADEMY will provide the PRODUCTS on the TURBOMECHANICA PLATFORM in accordance with the AGREEMENT.

4.2. Subscription Models:

MECHADEMY offers various subscription models for the PRODUCTS to the CUSTOMER. The terms and conditions applicable to each subscription model shall be as specified in the applicable PURCHASE AGREEMENT.

4.4. Disclaimer of THIRD-PARTY PRODUCTS:

MECHADEMY may offer the CUSTOMER use, access, or purchase of THIRD-PARTY PRODUCTS either directly or through the TURBOMECHANICA PLATFORM, the PRODUCTS, or external websites.

• Such use, access, or purchase of THIRD-PARTY PRODUCTS shall be solely governed by the contract between the CUSTOMER and the THIRD-PARTY and shall be at CUSTOMER’S own risk; and
• MECHADEMY disclaims all warranty, liability, or obligation relating to such THIRD-PARTY PRODUCTS.

4.5. Modifications or Discontinuance of Content:

So long as the same does not violate the terms of any PURCHASE ORDER, at any time, MECHADEMY may modify or discontinue:

• Any content developed by MECHADEMY that is made available or accessible through the TURBOMECHANICA PLATFORM, the PRODUCTS, or the DOCUMENTATION, including but not limited to text, audio, video, images, technical drawings, engineering specifications, software, data, models, samples, libraries, standards, information, programming interfaces, code, command line tools, proofs of concept, templates, or any related technology.
• Any CUSTOMER CONTENT that violates the AGREEMENT.

4.6. Modifications or Discontinuance of PRODUCTS:

So long as the same does not violate the terms of any PURCHASE ORDER, at any time, MECHADEMY may modify or update the features, specifications, or functionality of, or discontinue, any PRODUCT or DOCUMENTATION, in whole or in part.

4.7. Collection of Metrics:

MECHADEMY and/or its licensors may record and analyze various metrics including, but not limited to usage, billing, performance, or other information concerning the use, access, or functioning of the PRODUCTS:

• For MECHADEMY's internal processes, compliance, or product improvement;
• To ensure compliance of the PARTIES with the AGREEMENT; or
• To detect and prevent fraud.

5. SECURITY MEASURES AND DATA PRIVACY

5.1. Security Measures:

MECHADEMY will implement reasonable measures to secure and protect the PRODUCTS against accidental or unlawful loss, access, or disclosure.

MECHADEMY shall not be liable for any security breaches, including but not limited to those by computer hackers, unlawful entry, unauthorized access, or theft beyond MECHADEMY’s CONTROL.

5.2. Usage of PERSONAL DATA:

No PERSONAL DATA shall be uploaded by the CUSTOMER as CUSTOMER CONTENT except for the express purpose of setting up USER’S CREDENTIALS for access to the PRODUCTS.

MECHADEMY shall use PERSONAL DATA in accordance with the then-current TURBOMECHANICA PRIVACY POLICY.

5.3. CUSTOMER Security Requirements:

CUSTOMER shall be responsible for reviewing the security features associated with the PRODUCTS and determining if the security features meet the CUSTOMER’S requirements for the use of the PRODUCTS.

CUSTOMER shall also be responsible for determining and implementing controls and measures to secure CUSTOMER CONTENT provided by the CUSTOMER to the TURBOMECHANICA PLATFORM.

6. CUSTOMER OBLIGATIONS AND CONTENT

6.1. CUSTOMER CONTENT:

The CUSTOMER is responsible for obtaining all rights concerning the CUSTOMER CONTENT provided by the CUSTOMER to the TURBOMECHANICA PLATFORM.

The CUSTOMER hereby grants MECHADEMY, its AFFILIATES, and its subcontractors all necessary rights and permissions to the CUSTOMER CONTENT to use, copy, store, host, distribute, provide, transmit, process, modify, display, perform, make disclosures, obtain licenses, permits, approvals, or consents to the extent required to fulfill MECHADEMY's obligations under the AGREEMENT.

The CUSTOMER is solely responsible for the accuracy, quality, integrity, legality, vulnerability, reliability, and appropriateness of the CUSTOMER CONTENT.

The CUSTOMER is also responsible for any system or security breach arising from the CUSTOMER CONTENT, including any viruses, Trojan horses, worms, or other harmful programming routines contained in the CUSTOMER CONTENT.

MECHADEMY shall not be responsible for the security, integrity, or confidentiality of any CUSTOMER CONTENT disclosed by the CUSTOMER to any THIRD-PARTY.

6.2. Provision of Information:

CUSTOMER shall provide details of at least one Account Administrator in order to use or access the PRODUCTS.

MECHADEMY or the Account Administrator may subsequently register other USERS and create USERS CREDENTIALS for their access to the PRODUCTS.

USERS CREDENTIALS shall remain personal, and neither PARTY nor their respective AFFILIATES or subcontractors may sell, transfer, sublicense, or assign the USERS CREDENTIALS to any other individual or entity.

6.3. Specific CUSTOMER Responsibilities:

The CUSTOMER is responsible and liable for its own and its USERS' use of the PRODUCTS.

Unless otherwise specified in the PURCHASE AGREEMENT, the CUSTOMER is responsible to ensure:

• All USERS are aware of the terms of the AGREEMENT;
• Payment of all fees and charges for all its USERS who have been granted access to the PRODUCTS;
• No USER CREDENTIALS are used by more than one individual USER;
• The use and access of the PRODUCTS does not violate any applicable law, MECHADEMY policy, or the AGREEMENT;
• Provision of all reasonably necessary information and infrastructure at CUSTOMER’S end to allow MECHADEMY to fulfill its obligations under the AGREEMENT;
• The USERS CREDENTIALS are kept confidential and secure. MECHADEMY shall not be responsible for any unauthorized access through CUSTOMER’S USERS CREDENTIALS;
• The CUSTOMER CONTENT and CUSTOMER’S network and systems are compatible with the TURBOMECHANICA PLATFORM requirements;
• The accuracy, legality, reliability, integrity, and quality of all CUSTOMER submissions;
• Procurement and maintenance of systems, network connections, and telecommunications links required to access the PRODUCTS; and
• Deploying reasonable measures to prevent unauthorized use of or access to the PRODUCTS. The CUSTOMER shall promptly notify MECHADEMY immediately upon becoming aware of any unauthorized use or access.

6.4. No Special or Specific Data:

Unless agreed by MECHADEMY in writing, the CUSTOMER may not introduce any CUSTOMER CONTENT into the TURBOMECHANICA PLATFORM that is subject to any data security or data protection obligations, or governmental regulations, including, but not limited to:

• The Health Insurance Portability and Accountability Act of 1996 (HIPAA);
• Gramm-Leach-Bliley Act of 1999 (GLB);
• All applicable laws and non-governmental standards protecting PERSONAL DATA such as Payment Card Industry Data Security Standard (PCI-DSS) and Payment Application Data Security Standard (PA-DSS);
• All laws concerning the protection, transport, storage, use, and processing of data such as the EU General Data Protection Regulation (GDPR); and
• All applicable laws similar to those laws listed in Section 6.4, Subsections (i) through (iv).

6.5. Return of CUSTOMER CONTENT During the Term:

During the Term of the AGREEMENT, the CUSTOMER may at any time request MECHADEMY in writing to return any CUSTOMER CONTENT associated with or introduced into the TURBOMECHANICA PLATFORM.

Upon receipt of such a request, MECHADEMY shall, at CUSTOMER’S expense, deploy reasonable efforts to return or remove from the PRODUCTS such CUSTOMER CONTENT within sixty (60) days after receipt of such request, in the manner and format deemed most appropriate by MECHADEMY.

6.6. Return of CUSTOMER CONTENT Following Expiration or Termination:

At the end of the Term of the AGREEMENT or upon termination of the PURCHASE AGREEMENT, upon CUSTOMER’S request and at CUSTOMER’S expense, MECHADEMY shall deploy reasonable efforts to return or remove from the PRODUCTS such CUSTOMER CONTENT within sixty (60) days after receipt of such request, in the manner and format deemed most appropriate by MECHADEMY, except where required to retain such CUSTOMER CONTENT in accordance with applicable law.

Following the sixtieth (60th) day after the end of the Term of the AGREEMENT or the termination of the PURCHASE AGREEMENT, MECHADEMY shall have no obligation to continue to hold, store, export, delete, or return any CUSTOMER CONTENT.

6.7. CUSTOMER CONTENT Inclusion and Exclusions:

• Any THIRD-PARTY PRODUCTS introduced by the CUSTOMER or its USERS into the TURBOMECHANICA PLATFORM shall be deemed to be included in CUSTOMER CONTENT.
• Any THIRD-PARTY PRODUCTS made available by MECHADEMY to the CUSTOMER shall be deemed to not be included in CUSTOMER CONTENT.

6.8. Legal and Regulatory Requirements:

The CUSTOMER is solely responsible for CUSTOMER’S compliance with any applicable laws, rules, and regulations.

The CUSTOMER is also responsible for ensuring that the PRODUCTS meet all technical, functional, legal, or other requirements necessary to fulfill the CUSTOMER’S compliance obligations.

6.9. Data Retention System:

Neither the TURBOMECHANICA PLATFORM nor the PRODUCTS are intended to serve as data or document storage utilities.

Limited CUSTOMER CONTENT may be stored periodically on the TURBOMECHANICA PLATFORM to enable the desired functioning of the PRODUCT. The CUSTOMER is responsible for backing up all CUSTOMER CONTENT using suitable resources at their own cost.

7. SUSPENSION OF PRODUCTS

7.1. Suspension Rights:

MECHADEMY may suspend any CUSTOMER’S or USER’s access to or use of the TURBOMECHANICA PLATFORM or the PRODUCTS if it believes such access or use is likely to:

• Adversely affect the functionality of the PRODUCTS, any THIRD-PARTY PRODUCT, or the access and use of other MECHADEMY CUSTOMERS;
• Pose a security risk to MECHADEMY or others; or
• Violate any applicable laws, the AGREEMENT, or the PURCHASE AGREEMENT.

MECHADEMY shall, to the extent practicable, notify the CUSTOMER in advance of any such suspension.

7.2. Restoration of PRODUCTS:

If no termination of the applicable PURCHASE AGREEMENT has occurred, MECHADEMY will make reasonable efforts to restore access to the TURBOMECHANICA PLATFORM or the PRODUCTS as soon as practicable, once the CUSTOMER resolves the issue that caused the suspension.

7.3. Material Breach of AGREEMENT:

Any suspension event described in Section 7.1 shall constitute a material breach of the AGREEMENT.

8. SERVICE LEVELS

Unless it would breach a PURCHASE AGREEMENT, MECHADEMY reserves the right to amend, suspend, or terminate any Service Levels at its discretion.

MECHADEMY will provide thirty (30) days’ prior notice to the CUSTOMER before making any such changes.

9. DISCLAIMER

MECHADEMY shall not be liable for:

• Any expenses, costs, investments, or obligations related to the CUSTOMER’S or USER’S access or use of the PRODUCTS;
• Any information, product, or service provided by a THIRD-PARTY to MECHADEMY relating to the functionality of the PRODUCTS;
• Unauthorized access or use of the PRODUCTS by any party using USERS CREDENTIALS without permission; or
• Temporary unavailability of the PRODUCTS or any part thereof.

10. HIGH RISK USE

MECHADEMY does not guarantee that the PRODUCTS are error-free, fault-free, or will operate without interruption.

The CUSTOMER shall not use the PRODUCTS in any high-risk environment where their failure could result in:

• Fatality or bodily injury to any individual;
• Material damage; or
• Environmental damage.

11. AUDITS AND VERIFICATION

11.1. Record Keeping:

During the Term of the AGREEMENT and for a period of two (2) years afterward, the CUSTOMER must accurately maintain complete records related to the location and use of the PRODUCTS.

These records shall be available to MECHADEMY upon request to facilitate its audit rights under Section 11.2.

11.2. Audit Right:

During the Term of the AGREEMENT and for a period of two (2) years thereafter, the CUSTOMER shall permit MECHADEMY and/or its designated Auditor to conduct audits once annually upon request. These audits may be conducted remotely or on-site and may involve examining:

• CUSTOMER’S records, systems, personnel, and facilities;
• The CUSTOMER’S or USERS’ access or use of the PRODUCTS;
• Compliance with the AGREEMENT or PURCHASE AGREEMENT; and
• Other relevant information regarding the PRODUCTS.

Audits will take place during regular business hours, and the CUSTOMER shall provide full cooperation during the audit process.

Additionally, MECHADEMY reserves the right to conduct remote audits using the inherent functionalities of the PRODUCTS at any time.

If an audit reveals that the CUSTOMER has breached the AGREEMENT or PURCHASE AGREEMENT, accessed or used the PRODUCTS beyond permitted measures, or underpaid any fees, the CUSTOMER shall be responsible for all audit-related costs incurred by MECHADEMY.

11.3. Compliance Certificate:

Upon MECHADEMY’s request, the CUSTOMER shall submit a signed certificate of compliance affirming that the CUSTOMER has adhered to the terms of the AGREEMENT regarding the access and use of the PRODUCTS.

The CUSTOMER shall provide the compliance certificate within thirty (30) days of receiving MECHADEMY's written request. However, MECHADEMY will not request more than one compliance certificate per year.

12. SUPPORT SERVICES AND MAINTENANCE

All support and maintenance services provided by MECHADEMY for the PRODUCTS will be governed by MECHADEMY's then-current maintenance and support policies. The CUSTOMER may refer to those policies for detailed information on the scope of support available.

13. SUBCONTRACTORS AND DATA CENTERS

13.1. Use of Subcontractors:

MECHADEMY may subcontract, host, perform, or outsource certain functionalities or components of the PRODUCTS. This may include, but is not limited to:

• Data hosting and storage;
• Service administration;
• Product support and maintenance;
• Disaster recovery services;
• System security management;
• Data monitoring and analysis; and
• Consulting or related services.

13.2. Global Data Operations:

CUSTOMER’S use of the PRODUCTS may involve the collection, transfer, processing, or storage of CUSTOMER CONTENT across various geographic regions. CUSTOMER CONTENT may be processed in data centers located worldwide, as determined by MECHADEMY.

13.3. Third-Party Providers:

MECHADEMY reserves the right to engage THIRD-PARTY providers for the provision of any part of the PRODUCTS. MECHADEMY may substitute or modify its agreements with such THIRD-PARTIES at any time without requiring CUSTOMER’s prior approval.

14. DISCLAIMER OF WARRANTIES

15. INDEMNIFICATION

The CUSTOMER shall indemnify, hold harmless and defend MECHADEMY and its AFFILIATES against claims brought against MECHADEMY by any THIRD-PARTY arising from or related to:

• MECHADEMY's or CUSTOMER’S access or use of any THIRD-PARTY PRODUCTS;
• MECHADEMY's or CUSTOMER’S access or use of any software, machines, equipment, systems, information technology environment, or premises which is facilitated, provisioned, owned or operated by the CUSTOMER or any THIRD-PARTY; or
• CUSTOMER’S access or use of the PRODUCTS for any high-risk use as specified in Section 10.

16. NOTICE

CUSTOMER agrees that notices shall be valid and MECHADEMY may deliver to the CUSTOMER all notices or communications pursuant to this AGREEMENT:

• on the TURBOMECHANICA PLATFORM, or
• by electronic mail to the last known/recorded CUSTOMER’S email address available with MECHADEMY.

17. MODIFICATION OR AMENDMENT OF AGREEMENT

MECHADEMY reserves the right to alter or revise or update any terms and conditions contained in the AGREEMENT, in whole or in part, at any time.

All such alterations or revisions or updates will be effective upon posting of such alterations or revisions or updates on the TURBOMECHANICA PLATFORM by MECHADEMY.

In the event such alterations or revisions or updates to the AGREEMENT result in an adverse effect to the CUSTOMER’S access or use of the PRODUCTS, the CUSTOMER may provide MECHADEMY with a request for amendment, citing specific clauses and the adverse effect resulting therefrom, within Ten (10) calendar days after MECHADEMY first posts of such alterations or revisions or updates.

MECHADEMY shall make reasonable efforts to amend the requested clauses to remove the adverse effects on CUSTOMER within thirty (30) calendar days of receipt of such a request for amendment.

If MECHADEMY fails to amend or update the cited clauses within the said period, the CUSTOMER may terminate the PURCHASE AGREEMENT by delivering a notice of termination to MECHADEMY within ten (10) calendar days of the end of the thirty (30) calendar day period.

The CUSTOMER shall not be liable to pay any subscription fees to MECHADEMY for the period following the effective date of a termination notice which is properly and timely delivered pursuant to this Section 17.

© 2025 Turbomechanica. All Rights Reserved.

TURBOMECHANICA PRIVACY POLICY

Last Updated: February 24, 2025

This TURBOMECHANICA PRIVACY POLICY ("Privacy Policy") is effective as of January 2023. Please note that this privacy statement will regularly be updated to reflect any changes in the way we handle your personal data or any changes in applicable laws.

DEFINITIONS:

All capitalized terms not otherwise defined herein shall have the meanings given to them in the TURBOMECHANICA TERMS AND CONDITIONS.

NOTICES:

MECHADEMY recognizes the importance of and is committed to protecting and responsibly processing PERSONAL DATA of all CUSTOMERS and USERS and comply with applicable data privacy and protection laws.

This POLICY is disclosed for full transparency on MECHADEMY's general privacy practices as applicable to PERSONAL DATA provided by CUSTOMERS or USERS of the TURBOMECHANICA PLATFORM or the PRODUCTS.

This POLICY also describes the CUSTOMERS or USERS options regarding use of their PERSONAL DATA.

By clicking "I UNDERSTAND" in the Cookie Disclaimer notification when first entering the TURBOMECHANICA PLATFORM, the USER agrees to the terms of this POLICY and consents to the collection and usage of their PERSONAL DATA as specified in the POLICY.

MECHADEMY recommends that all CUSTOMERS and USERS review the TURBOMECHANICA PRIVACY POLICY periodically as it may be updated from time to time.

If this POLICY or any part thereof is not agreeable to the CUSTOMER or USER, the CUSTOMER or USER should not use the TURBOMECHANICA PLATFORM or the PRODUCTS.

MECHADEMY strongly advises the CUSTOMERS and USERS to not send, post, disclose, or make available any sensitive information (such as Social Security numbers, financial account information, information related to racial or ethnic origin, political opinions, religious or philosophical beliefs, criminal background, trade union membership, genetic or biometric data, health data, or sexual orientation) on the TURBOMECHANICA PLATFORM or the PRODUCTS or to MECHADEMY directly.

COLLECTION OF PERSONAL DATA:

In order to permit access or use of the TURBOMECHANICA PLATFORM or the PRODUCTS, MECHADEMY may collect and store:

• information in compliance with security and legal requirements to grant such an access or use, including but not limited to the USERS CREDENTIALS;
• non-personally identifiable information about the USERS' computer and/or browser, including but not limited to browser type, type of device, IP address, location, operating system, internet service provider, the referring URL and information on the pages accessed on the TURBOMECHANICA PLATFORM;
• information from USERS' computers to gather insights on how the TURBOMECHANICA PLATFORM is rendering across various browser platforms or conforming to required website security;
• USAGE METRICS or other data in relation to the CUSTOMERS' or USERS' actions during access or use of the TURBOMECHANICA PLATFORM or the PRODUCTS. Such data may include CUSTOMERS' or USERS' preferences & settings, usage statistics and performance analytics.

In order to facilitate USER'S contact with MECHADEMY electronically or to allow USER to acquire any content provided by MECHADEMY such as PRODUCTS DOCUMENTATION, white papers, webinars, newsletter, PRODUCTS demo or training content MECHADEMY may prompt the USER to provide relevant PERSONAL DATA such as:

• USER'S name;
• USER'S contact information;
• USER'S company name;
• USER'S job title; and
• Any other information relating to the USER that is requisite to responding to the USER in an appropriate manner

In order to facilitate fulfilment of the terms of the AGREEMENT, make available the PRODUCTS, provide customer support, prepare invoices, service business relationships or manage MECHADEMY's business, MECHADEMY may collect and store information relating to the CUSTOMER, the CUSTOMER's employees, contractors, advisors and authorized USERS such as:

• Name;
• Business contact details; and
• Position or title.

In order to ensure safety and security and to comply with regulatory requirements MECHADEMY may collect and store visitor information or initiate supervisory or surveillance activities on individuals visiting the TURBOMECHANICA PLATFORM.

USE OF PERSONAL DATA:

MECHADEMY may use the collected PERSONAL DATA to:

• Register a USER account on the TURBOMECHANICA PLATFORM;
• Allow CUSTOMERS or USERS to purchase PRODUCTS from MECHADEMY;
• Contact CUSTOMERS or USERS or CUSTOMERS' employees, prospects, partners and suppliers in relation to the PRODUCTS;
• Provide information on the PRODUCTS that CUSTOMERS or USERS expressed interest in;
• Send the required content to the USER;
• Enable the USER contact MECHADEMY or be contacted by MECHADEMY;
• Deploy initiatives to personalize, improve or optimize the PRODUCTS, PRODUCTS features and functionalities, content or user experience on the TURBOMECHANICA PLATFORM;
• Augment with THIRD-PARTY information to improve understanding of USERS' needs;
• develop analysis and business intelligence for facilitating MECHADEMY's business or for MECHADEMY's marketing purposes;
• Respond to USERS' feedback, enquiries, complaints, suggestions or request for information, technical support, dispute resolution or logistics assistance;
• Enforce TURBOMECHANICA TERMS AND CONDITIONS, TURBOMECHANICA GENERAL TERMS AND CONDITIONS, TURBOMECHANICA PLATFORM TERMS AND CONDITIONS, TURBOMECHANICA PRIVACY POLICY, PURCHASE AGREEMENT or any other legal or administrative matter;
• Initiate a CUSTOMER or USER satisfaction survey information; or
• Defend MECHADEMY's rights.

SHARING OF PERSONAL DATA

MECHADEMY's PRODUCTS are offered globally and MECHADEMY's AFFILIATES, business processes, management and technical systems are present all around the world. Accordingly:

• MECHADEMY shall put in place standard commercially reasonable procedures, to protect PERSONAL DATA consistently.
• MECHADEMY may share requisite PERSONAL DATA with its business partners and AFFILIATES across the world in accordance with this PRIVACY POLICY, for the purpose of facilitating access or use of the TURBOMECHANICA PLATFORM or PRODUCTS, provide customer support, reply to CUSTOMERS' or USERS' queries or make available content requested by the CUSTOMERS or USERS.
• The CUSTOMERS and USERS recognize that the privacy and data-protection laws in countries other than that of the CUSTOMERS or USERS, may be different from, or less stringent than, those in the CUSTOMERS' or USERS' country of residence. By agreeing to this PRIVACY POLICY or using the TURBOMECHANICA PLATFORM or PRODUCTS or by providing any PERSONAL DATA to MECHADEMY, the CUSTOMERS or USERS expressly consent to such transfer and processing.
• MECHADEMY shall restrict the PERSONAL DATA shared with any such entity and limit the usage of the shared data, to the minimum required to execute the applicable function.
• During the process of identifying partners with whom PERSONAL DATA may be shared, MECHADEMY endeavors to take reasonable measures to ensure protection of privacy and security of data in accordance with this Privacy Policy.

In the event of sale, purchase, merger or corporate reorganization of MECHADEMY's business:

• MECHADEMY may disclose or transfer PERSONAL DATA to the successor or buyer;
• MECHADEMY may receive or acquire PERSONAL DATA from the predecessor or seller;
• MECHADEMY shall deploy appropriate measures for the protection of PERSONAL DATA exchanged.

Upon receipt of formal legal notice from a government authority or legal enforcement agency, in the due course of an investigation or as applicable by law, MECHADEMY may be required to share information, including PERSONAL DATA and computer information, with the investigating body.

MECHADEMY may disclose PERSONAL DATA to safeguard, preserve or defend the rights or property, limit the liability or safeguard the welfare of MECHADEMY, its affiliates, partners, suppliers or clients, and others, provided that, in MECHADEMY's opinion there are reasonable grounds to believe that such disclosure is necessary.

MECHADEMY may disclose information, including PERSONAL DATA and Computer Information with a third party to verify or enforce compliance with the AGREEMENT, PRIVACY POLICY, Copyright Policy or any other policy governing the TURBOMECHANICA PLATFORM or PRODUCTS, or to safeguard against abuse, violation, exploitation or unauthorized use of the TURBOMECHANICA PLATFORM or PRODUCTS.

INFORMATION SECURITY AND ACCURACY

MECHADEMY shall deploy commercially reasonable physical, administrative and technical measures to safeguard PERSONAL DATA from unauthorized access, use, exposure, modification, disclosure or damage and to maintain accuracy of the PERSONAL DATA.

INFORMATION SECURITY DISCLAIMER

MECHADEMY does not have any control of the breach of security through CUSTOMERS' devices, internet service providers or any other intermediary. MECHADEMY advises CUSTOMERS to review the security and privacy policies of their internet service provider and the software on their devices, as well as employ sufficient security measures on their devices to safeguard their security credentials.

It is the CUSTOMERS' responsibility to protect their USER CREDENTIALS such as username, password and other PERSONAL DATA. All communications with security credentials such as username, password and payment information should be stored safely or destroyed after memorizing. Any loss or misuse of CUSTOMER'S account due to compromised security credentials is beyond the scope of MECHADEMY's control and MECHADEMY shall not be liable or responsible for any damages caused.

CUSTOMERS are also informed that certain information submitted by them may be recorded on their device browser history even after they conclude their visit to the TURBOMECHANICA PLATFORM. MECHADEMY strongly recommends the CUSTOMERS to log off from a device after end of session especially if others have access to it, such as in the case of public devices or mobile devices. Any loss or misuse of data on account of compromised security on CUSTOMERS' device is beyond the scope of MECHADEMY's control and MECHADEMY shall not be liable or responsible for any damages caused on this account.

MECHADEMY hereby declares that no security measure is 100% effective, and MECHADEMY cannot guarantee 100% absolute protection of data from unauthorized access, exposure, modification or damage, nor can MECHADEMY guarantee that data will not be compromised on account of accidents, malicious attacks or other circumstances beyond MECHADEMY's control.

RETENTION PERIOD

MECHADEMY shall retain PERSONAL DATA no longer than required to fulfil the purposes for which it was collected.

PERSONAL DATA may be retained beyond the term of the AGREEMENT or the delivery of the PRODUCTS if required for security, legal, regulatory or other compliances or obligations (such as statutory or accounting audits), or for defending legal claims or disputes.

CONTACT US

Any concerns or questions regarding this PRIVACY POLICY, may be addressed to info@mechademy.com with subject "Query".

While contacting MECHADEMY the CUSTOMER or USER must provide their name and contact details exactly as it appears on correspondence received from MECHADEMY or as specified in the AGREEMENT or PURCHASE AGREEMENT.

CHANGES TO PRIVACY POLICY

MECHADEMY reserves the right to update, modify, change, amend or cancel this PRIVACY POLICY at any time, without prior notice, in our discretion.

Upon modification, the revised PRIVACY POLICY will be uploaded on the TURBOMECHANICA PLATFORM.

Any use of the TURBOMECHANICA PLATFORM or PRODUCTS post uploading of the revised PRIVACY POLICY be deemed to constitute the CUSTOMERS' agreement to all revisions.

CUSTOMERS and USERS are responsible for periodic review of the latest version of the PRIVACY POLICY.

GOVERNING LAW

This PRIVACY POLICY is governed by the laws of the State of Texas, notwithstanding the jurisdiction and the location of the CUSTOMER or USER.

Any dispute arising on account of this Privacy Policy will be filed with the courts located in the state of Texas

COOKIE POLICY

The TURBOMECHANICA PLATFORM employs cookies which are necessary for the proper functioning of the TURBOMECHANICA PLATFORM and the PRODUCTS.

Cookies are small text files downloaded to USER'S device to assist websites in identifying the USER by allotting a unique identifying code to each device. Cookies are sometimes also utilized to "link" USER'S device to data hosted in an alternate place.

Data collected by cookies may include information on the pages visited, the time of visit, referring URL or IP address, browser type, query string, status of request, number of bytes in the response, and other relevant session information.

Cookies may be provided to MECHADEMY by a THIRD-PARTY, however only MECHADEMY shall be privy to the information collected.

THIRD-PARTY cookies may include re-marketing tracking cookies, such as those provided by Google AdWords. Such cookies allow MECHADEMY to showcase MECHADEMY's products outside of the TURBOMECHANICA PLATFORM to users who visit the TURBOMECHANICA PLATFORM.

MECHADEMY may use cookies to enhance USERS' experience, optimize PRODUCTS functionality, secure access to the TURBOMECHANICA PLATFORM or the PRODUCTS, remember log-in information, manage sessions, record statistics, track web traffic, analyze customer behavior and personalize content.

MECHADEMY shall not deploy any cookies that are capable of reading information from USERS' devices or that store any retrievable data on USERS' devices. MECHADEMY shall not use any cookies to collect any personally identifiable data.

MECHADEMY shall honor the USERS' preferences for receiving cookies. CUSTOMERS may use the "Help" tab in the toolbar of their browsers to get further information on restricting their browser from receiving cookies, or getting notifications upon receiving a new cookie, or deactivating cookies entirely. Certain features of the TURBOMECHANICA PLATFORM or the PRODUCTS may not work as intended if cookies are disabled.

LINKS TO THIRD-PARTY WEBSITES

During CUSTOMERS' or USERS' usage of the TURBOMECHANICA PLATFORM or the PRODUCTS, MECHADEMY may provide links to THIRD-PARTY websites. Such websites may have varying Terms of Service, Privacy Policies and Copyright Policies. CUSTOMERS are strongly advised to read the policies governing such THIRD-PARTY websites and be aware of the PERSONAL DATA collected by them, before using such a website.

This PRIVACY POLICY applies only to content, use, data collection and privacy relating to the TURBOMECHANICA PLATFORM.

USERS' RIGHTS

USERS may have additional rights pursuant to their local law applicable to the processing.

PERSONAL DATA applicable to EU individuals may be subject to the EU Privacy Legislation and consequential to the CUSTOMERS' or USERS' Rights. All individual subject to the GDPR, are advised to read the below section pursuant to their Privacy Rights.

GDPR COMPLIANCE: USERS' RIGHTS – INDIVIDUALS IN THE EUROPEAN UNION

Under GDPR, as an EU individual, USERS have the right to:

• Be informed about what happens to their PERSONAL DATA
• Access their PERSONAL DATA
• Update or correct their PERSONAL DATA
• Erase their PERSONAL DATA (to be forgotten)
• Object to direct marketing
• Request to have their PERSONAL DATA deleted or restricted
• Ask for portability of their PERSONAL DATA

The Right to be Informed and Access PERSONAL DATA

Upon request by a verified USER, MECHADEMY shall provide any information relating to USERS' PERSONAL DATA and MECHADEMY's processing of USERS' PERSONAL DATA in a concise, transparent, intelligible, and easily accessible from using clear and plain language.

The information shall be provided in writing or by other means, including, where appropriate, by electronic means within 30 days of a written request.

The Right to Update and Correct PERSONAL DATA

The USERS have the right to ask MECHADEMY to rectify any inaccurate or incomplete PERSONAL DATA on the TURBOMECHANICA PLATFORM.

If MECHADEMY has given USERS' PERSONAL DATA to any THIRD-PARTY, MECHADEMY will notify the THIRD-PARTY that MECHADEMY has received a request to rectify USERS' PERSONAL DATA, unless doing so proves impossible or involves disproportionate effort.

Such a THIRD-PARTY should also rectify the USERS' PERSONAL DATA they hold – however, MECHADEMY is not in a position to audit such a THIRD-PARTY to ensure that the rectification has occurred.

The Right to PERSONAL DATA

In some circumstances USERS may ask MECHADEMY to erase USERS' PERSONAL DATA stored on the TURBOMECHANICA PLATFORM.

If MECHADEMY receives such a request to erase USERS' PERSONAL DATA, MECHADEMY will keep a list of individuals who prefer to not be contacted in the future so that MECHADEMY does not contact such USERS with regard to any future correspondence (for a specified period or otherwise).

Third Party Usage of Data

If MECHADEMY has given USERS' PERSONAL DATA to any THIRD-PARTY, MECHADEMY will notify the THIRD-PARTY that MECHADEMY has received a request to erase USERS' PERSONAL DATA, unless doing so proves impossible or involves disproportionate effort.

Such a THIRD-PARTY should also rectify the USERS' PERSONAL DATA they hold – however, MECHADEMY is not in a position to audit such a THIRD-PARTY to ensure that the rectification has occurred

Withdrawing Your Consent

MECHADEMY may seek USERS' consent to process USERS' PERSONAL DATA (for example consent to receive marketing)

The USERS have the right to withdraw their consent at any time

Withdrawal of consent shall not affect the lawfulness of any processing carried out before such a withdrawal is received by MECHADEMY.

MECHADEMY may not be able to provide full functionalities of the TURBOMECHANICA PLATFORM or the PRODUCTS if the USERS withdraw their consent. A disclaimer to this effect shall be presented to the USERS at the time of processing the withdrawal of USERS' consent.

Accessing Account Information

Any PERSONAL DATA, which may contain personally identifiable information, shall be encrypted in transit and at rest.

USERS may request more information by sending an email to MECHADEMY at info@mechademy.com with subject "Query - GDPR Compliance"

CALIFORNIA ONLINE PRIVACY PROTECTION ACT

MECHADEMY does not share PERSONAL DATA about its CUSTOMERS or USERS with any THIRD-PARTY for the THIRD-PARTY's own marketing purposes.

California Civil Code Section 1798.83provides California residents the right to request from certain businesses with whom the California resident has an established business relationship a list of all THIRD-PARTIES to which the business, during the immediately preceding calendar year, has disclosed certain personally identifiable information for direct marketing purposes.

California law also affords California residents a right to opt out of the sale of your personal information. This right is applicable to the extent MECHADEMY is engaging in a sale of your personal information as defined under applicable law.

MECHADEMY is required to respond to such a request only once during any calendar year.

To exercise any rights available under California law, Users may email to MECHADEMY at info@mechademy.com with subject "Query - California Online Privacy Protection Act"

In the request, the USER is required to attest to the fact that the USER is a California resident and provide a current California address for MECHADEMY's response

Not all information sharing is covered by the California Privacy Rights requirements and only the information sharing that is covered will be included in MECHADEMY's response

More information on the California Act is available at: http://consumercal.org/california-online-privacyprotection-act-caloppa/#sthash.0FdRbT51.dpuf

If you choose to exercise your rights, MECHADEMY will not charge you different prices or provide different quality of services unless those difference are related to your personal information or otherwise permitted by law.

RIGHT TO LODGE A COMPLAINT

In case of a concern with regard to MECHADEMY's privacy laws or in case a USER is an EU individual and subject to the GDPR or in case a USER considers MECHADEMY's processing of their PERSONAL DATA to be non-compliant with the applicable data protection laws, the USER may lodge a complaint by sending an email to MECHADEMY at info@mechademy.com with subject "Query – Privacy Compliance".

Subject to the EU General Data Protection Regulation ("GDPR"), USER may also contact the Data Protection Authorities in the European Union for assistance using this link: https://ec.europa.eu/justice/article-29/structure/data-protection-authorities/index_en.htm

DISCLOSURE OF INFORMATION

MECHADEMY does not sell the USERS' PERSONAL DATA.

MECHADEMY does not disclose USERS' PERSONAL DATA to any THIRD-PARTY outside the following exceptions:

• If the USER explicitly consents to have their information shared
• To comply with legal proceedings, laws, or other regulations
• If MECHADEMY needs to investigate or otherwise take action regarding illegal activities or violations of MECHADEMY's terms, PRODUCTS, rights, or property
• If a THIRD-PARTY requires access to USERS' PERSONAL DATA to facilitate the functionalities of the TURBOMECHANICA PLATFORM or the PRODUCTS.

DATA PROCESSING ADDENDUM

This Data Processing Addendum (this "DPA") states the rights and obligation of Mechademy and Customer concerning the protection of personal data and applies to personal data processing activities subject to GDPR (defined below).

1. DEFINITIONS

Capitalized terms used and not otherwise defined herein have the meaning given to them in the TURBOMECHANICA GENERAL TERMS AND CONDITIONS, TURBOMECHANICA PRIVACY POLICY and any PURCHASE AGREEMENT (collectively, the "AGREEMENT").

1.1. References to Personal Data, Data Subject, Data controller, Data Processor, Processing, or Personal Data Breach have the meanings ascribed to them under the Data Protection Legislation.

1.2. "Customer Personal Data" shall mean the Personal Data that is uploaded into the PRODUCTS or otherwise provided to MECHADEMY or its representatives pursuant to the delivery of PRODUCTS pursuant to a valid license or other agreement with the Customer.

1.3. "Data Protection Legislation" shall mean (i) the General Data Protection Regulation ((EU) 2016/679) ("GDPR") and any national implementing laws, regulations and secondary legislation, as amended or updated from time to time, and then (ii) any successor legislation to the GDPR.

1.4. "Standard Contractual Clauses" shall mean the standard contractual clauses for the transfer of Personal Data from the European Union to processors established in third countries (controller-to-processor transfers), as set out in the Annex to Commission Decision 2010/87/EU.

2. DATA PROTECTION

2.1. This DPA shall only apply to the extent the Data Protection Legislation applies to PRODUCTS and services rendered pursuant to the AGREEMENT. To the extent the Data Protection Legislation applies, then this DPA shall form a part of and become incorporated therein with the terms and conditions of the AGREEMENT.

2.2. Each PARTY shall comply with all applicable requirements of the Data Protection Legislation. This Section 2.2 is in addition to, and does not relieve, remove or replace, a PARTY's obligations under the Data Protection Legislation.

2.3. The PARTIES acknowledge that for the purposes of the Data Protection Legislation, the Customer is the Data Controller and MECHADEMY is the Data Processor. The following set out the details of the Data Processing to be undertaken by MECHADEMY.

• Scope: Processing of the Customer Personal Data pursuant to delivery of the PRODUCTS.
• Nature of processing: Transfer, storage and such other processing activities that are specified by the Customer pursuant to the PRODUCT terms and conditions.
• Purpose of processing: The provision of PRODUCTS to the Customer.
• Duration of the processing: The duration set forth in a valid agreement in place with the Customer unless otherwise required by law.
• Types of Personal Data: The Customer Personal Data which may include but not be limited to Name, Email address, Phone number, Device ID (with data about the vendor, version & features of the device), IP address and/or Postal code.
• Categories of Data Subject: The Customer's customers, employees, suppliers.

2.4. Without prejudice to the generality of Section 2.2, the Customer will ensure that it has a legal basis for processing, including all necessary and appropriate consents and notices, to enable the lawful transfer of the Personal Data to MECHADEMY for the duration and purposes of this AGREEMENT.

2.5. MECHADEMY shall process the Customer Personal Data only on the written instructions of the Customer (as detailed in Section 2.3 above) unless MECHADEMY is required by the laws of any member of the European Union or by the laws of the European Union applicable to MECHADEMY to process Personal Data ("Applicable Laws"), which shall be undertaken upon notice to the Customer (where permitted). Confirming acceptance to these terms shall constitute the Customer's written instructions for MECHADEMY to undertake the processing detailed in Section 2.3.

2.6. MECHADEMY shall ensure that it has in place appropriate technical and organizational measures, to protect against unauthorized or unlawful processing of Personal Data and against accidental loss or destruction of, or damage to, Personal Data, appropriate and proportionate to the harm that might result from the same, having regard to the state of technological development and the cost of implementing any measures.

2.7. MECHADEMY shall, in relation to any Customer Personal Data processed, in connection with the performance by MECHADEMY of its obligations under this AGREEMENT:

2.7.1. ensure that all personnel who have access to and/or process Personal Data are obliged to keep the Personal Data confidential; and

2.7.2. not transfer any Personal Data outside of the European Economic Area unless the prior written authorization of the Customer has been obtained and the following conditions are fulfilled:

• (a) The Customer or MECHADEMY has provided appropriate safeguards in relation to the transfer which shall include use of the Standard Contractual Clauses or confirmation that such transfer is made subject to the EU-US Privacy Shield (as applicable);
• (b) The data subject has enforceable rights and effective legal remedies;
• (c) MECHADEMY complies with its obligations under the Data Protection Legislation by providing an adequate level of protection to any Personal Data that is transferred;
• (d) MECHADEMY complies with reasonable instructions notified to it in advance by the Customer with respect to the processing of the Personal Data; and
• (e) Taking into account the nature of the processing and the information available to MECHADEMY, assist the Customer, at the Customer's cost, in responding to any request from a Data Subject and in ensuring compliance with its obligations under the Data Protection Legislation with respect to security, breach notifications, impact assessments and consultations with supervisory authorities or regulators, as applicable;

2.7.3. notify the Customer without undue delay on becoming aware of a Personal Data Breach;

2.7.4. at the written direction of the Customer, delete or return Personal Data and copies thereof to the Customer on termination of the AGREEMENT unless required by Applicable Law to store the Personal Data; and

2.7.5. maintain complete and accurate records and information to demonstrate its compliance with this Section 2.7 and allow for audits by the Customer or the Customer's designated auditor.

2.8. The Customer consents to MECHADEMY appointing THIRD-PARTY processors of Personal Data under this AGREEMENT. MECHADEMY confirms that it has entered or (as the case may be) will enter with the THIRD-PARTY processor into a written agreement incorporating terms which are substantially similar to those set out in this DPA.

© 2025 Turbomechanica. All Rights Reserved.