Company · About

About MatrixHubx

Last updated: November 12, 2026 · This page only states what can be verified

About MatrixHubx

MatrixHubx is a multi-platform content operations platform operated by Hubei Leyi Times Engineering Co., Ltd., built for teams that have to publish overseas platform content.

MatrixHubx uses Google API Services only to connect a YouTube channel authorized by the account owner, upload videos that the user has created and approved, and read basic channel and video information for display. We do not sell Google user data, use it for advertising, or use Google APIs to generate or distribute non-consensual intimate imagery (NCII). MatrixHubx is a content distribution and management tool; it does not provide AI generation of images, video, or music.

It pulls one chain of work into a single workspace: material and version management, human approval, publishing through platform official APIs, public engagement handling after publishing, and data plus lead hand-back. The point is not one more tool — it is fewer hand-offs. Every hand-off you remove is one less thing lost, one less post sent from the wrong account, and one less decision nobody can reconstruct afterwards.

The "matrix" in the name means one team running many platforms, many accounts and many brands at the same time. Those teams usually already have a scheduling sheet, a group chat and a cloud drive. What they are missing is the layer that connects them and keeps a record.

The problem we solve

• Material sits across drives, chat logs and different people's local folders, and versions are told apart by file names;
• publishing is done by manually switching accounts and platforms, so "who posted what, when" has to be reconstructed from chat history;
• when accounts and brands are handed over between people, there is no record of which platform permissions were granted and revoked;
• every platform dashboard reports numbers differently, so one consolidated report means several exports;
• teams want to automate the flow but do not dare let a program publish on its own.

Our answer is written into the product structure: machines move things, people decide. Nothing enters the publishing queue without a person confirming it, while moving, logging and reading back is the system's job.

What we do

• Material and versions: one intake, per-platform checks on title length, cover ratio and video duration, version history kept.
• Approval and publishing: content requires human confirmation before it leaves; publishing goes through each platform's official OAuth API, in throttled waves, and stops automatically on anomalies.
• Engagement handling: public comments and mentions visible inside your granted scopes land in one inbox, and every reply is sent after a person confirms it.
• Data and leads: publishing results, platform engagement data and leads return to the workspace; bills, audit logs, the lead pool and your own reports export to CSV / JSON.
• Open interfaces: MCP, REST OpenAPI, Webhook and n8n / Make nodes, so you can adopt just one segment of the chain.
• Text polish suggestions: text-level polish suggestions only, and nothing enters the publishing queue without human confirmation.

What we will not do

Delivery forms

Billing runs per subscription term, per use or by capacity. Live prices and the USD conversion are stated on the pricing page and in the Credits module — this page states no fixed prices.

Platform coverage

12 overseas platforms today, all connected through official authorization interfaces:

Platform trademarks belong to their owners; MatrixHubx has no affiliation with or endorsement from these platforms.

Data and compliance

• Data is stored isolated per workspace, with credentials encrypted field by field;
• every action is logged: who published what, from which account, when, and who approved it — retrievable within the retention policy;
• data flows are designed for GDPR; user rights, international transfers and retention periods are in the Privacy Policy;
• processing standards for business data, the sub-processor list and deletion windows are in Section 6 of the Privacy Policy;
• Meta permissions and their purposes are disclosed one by one in the platform review brief and the Privacy Policy appendix;
• deletion requests can be submitted through the Data Deletion Instructions page, or by contacting us under Section 12 of the Privacy Policy.

Numbers we publish, and numbers we do not

Structural numbers that can be checked are stated plainly:

• 12 overseas platforms and 3 delivery forms;
• workspace modules and navigation groups follow the live interface;
• the operating entity, registered address and ICP filing number are in the next section.

Effect metrics we cannot have audited — registered users, paid conversion, total posts published, account availability, hours saved — stay off this page. Business data shown in the interface is illustrative and is not a measurement or a performance promise.

Company and filings

Contact us

• Sales and partnerships: matrixhubx@matrixhubx.com (demos, onboarding, quotes, channels and press)
• Technical support: support@matrixhubx.com (account authorization, publishing failures, data read-back and billing)
• Privacy and data-rights requests: contact us under Section 12 of the Privacy Policy; to protect your information we may first verify your identity
• Response window: within 2 business days; refunds and billing follow the Refund Policy

Including the workspace name, the platform account and when it happened saves a round trip.