FAQ
pricing, billing, privacy, and product behavior
Which pricing tier should I choose?
Choose the tier that matches your expected monthly /identify volume. Free is for evaluation, Hobby is for small production traffic, Starter is for standard production integrations, and Pro is for higher-volume usage with volume discounts.
Is there a free trial?
There is a free tier with 1,000 included identify requests and no credit card required. It is not a time-limited trial. Free accounts stop when the included quota is exhausted.
What counts as usage?
Successful POST /v1/identify calls count as metered product usage. Dashboard management calls, billing screens, and account settings are not metered as identify usage.
How do overages work?
Free accounts do not allow overages. Paid accounts continue serving production traffic after the included monthly quota and bill additional requests at the plan's overage rate.
How are payments processed?
Stripe processes payments, invoices, and tax. Fingerprint.dev stores billing identifiers and subscription state, but payment card details are handled by Stripe. Invoices and payment records may reference Helium LLC; fingerprint.dev is a product of Helium LLC.
Are plan changes prorated?
Plan changes are managed from the dashboard billing screen. When Stripe produces a prorated effect for a change, the dashboard shows a preview before you confirm it.
Where do I find invoices?
Invoices are available from the dashboard billing screen when your account has an active Stripe billing customer record.
Can I cancel?
Yes. Cancellation is handled from the dashboard billing screen. See the Cancellation Policy for the current policy text.
Do you use cookies or local storage for identification?
No. The /identify handshake does not require cookies or local storage to keep a client-side identifier alive. The dashboard may use essential cookies or local storage for session state and preferences.
What data is stored?
Fingerprint.dev stores the account, API key metadata, usage counts, billing identifiers, and identify-event records required to operate the service. Browser evidence is treated as product evidence, not as a customer-visible profile.
Are API keys stored raw?
No. Raw API keys are shown once at creation. Store them in your own secret manager and rotate keys from the dashboard when needed.
Is fingerprint.dev authentication?
No. Fingerprint.dev returns visitor evidence and a confidence score. Your own account, session, authorization, and review systems should remain in charge of the final decision.
A visitor_id is meant to be used as metadata and/or associated with your existing systems. See common solution patterns.