MENZA EMPIREDIGITAL OPERATIONS
Digital operations · E-commerce

Clearer conversations.
Better control.

We develop internal tools to manage comments on the pages and advertisements administered by MENZA EMPIRE. The platform connects conversations with moderation rules, human review and a record of decisions.

Explore the application How we use APIs

Internal access for authorized administrators. This website does not connect visitors’ social accounts.

Example workflowIllustrative data
Demonstration comment
“How can I return the product?”
Support request
Sent for human review

Context is reviewed before a decision. Classification does not confirm an action.

Processing logClassification → review

Illustrative example; not a real comment or a confirmed action.

Authorized accountsOnly assets for which administrative access has been granted.

Traceable decisionsProposals and confirmed outcomes are recorded separately.

Human controlPause, simulation and review of cases that need attention.

01 / The application

One workspace for
e-commerce conversations.

The application organizes comment moderation and support requests. It is not a general-purpose social account management service.

01

Comment organization

Brings together comments available through the API for authorized pages, posts, accounts and ads. Preserves the platform and source association so administrators can understand the context.

02

Classification and prioritization

Uses rules and, when configured, AI classification to identify spam, abusive language, product questions, delivery or return requests and uncertain cases.

03

Review and intervention

Provides a human review queue and per-page controls. Hiding, replying or deleting is possible only where the integration, granted permissions and application settings allow it.

04

Logs and reporting

Records decisions, attempts, API responses and outcomes. Supports operational history and exports. Simulations and errors are not represented as confirmed deletions.

02 / Workflow

From a comment
to a decision with context.

The workflow preserves data provenance and separates detection from execution. API inventories may be incomplete; reports reflect information available when the source was checked.

01

Authorization

An administrator configures access to accounts and pages they are entitled to manage.

02

Collection

Comments arrive through webhooks or API reads, retaining their page or advertisement context.

03

Analysis

Rules and classification produce a category, confidence level and proposed action.

04

Review

Support cases and uncertain decisions can be examined by an administrator.

05

Action & audit

Only permitted actions are executed. Confirmed outcomes are recorded separately from attempts.

03 / API access

Purposeful access.
Clearly defined capabilities.

Integrations support internal operations for administered business assets. Each platform has its own permissions, limits and access requirements.

Meta

Existing integration

The Meta integration is used for Facebook Pages and Instagram accounts that are configured and authorized in the platform.

  • Receives comment events through webhooks and reads content available through the API.
  • Associates comments with the authorized page, post or media and classifies them.
  • Manages comments and replies according to permissions and each page’s operating mode.
  • Provides human review, history, reports and visibility into access errors or API limits.

Configuring a page does not automatically enable Live moderation. Capabilities depend on account permissions and application controls.

TikTok

In development · access pending

We are preparing a TikTok API for Business integration to manage comments from our own authorized advertising accounts.

  • An OAuth flow prepared for administrator connection, including state validation and error handling.
  • Reading authorized accounts, selected ads and comments, with pagination and deduplication.
  • Classification, rules, review queues, archiving and reports tested using mock adapters.
  • Preparation of hide, restore and delete actions, without enabling real execution.

We do not represent the TikTok integration as approved or live in production. Demonstration data is clearly separated; real reads and actions are not enabled in the current workflow. Real connection depends on TikTok approval and granted permissions.

Why do we request API access?

To identify authorized assets, read and organize their comments, support human review and, only after configuration and authorization, manage comments under applicable rules. The project is not intended to extract data from unauthorized accounts, publish advertising campaigns or manage advertising payments.

04 / Operational control

Automation with
visibility and boundaries.

Automated classification is a working aid. A category or score does not demonstrate that an action was executed and does not replace contextual review.

Explicit operating modes

Pages can be paused or placed in simulation. Live actions require appropriate configuration and authorization.

Visible support cases

Questions about orders, delivery, products and returns can be flagged for human review and follow-up.

Errors are not outcomes

A timeout, API rejection or uncertain result remains an issue to investigate. It is not reported as a successful deletion.

Controlled processing pace

Bounded batches, pauses and overlap prevention are used. API limits and the available level of access must be respected.

05 / Data & transparency

Relevant data.
A clear operational purpose.

Depending on the integration, the platform may process comment text, account, ad, post or media identifiers, author information provided by the API, observation timestamps and moderation outcomes.

Tokens and private configuration are managed server-side, outside public pages. The operational dashboard requires authentication. If external AI classification is used, text needed for analysis may be sent to the configured provider; this must be considered when managing the data.

Comment textSource & account IDsAPI-provided authorCategory & decisionOutcome & audit log
Data information ↗Request data deletion ↗
Frequently asked questions

What you should
know.

Is this a public account-connection service?

No. The platform described is an internal tool for administered commercial operations. This website explains the application; it does not offer social login or connect visitors’ accounts.

Is TikTok already connected and approved?

We do not claim TikTok approval. The module is in development and is tested with synthetic data. Integration validation and required approvals precede activation of real access.

Does every negative comment get deleted automatically?

A negative classification is not confirmation of deletion. The application includes rules, thresholds, human review and per-page controls; uncertain cases and support requests need attention. Real TikTok actions are blocked at the current stage.

Does an API scan cover a platform’s entire history?

This cannot be guaranteed. Deleted, unavailable or permission-restricted data may be missing. Reports must be read in the context of the sources scanned and the exceptions recorded.

How can I ask about or request deletion of data?

Email contact@menzaempire.ro with enough context to identify the case: the platform, page and comment link, if available. Do not send passwords or access tokens. The data-request page explains the steps.

Direct contact

Questions about the application
or the use of data?

For technical details, API integration review or data-related requests, contact us by email.

contact@menzaempire.ro