Detect risky scan patterns without punishing real customers.
Pearpin scores suspicious behavior, explains why a scan looks risky and lets your team choose how aggressively to escalate — backed by tenant-scoped keys, signed webhooks and clear retention defaults.
How Pearpin builds trust — explainable, layered, brand-controlled.
Pearpin combines unit identity, scan context, history and behavior to score risk and route the next action. Risk thresholds are tunable, escalation is brand-controlled and every signal is auditable.
Unit identity
Every unit gets a unique, unguessable ID generated by Pearpin and bound to a batch. Re-using the same code somewhere else creates a detectable signal.
Scan context
Each scan carries time, approximate location, device-class hints, code state and originating channel. Context turns a static QR into a temporal event.
Risk scoring
Explainable, per-unit, per-event. Adjustable thresholds. Brands can tune sensitivity per category, per region, per batch.
Anomaly detection
Patterns over time. Velocity, geo-impossibility, scan-cluster shape, batch-level outliers. Detection improves as scan history accumulates.
What Pearpin does
- Layered trust signals
- Explainable risk scoring
- Brand-controlled escalation
- Pattern detection over time
What Pearpin does not pretend
- QR codes are uncopyable
- 100% counterfeit prevention
- Tamper-proof packaging guaranteed
- Magic anti-counterfeit security
Pearpin reduces counterfeit risk over time by helping brands see patterns, escalate safely and control how consumers experience trust. Real security is layered — and Pearpin is one strong layer.
Layered signals. Tunable thresholds. Honest escalation.
Pearpin doesn't claim QR is uncopyable. It detects the patterns counterfeiters create and routes risk through a five-tier ladder you control.
Five-tier risk ladder
authority · brand → platform → humanBaseline. Continue.
One signal off-pattern. Logged. No consumer warning.
Multiple signals. Internal alert. Optional consumer message.
Strong signals. Brand decides whether to warn or block the action.
Human-in-the-loop. Inspector workflow on Enterprise.
Same unit scanned in two cities within a window that physical travel cannot satisfy.
Unusual scan frequency on a single unit — possible code reuse or photographed code.
A code marked sold or returned is scanned in a new retail context.
Scan footprint of one unit diverges sharply from its batch's normal pattern.
Scan originates from a marketplace or region where the SKU was never shipped.
First-scan timestamp drifts far outside the expected manufacture-to-retail window.
Brand-controlled escalation. Every signal is logged, but only your team decides when a consumer hears about it. Watch tiers stay silent. Suspicious tiers can show a soft message. High-risk can warn or block. Brand review unlocks the inspector workflow on Enterprise.
Specific controls. Specific commitments.
The honest-positioning chips above tell you what Pearpin is not. The grid below tells you what Pearpin actually does about identity, data and incident response. Status labels make timing explicit.
Tenant-scoped API keys
Every key is scoped to a single brand tenant, with rotation enforced and a public revocation path. No cross-tenant blast radius.
Webhook HMAC signing
Every webhook payload is signed with a per-tenant secret. Replays are rejected via timestamp + nonce checks.
Idempotency keys
Every mutation accepts an Idempotency-Key header so safe retries never produce duplicates — required on bulk unit creation.
Retention defaults
Scan events keep operational metadata only; raw IPs and device fingerprints are aggregated. Free retains 90 days, Pro retains 12 months and Growth/Enterprise support extended or configurable retention.
What we do not store
Pearpin does not store consumer PII unless a brand opts in for warranty or loyalty flows. We do not sell scan data to third parties — full stop.
Data residency
Identity ledgers and scan events are region-pinned where required. Pearpin's first regional pin is India, with EU and US to follow.
Incident response
Public status page, a documented escalation chain and post-mortems for any incident affecting verification availability.
Compliance roadmap
DPDP-aligned data handling for India is our first compliance milestone. SOC 2 Type 2 trajectory begins post-launch.
Need to review Pearpin with security and procurement?
Request the security overview and we'll share our key-management notes, draft DPA materials and incident-response posture on request.