INLOCAL / SERVICE GUIDE
How we verify publishing
Understand publication records, human confirmation, observed metrics and fictional previews before judging INLOCAL results.
Reviewed
A request is not a published post
A submitted clip awaits review. Approval means it is ready for the publication workflow, not that it is already public. A person performs the final Post action. The customer’s Published state requires the recorded post link and publication time through the reviewed workflow.
What the publication record proves
The workflow binds the customer request to an operator-confirmed publication record with a URL and time. Operational receipts retain media and caption hashes and the device reference. Private device identifiers and operator identities are not published as customer proof. A receipt is evidence of the recorded operation, not an independent platform audit.
How to read performance data
Use the recorded value and its observation time when available. Missing measurements are not zero. A current cumulative view count is not daily growth or proof of sales. We do not infer a missing history or a causal effect from operating in a particular country.
Samples, corrections and limitations
The public workspace preview uses fictional accounts and is labeled as a sample. It is not a customer case study. If a record looks wrong, send the team the request title and published link through the agreed support channel. Reach, followers and sales are not guaranteed. Local operation describes how the work is performed, not a ranking advantage. We do not provide likes, follows or comments. Content production and advertising spend are separate.