whats-best.ai
Search Sign in

Social Media Marketing

NapoleonCat

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by NapoleonCat sp. z o.o. · napoleoncat.com

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

Notes that every comment and message arriving from a network is personal data the company now processes. Wants a DPA that addresses that squarely, retention on the conversation archive, and an answer on where the sentiment analysis sends the text.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Publishing & calendar

How this is scored

Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails at 3am.

0 — One post to several networks at once with no per-network variation and no calendar.

3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.

5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.

8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.

10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.

Report an error

The Data Protection Officer

The publishing pages show a drag-and-drop content calendar with drafts, scheduled first comments on Instagram, carousels and Stories, batch image upload, campaign labels and best-day-and-time guidance. We found no public information on bulk CSV import, queue-based or evergreen scheduling, previews matching each network's rendering, or what happens when a scheduled post fails overnight — the failure story is the part I need before calling this dependable. 2 3 7 9

Report an error

Engagement & community inbox

How this is scored

Comments, mentions and messages in one queue — the half of the job that is customer service wearing a marketing badge.

0 — No inbox; engagement happens in each native app.

3 — Mentions and comments listed per network with no assignment, no status and no history.

5 — A unified inbox across the connected networks with assignment, status and internal notes, and the conversation history visible per person.

8 — Direct messages included where the API allows, saved replies, SLA timers, sentiment or priority flags, spam and hidden-comment handling, and escalation to a helpdesk.

10 — The inbox is a service desk: every public and private interaction in one queue with ownership and response-time reporting, moderation rules that act automatically, and a per-person history spanning networks.

Report an error

The Data Protection Officer

A unified inbox across Facebook, Instagram, TikTok, LinkedIn, YouTube and Messenger, taking private messages, comments, mentions and reviews, with assignment, tickets, internal notes, sentiment tagging, priority sorting, automatic spam and hate-speech removal, per-person Social CRM profiles and response-time reporting — this is close to a service desk. We found no public information on SLA timers or escalation into a helpdesk, and nothing on how long the conversation archive of customer personal data is retained. 1 4 7 9 10

Report an error

Analytics & reporting

How this is scored

Measurement across networks with different metrics and retention windows, plus the reporting an agency hands a client.

0 — Per-network vanity counts pulled live; no history kept.

3 — Basic post and profile metrics with a short history and no cross-network comparison.

5 — Metrics stored beyond the networks' own retention, cross-network comparison, competitor benchmarking, and scheduled exports.

8 — Custom dashboards, white-label client reporting, paid and organic combined where the API allows, UTM-based attribution into web analytics, and audience demographics over time.

10 — Reporting answers what worked and why: metrics normalised across networks with the differences documented rather than hidden, full historical retention independent of platform windows, and exports an agency can hand over unedited.

Report an error

The Data Protection Officer

Custom dashboards, white-label scheduled PDF reports with configurable branding, time frames, metrics and language, competitor benchmarking, audience demographics and UTM tags into Google Analytics are all documented. The captured pages give different figures for which networks reports cover — Facebook and Instagram in one place, Facebook, LinkedIn and Instagram in another — and we found no public information on retention of metrics beyond the platforms' own windows or on paid combined with organic. 1 2 6 7

Report an error

Approvals, roles & brand safety

How this is scored

How a team of several people and an agency publish to a brand account without an accident — and who can be shown to have approved what.

0 — Shared login, no roles, no approvals.

3 — Separate users with a coarse admin split and an optional single approval step.

5 — Roles per network and account, multi-step approval workflows, comments on drafts, and an activity log.

8 — Client or brand workspaces with strict separation, configurable approval chains including legal review, content locking after approval, and an audit trail of who changed and published what.

10 — Governance a regulated brand could pass an audit on: complete audit trail of edits, approvals and publications, enforced approval before anything reaches a network, granular permissions per account and action, and no shared credentials anywhere in the design.

Report an error

The Data Protection Officer

Roles and permissions with an approval step, including sending content to clients for approval, plus task assignment and team monitoring, are documented. We found no public information on multi-step approval chains, content locking after approval, or an audit trail of who changed and published what — and for a tool holding customer conversations as personal data, that trail is the governance I look for and cannot see. 2 6 8 9

Report an error

Network coverage & API resilience

How this is scored

Which networks are supported through official APIs, how quickly the vendor follows platform changes, and what the customer keeps when a network breaks or leaves.

0 — A few networks, some through unofficial means, with no statement about API status or platform changes.

3 — The major networks through official APIs, but feature gaps undocumented and platform changes communicated after they bite.

5 — Official API integrations across the main networks with the per-network limitations documented, and a changelog when platform behaviour changes.

8 — Broad official coverage including the newer networks, a public status page for integrations, advance notice of deprecations, and full export of the customer's own publishing and engagement archive.

10 — Platform dependency handled as an engineering commitment: official partner status where it exists, per-network capability documented and kept current, rapid response to API changes with the history to show it, and an archive that stays the customer's whatever a network does next.

Report an error

The Data Protection Officer

Coverage spans Facebook, Instagram, TikTok (business and private accounts), LinkedIn, YouTube, Google My Business, Messenger and app-store reviews, with X named on the publishing page, and some per-network limits are documented openly — no video publishing on YouTube, reports limited to a set of networks, and profiles over one million followers requiring support. We found no public information on a public integration status page, advance notice of deprecations, a changelog, or export of the customer's publishing and engagement archive — that archive is the customer's record of personal data, and its portability is unaddressed. 1 2 4 9 10

Report an error

European sovereignty

How this is scored

Where the archive and the community conversations are processed, who the contracting entity is, which subprocessors touch them. Independently sourced by the sovereignty pipeline. Note that the networks themselves are non-EU by definition — this criterion judges the tool, not the platforms it talks to.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — AI features, analytics, support tooling — are non-EU without an explained safeguard.

8 — EU or DACH hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and the handling of message content from the networks described with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a DPA that squarely addresses the personal data arriving from the networks in comments and messages.

Report an error

The Data Protection Officer

The sovereignty record for this vendor carries no attributes at all: I found no public information on where the archive and community conversations are processed, on hosting, on any subprocessor list, on a DPA addressing the personal data arriving in comments and messages, or on retention of the conversation archive. The vendor's own pages describe AI sentiment tagging and auto-moderation running over comment text with no statement of where that text is sent for analysis. The Polish legal form in the vendor name is the only European signal in the material, and it is not a safeguard. 1 4 10

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a team can compute the real annual invoice for their account and user count — including the tier where approvals and the inbox begin — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A per-user headline exists, but the number of social accounts included, or the tier where approvals and the inbox appear, is unstated.

5 — Per-user or per-account prices public with billing period stated, but at least one commonly needed capability (inbox, approvals, reporting) sits in an unpriced tier.

8 — Every tier priced publicly with account and user limits, feature boundaries, the cost of an extra account or seat, minimum term and VAT treatment stated.

10 — Complete price computability: annual invoice derivable for a given number of social accounts, users and client workspaces, with every add-on priced.

Report an error

The Data Protection Officer

A plan comparison page exists but the captured pages show no prices on it, and no monetary figure appears in the public material we reviewed, so a team cannot compute an annual invoice from these pages. The trial terms are unusually specific — five seats, ten social profile slots, a 25,000-message inbox capacity — but the tier where approvals and the inbox begin is unpriced, as is the cost of an extra account or seat. 1 6 10

Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about NapoleonCat? Tell us Report an error on this page

Sources (10)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page napoleoncat.com Checked 22 Sep 2026 Details →
  2. 2 Publishing & calendar — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  3. 3 Publishing & calendar — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  4. 4 Engagement & community inbox — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  5. 5 Engagement & community inbox — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  6. 6 Analytics & reporting — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  7. 7 Analytics & reporting — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  8. 8 Approvals, roles & brand safety — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  9. 9 Network coverage & API resilience — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →
  10. 10 Network coverage & API resilience — found from sitemap napoleoncat.com Checked 1 Oct 2026 Details →