Skip to main content
ShieldLabs bills per identification. One browser check counts once, and all domains on the account share its included volume. History reads, profile reads, webhook delivery, analytics dashboard views and exports do not consume identifications.

​
Plans

All plans include identification, risk signals, scoring, High-Risk Events, traffic analytics and API integration. Scale adds priority support. For an uptime commitment, check the applicable agreement. Contact support for a volume arrangement above the self-serve plans.

​
Billing frequency

Choose monthly or yearly billing in Usage. Yearly billing saves approximately 20%; review the exact total and tax treatment in checkout. The included identification allowance renews monthly on paid plans, including annual subscriptions. Check the displayed reset date for your account.

​
What counts toward your plan

Regular snippet calls use the same-user visit cooldown. A suppressed call does not create another identification. Force-check methods bypass that cooldown, so place them at meaningful protected actions rather than in render or polling loops. One login flow can deliberately run two checks: an anonymous attempt and an authenticated session. Reading either result later does not add usage. Optimize usage explains the call placement.

​
When you reach your included volume

The identification request returns HTTP 402 once the account’s available identification volume is exhausted. Paid-plan identification resumes after the allowance resets or the plan changes. Free’s 5,000 identifications are a one-time allowance. History and profile reads do not return 402 for exhausted identification volume. Rate limits are a separate condition: 429, described in Rate limits.

​
Manage your subscription

Open Usage to see used and remaining identifications, reset date and plans. The plan-change dialog shows the billing preview before checkout. Read its effective date and amount, especially when downgrading or changing billing frequency. Settings > Billing holds payment details and invoices. Manage the payment method through the linked Stripe flow. Cancellation retains access until the displayed end of the paid period; review the confirmation before proceeding.

​
Retention and exports

The Privacy Policy states a maximum retention of up to 12 months, subject to applicable settings. The current analytics dashboard provides a 90-day live investigation window. Do not assume that every record remains queryable for twelve months. Export evidence needed for your own records while it is available. Related: Usage screen, API keys, HTTP errors.