Incognia review

Incognia is a fraud-detection and identity service for companies that need to recognize users across devices. Its Incognia ID combines location intelligence, device identity and app security, using those signals to help identify account takeover, account abuse and other fraud risks while reducing friction for users it considers trusted.

The product is built around signals that can persist beyond a single app session. Incognia says it can recognize devices after app reinstalls and recognize users across devices. It also includes tamper detection as part of its fraud intelligence. That makes it a specialist identity layer, not a general-purpose marketing or analytics platform.

For teams comparing fraud tools, the central question is whether these location and device signals fit their risk decisions and existing systems. The published product information describes what Incognia aims to identify, but does not publish detection rates or quantified reductions in fraud or friction.

Incognia’s clearest strength is the combination of identity signals. Rather than relying on a device identifier alone, Incognia ID brings together location intelligence, device identity and app security. That gives fraud teams several kinds of information to use when assessing whether a user or activity looks risky.

The product information also points to continuity across common changes in a user’s setup. Incognia says it recognizes devices persistently, including after app reinstalls, and can recognize users across devices. Those capabilities are relevant to account takeover and account abuse, where a single device or session may not tell the whole story. Tamper detection adds another signal for assessing risk.

The practical appeal is strongest for companies that want identity and fraud signals spanning apps and devices, rather than a tool limited to one device-level identifier. The pricing information lists Essential, Advanced and Premium tiers for teams needing core, advanced or premium identity services. However, it does not spell out feature-by-feature differences between those tiers, so buyers will need to confirm which capabilities are included in a proposal.

The main drawback is price transparency. According to the published pricing information, Incognia charges by volume, based on monthly active users (MAU) or API calls, but does not publish rates for Essential, Advanced or Premium. There is no published monthly or annual price to compare with a current vendor bill, and no stated starting price.

The same information does not publish seat limits or usage caps. That leaves buyers without a public way to estimate how costs change as adoption or API traffic grows. The tiers are described broadly, but their detailed feature differences and volume thresholds are not listed either.

A Proof of Value trial is listed for all three plans, but its duration is not published. The pricing data also lists no free plan; it does not provide a published free-trial duration. Teams should ask for written pricing tied to expected MAU or API calls, plus clear overage terms and trial scope, before treating Incognia as a comparable line item in a stack review.

Incognia’s prices are not published, so there’s no reliable monthly or annual bill to quote—and no way to calculate the jump between tiers. Pricing is volume-based on monthly active users (MAU) or API calls, but rates and usage caps are not published.

The listed tiers are Essential for core identity services, Advanced for advanced identity services, and Premium for premium identity services. The available pricing information does not say what specific features separate them, so ask for a tier-by-tier quote before comparing costs. Seat limits are also not published.

No free plan is listed. A Proof of Value trial is mentioned for each tier, but its duration and terms are not published; don’t assume it is a free trial. No add-ons are listed. Get the MAU or API-call measurement rules, overage charges, billing minimums, and renewal terms in writing before committing.

The available information does not document migration steps, implementation effort, data export options, or contractual lock-in. We’d confirm those points with Incognia before moving a fraud workflow, especially if your current system depends on identity or device records that need to carry over. The product description centers on location intelligence, persistent device recognition, cross-device recognition, and app security; it does not explain how existing records map to Incognia ID.

There’s no Reddit feedback in the published sources to establish why customers leave, so we can’t attribute a common exit reason to users. The clearest buying risk in the available material is commercial: volume-based pricing, usage limits, and trial duration are not published. Ask for export formats, retention and deletion terms, integration requirements, and a written exit process alongside the quote. If you’re switching away, confirm what data you can retrieve and whether another provider can use it before setting a cutover date.