Flow Intellectual Property
This page describes how intellectual property ownership is separated between the Microbe Studio platform and automation workflows, referred to in this document as Flows.
This is a supplementary product documentation page. Use of Microbe Studio remains governed by the official Terms of Service, Privacy Policy, and Refund Policy on the main website.
0. Relationship to Official Policies
The Flow-related content on this page should be read together with:
- Terms of Service: terms governing use of the Service, Tokens, License Packages, Protected Flows, and intellectual property.
- Privacy Policy: how Microbe Studio handles account, device, license, transaction, and technical data.
- Refund Policy: refund eligibility for Tokens, License Packages, and Protected Flows.
If there is any difference between this page and the official policies on the main website, the official website policies take precedence.
1. Microbe Studio Ownership
Microbe Studio owns all intellectual property rights related to the platform, including but not limited to:
- Software source code.
- System architecture and platform structure.
- Application interface.
- APIs and integration mechanisms.
- Workflow building tools, including Flow Builder.
- Core software components used to run, test, store, and execute Flows.
These rights belong to Microbe Studio and are not transferred to Partners, Customers, or any third party unless otherwise agreed in writing.
2. Partner Ownership of Flows
In this document, a Flow includes the scenario design, configuration logic, template content, node configuration, and arrangement of steps configured by a Partner on the Microbe Studio platform.
The intellectual property rights to Flows created by a Partner belong exclusively to that Partner. Microbe Studio may not copy, sell, distribute, or transfer those Flows to any third party without the Partner's written consent.
3. Flow License for End Customers
When a Partner sells or provides a Flow to an End Customer, the Partner grants the End Customer the right to use that Flow on the Microbe Studio platform.
This usage right is:
- Non-exclusive.
- Non-transferable.
- Limited to the designated account, Workspace, or organization.
- Valid only during the active term of the software subscription or commercial agreement between the End Customer and the Partner.
The End Customer may not commercially copy, resell, redistribute, or transfer access to the Flow to another account, individual, or organization without the Partner's written consent.
4. Service Components
When using Microbe Studio, a Customer may interact with two separate intellectual property components:
| Component | Owner | Description |
|---|---|---|
| Platform | Microbe Studio | Source code, interface, APIs, Flow Builder, execution mechanism, and platform tools. |
| Flow | Partner | Logic, processing steps, template content, node configuration, and workflow arrangement configured by the Partner. |
Being granted the right to use a Flow does not give the Customer ownership of the Flow or ownership of the Microbe Studio platform.
5. Prohibited Actions Related to Flows
Customers agree not to directly or indirectly perform the following actions:
5.1. Copying Flow Structure
Customers may not take screenshots, record videos, document logical structure, or use technical tools to copy a Flow configuration in order to recreate it on another account or another platform.
5.2. Unauthorized Commercialization
Customers may not resell, rent, gift, distribute, or transfer activation codes, access rights, or usage rights for a Flow to any individual or organization outside the licensed scope.
5.3. Reverse Engineering
Customers may not intentionally interfere with source code, APIs, configuration data, or platform mechanisms to extract, reconstruct, or reproduce the data structure of a Flow without written consent from both the Partner and Microbe Studio.
6. Technical Protection Mechanisms
Microbe Studio may build technical mechanisms to protect Flows that a Partner marks as Exclusive, including but not limited to:
- Flow data encryption.
- Hiding detailed Flow structure.
- Limiting the ability to view, copy, or export Flow data.
- Controlling access by account, Workspace, or organization.
These mechanisms are intended to reduce unauthorized copying of Partner-owned Flows by customer accounts or other partners.
7. Termination of Usage Rights
If a Customer violates this page or terminates the service agreement with the Partner, Microbe Studio may, at the request of the owning Partner or under platform policy:
- Revoke access to the Flow.
- Freeze or remove the infringing Flow from the Customer's Workspace.
- Suspend or terminate access to features related to the infringing Flow.
If the violation is caused by the Customer, software fees related to the remaining subscription period may be non-refundable, depending on the applicable commercial terms.
8. Indemnification
If a Customer unlawfully copies, distributes, or commercializes a Partner's Flow and causes commercial damage, the Customer is responsible for compensating the Partner for actual damages incurred.
In addition to indemnification, the Customer may be subject to remedies under applicable intellectual property laws in Vietnam and related agreements between the parties.