Trust
Cenelira is a controlled publishing system for social posts. It refuses a post whose destination account is unclear, ties each approval to the exact version the reviewer saw, records every publishing failure with a named cause, and keeps a proof record for every scheduled post, which a PDF export signs. This page lists what ships today, how to reach support, and the claims Cenelira does not make.
Every claim below comes from repository constants or from files named on a linked page. The page shows no customer logos, ratings, testimonials or rankings against competitors.
Cenelira schedules posts, checks each destination, ties approval to the exact version, names the cause of every failure and keeps a proof record for every schedule, which a PDF export signs. What it produces is a record you can check, rather than a count of posts sent.
It serves agency operators who run publishing across several platforms for clients, and brand teams who need a record of who approved which version for which destination and what happened at publish.
Cenelira ships the mechanisms linked from this page. It does not claim SOC 2, ISO 27001, HIPAA or GDPR certification, it guarantees no audience outcome, and it does not compete on customer logos.
Entity
The product name and support contact are constants in src/lib/brand.ts, and the declared scope covers everything the public mechanism pages on this site describe.
Cenelira
Controlled scheduling, approvals, publishing, recovery and proof export, signed as a PDF, across these platforms: Instagram, Facebook, Threads, LinkedIn, YouTube, TikTok, Pinterest, X.
What ships
Each link below describes a mechanism that runs when a post publishes or when proof is exported. The linked pages name the code that enforces each behaviour, so this page only points to them.
Six named refusals at publish time when the saved destination account is missing or invalid. Each refusal returns HTTP 409 target_repair_required.
External review decisions are bound to the schedule's SHA-256 reviewVersion fingerprint, which covers its content, settings and verified media. A change made after the link is issued and before the decision is saved marks the link SUPERSEDED.
Twenty-one named causes of a publishing failure, mapped to nine next actions and six kinds of owner. Replay is offered when the cause and the replay check allow it.
The manual-completion workflow that runs when a schedule's publishMode or status is HANDOFF. It has seven named reasons and two states, pending and completed.
A 17-field record for every schedule, exported as a signed PDF or as an unsigned CSV file. The PDF signature is an HMAC-SHA256 of its canonical payload, and the signing secret is never written into the file.
Who this is for
Cenelira helps most where an approval of the version someone read must be kept apart from a general yes, and where every failure needs an owner. It helps less when a team wants a high-volume queue and has no need for an audit trail.
Proof export
Each mechanism above ends in the same place: a row in the 17-field proof record. The PDF export is signed, the unsigned CSV export is not, and both carry every column. A verifier can recompute the PDF's HMAC-SHA256 signature from its canonical payload, and the signing secret is never written into the file.
The proof export records scheduleId, versionFingerprint, targetAccount, platform, publishAtISO, approverIdentity, approverSource, approvalTimestamp, invalidationReason, publishOutcome, publishedAtISO, platformPostId, exceptionCause, recoveryAction, recoveryActor, deliverySetId, and deliverySetMemberCount.
The proof page explains how to verify a PDF: copy the canonical payload, recompute its SHA-256 digest, then recompute the HMAC-SHA256 with the shared signing secret and compare the result with the printed signature.
The proof export makes no claim about audience, reach or the identity of external reviewers. It records the state of each post's workflow and what the platform answered.
Support
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock cover, instant response SLAs or dedicated success managers. Requests for a vendor questionnaire, a security pack or a data processing agreement are answered case by case at the same address.
Public limitations
Each row below is a limit of a mechanism that already runs when a post publishes or when proof is exported.
External reviewers approve through a review link. On a shared link their identity is self-declared: they type their own name and email, which Cenelira does not verify. A saved client contact on a personal link is identified only by holding that link. Only internal workspace approvals are tied to a workspace user account.
Nothing in the proof export, the recovery pages or any public claim on this site describes audience, delivery or reach. The proof record reports what the platform answered and the state of the workflow, and it holds no impression counts.
Wrong-account prevention runs at publish time on schedules created in Cenelira. It does not retroactively audit posts that predate the connection.
Every supported platform has an auto-publish path. LinkedIn posts with several images currently go through the manual handoff path, and the handoff pack records who completed the manual publish. This is a current routing choice rather than a permanent platform limit.
Cenelira makes no public claim today about SAML SSO, SCIM provisioning, audit-log retention SLAs or a choice of data residency for a workspace. Procurement requirements are handled directly by email.
Does not claim
Vendors in this category often use the language below loosely. Cenelira states on this page that it makes none of these claims, so a procurement reviewer does not have to ask.
Cenelira does not claim SOC 2, ISO 27001, HIPAA or GDPR certification. What ships instead is the set of publish-time refusals, version-bound approvals, owned recovery and proof export named on this page.
Cenelira does not promise reach, delivery, engagement or any other audience outcome. A publish either succeeds, with the platform's post id where the platform returns one, is refused for a named reason, or is recorded as a failure with a named cause.
The site shows no customer logos, testimonials, aggregate ratings or review markup. It describes what is true today.
Cenelira does not publish ranked comparisons against named competitors. The mechanism pages on this site describe what Cenelira does and name the code behind it.
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock cover, instant response SLAs or dedicated success managers.
Unknown / deferred
A careful reader might expect a trust page to declare each item below. Cenelira has not published values for them, and each row says what is missing and where to ask.
The legal entity name, registration jurisdiction and postal address are not published on this site today. Procurement contacts who need them should email [email protected].
Cenelira does not publish sameAs links to social profiles, press pages, or public registries. The Organization JSON-LD on the trust and home pages carries no sameAs array.
Vendor questionnaires, security review packs and data processing agreements are handled case by case by email, and none is published as a download on this site.
FAQ
Cenelira is a controlled publishing system for social posts that refuses unclear destinations, ties each approval to the exact version, names the cause of every failure and keeps a proof record for every schedule, which a PDF export signs.
Cenelira is built by a small team. The legal entity name, registration jurisdiction and postal address are not published on this site today, and procurement questions go directly to [email protected].
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock cover, instant response SLAs or dedicated success managers.
You export the proof archive. Each proof record carries 17 fields, including approval, target account, platform, publish outcome, exception, recovery and delivery-set columns. You can download it as a signed PDF or as an unsigned CSV file, and the proof page explains how to verify the PDF.
Cenelira makes no public claim today of SOC 2, ISO 27001, HIPAA or GDPR attestations. What ships instead is the set of publish-time refusals, version-bound approvals, owned recovery and proof export named on this page.
Cenelira supports controlled scheduling and publishing on eight platforms, each with an auto-publish path: Instagram, Facebook, Threads, LinkedIn, YouTube, TikTok, Pinterest, X. LinkedIn posts with several images currently go through the manual handoff path described on the handoff packs page.
No. On a shared Cenelira review link, reviewer identity is self-declared, because the reviewer types their own name and email. A saved client contact on a personal link is identified only by holding that link. Internal approvals are tied to workspace user accounts, and the version-bound approval page describes how each decision is bound to the SHA-256 reviewVersion when it is saved.
Every claim on this page comes from repository constants or from files named on the linked mechanism pages. The page carries a last-reviewed date, and when a mechanism ships or its scope changes, the facts file, the link and the date are updated.
Last reviewed 2026-04-25
