Billing & Pricing
NoPII offers a free tier for getting started and a usage-based paid tier for production workloads. Billing is managed through Stripe and aggregated at the organization level across all your API keys.
Plans
NoPII offers Free, Pro, and Enterprise tiers. See the pricing page for full plan details and feature comparison.
What are protected tokens?
A protected token is any LLM token that passes through NoPII's PII detection and tokenization pipeline. This includes both input (prompt) and output (completion) tokens from every proxied request, whether or not PII was actually found. Protected tokens are the unit of billing across all NoPII plans.
How tokens are counted
The count is based on what the LLM provider reports, minus a small overhead NoPII adds to each request:
billable_tokens = prompt_tokens + completion_tokens - overhead_tokens - credited_tokens
| Term | Description |
|---|---|
| prompt_tokens | Input tokens reported by the LLM provider |
| completion_tokens | Output tokens reported by the LLM provider |
| overhead_tokens | A small overhead NoPII adds to each request (subtracted from your bill) |
| credited_tokens | Text already billed when an SDK tokenized it, so not billed again (see below) |
NoPII adds a small overhead to each request for internal processing. These overhead tokens are subtracted from your billable usage so you only pay for your actual content.
Using the SDKs
When an SDK tokenizes text, that text counts toward protected tokens. If your backend then sends it through the proxy in tokens-only mode, the proxy does not bill it a second time. Each message is paid for once, and your total matches what the proxy alone would charge.
This applies when the text reaches the proxy exactly as the SDK returned it, within 24 hours. Text your backend rewrites or combines before forwarding is billed at the proxy as usual.
Free tier limit
The free tier includes 1,000,000 protected tokens per month. Usage is aggregated across all your API keys and resets on the 1st of each month (UTC).
When you exceed the limit, NoPII returns HTTP 429 for subsequent proxy requests until either:
- The month resets
- You upgrade to the paid tier
Token retention (TTL)
Vault tokens have a configurable time-to-live (TTL) that controls how long tokenized PII is stored. When a token expires, the underlying PII is permanently deleted from the vault. If the same PII appears in a future request, it will be re-tokenized with a new token.
| Plan | Default TTL | Configurable |
|---|---|---|
| Free | 1 day | No |
| Pro | 1 day | Yes (1 day to permanent) |
On the Pro tier, you can configure TTL in the admin console under Settings. A TTL of 0 days means tokens are retained permanently (no expiration).
Token retention is separate from token purge. TTL handles automatic, time-based expiration. Purge handles on-demand deletion for GDPR erasure requests. See GDPR Compliance for details on token purge.
Managing your subscription
Billing is managed through Stripe. From the admin console, you can:
- Upgrade from the free tier to a paid subscription
- View invoices and billing history
- Update payment methods via the Stripe Customer Portal
- Check your current plan and subscription status
Usage monitoring
The admin console dashboard shows your token usage at a glance, including:
- Per-key usage with configurable time range and granularity
- Account-level usage aggregated across all API keys
- Estimated cost based on your current plan
- Detailed breakdowns and time-series charts
Related
- Quick Start - Get started with the free tier
- Error Handling - HTTP 429 when the free tier limit is exceeded