privacy.com

September 28, 2025

What Privacy.com Is and What It Actually Does

Privacy.com is a service that lets you generate virtual card numbers and use them for online (and sometimes in-app) purchases instead of typing in your real debit card number everywhere. You fund Privacy.com from a linked U.S. checking account or an eligible U.S. debit card, and then you create virtual cards on demand inside the Privacy dashboard/app. Those virtual cards are what you hand to merchants.

The practical value is control. If a merchant gets breached, the exposed number is the virtual card number you created for them, not the underlying funding source. And you can limit what that card can do (how much it can spend, where it can be used, whether it auto-closes after a purchase).

How the Money Flow Works

Privacy.com isn’t a “prepaid balance” by default in the way a gift card is. Think of it more like: you connect a funding source, then your Privacy virtual card attempts a charge, and Privacy routes that charge to your linked bank/debit funding source. The merchant sees a card number, but you’re not exposing the real one.

Funding sources matter because there are constraints. Privacy says it does not support credit cards as a funding source, and that it supports checking accounts and debit cards from U.S. banks/credit unions. That means if you were hoping to layer rewards points from a credit card on top of Privacy, that’s generally not how it’s set up.

Card Types: Single-Use vs Merchant-Locked

Privacy.com commonly describes two patterns people use:

• Single-use cards: you generate a card number for one purchase, and it closes automatically after it successfully goes through. This is useful when you’re buying from a site you don’t trust yet, or you just don’t want a stored payment method hanging around.
• Merchant-locked cards: you create a card that “locks” to the first merchant it’s used with. If that card number leaks and someone tries to use it at another merchant, the transaction should be declined. Privacy specifically positions this as a way to keep one merchant breach from spilling into other places you shop.

Merchant-locked is usually the better default for subscriptions and recurring bills because it’s stable (the merchant can keep charging it), but still constrained (it’s not usable everywhere).

Spend Limits: The Feature People Underuse

Spend limits are where Privacy.com becomes more than “a masked card number.” You can set limits at the virtual card level, and there are also account-level limits. Limits apply on a rolling basis depending on the type of limit. Practically, it means you can do things like:

• cap a subscription so it can’t suddenly jump in price without failing
• create a “trial” card that can’t exceed, say, $1 or $5
• set a monthly cap for a merchant you don’t fully trust yet

Privacy also notes that account spending limits can change based on review processes (algorithmic and/or manual). So if you’re planning to run very large volumes through it, expect that there may be gating and that the tool is built primarily for consumer controls, not unlimited throughput.

Plans and Pricing: What You Get as You Pay More

Privacy.com markets multiple plan tiers. Their pricing page shows differences like how many new cards per month you can create, whether there are fees on shared cards, and whether you get perks like cashback and “Privacy Everywhere” cards (a feature name used on their plan grid). The plan grid also shows card creation limits per month increasing by tier (for example, one grid shows 12/24/36/60 new cards per month across tiers).

Their blog description of paid plans also calls out what they associate with Pro, like priority support, a monthly card count increase, and cashback up to a monthly cap (as described on their materials). It also mentions options aimed at businesses (like Teams) and an Issuing offering tied to a developer API. Availability and packaging can change over time, so treat the website’s current plan page and support pages as the source of truth when you’re deciding.

What Privacy.com Helps With (and What It Doesn’t)

It helps most with:

• Reducing blast radius from breaches: a merchant leak exposes the virtual card, not your underlying funding source. Merchant-locked cards are specifically designed around this containment idea.
• Subscription hygiene: dedicated cards per subscription, easy pausing/closing, and spend limits mean fewer “how do I cancel this” headaches.
• Separating merchants: using different cards for different services makes it easier to see what’s charging you and shut off only the problem one.

It does not magically make you anonymous. Merchants can still collect your name, shipping address, email, IP-based signals, device fingerprints, and so on. Also, because funding is limited to U.S. checking/debit sources (per Privacy’s own support article), it may not fit people outside that footprint or people who want to route everything through credit.

Developer and Business Use: When the API Matters

Privacy also runs a developer-facing API and documentation that covers concepts like funding sources and issuing workflows. This is more relevant if you’re building a product or internal tooling that programmatically creates and manages cards rather than clicking around in the consumer UI. It’s a separate mindset: more operational, more compliance and accounting considerations, more monitoring.

For businesses, Privacy’s own plan materials have referenced tiers like Teams and Issuing and features like higher card counts and tailored transaction limits. If you’re evaluating it for a company, don’t assume the consumer plan behavior matches what you’ll need for procurement, reconciliation, and multi-user controls. Check the current business offering details and limitations in the official plan/support docs.

Operational Tips for Using Privacy.com Well

1. Default to merchant-locked for anything recurring. It’s stable for subscriptions but still constrained to that merchant.
2. Use single-use for one-off purchases from unfamiliar sites. If the number leaks later, it’s already dead.
3. Set spend limits intentionally, not as an afterthought. Even a simple “monthly max” prevents a lot of unwanted surprises.
4. Keep one clean funding source. Since Privacy is tied to checking/debit sources (and not credit cards), you may want a dedicated checking account for online spending if you like tighter separation. Privacy’s own ecosystem includes guidance around connecting funding sources and troubleshooting.

Key takeaways

• Privacy.com creates virtual card numbers you can use instead of exposing your real debit/checking funding details to merchants.
• Merchant-locked cards reduce risk if a merchant is breached because the card should only work with that merchant.
• Spend limits (per card and account-level) are a core control feature and can prevent both fraud damage and accidental overspending.
• Funding sources are limited: Privacy states it supports U.S. checking accounts and U.S. debit cards, and not credit cards as a funding source.
• Paid tiers mainly change card-creation limits and add perks; verify the current plan grid and support docs because packaging can change.

FAQ

Is Privacy.com a credit card?
No. It generates virtual card numbers, but it’s funded through a linked checking account or debit card (per Privacy’s support documentation), not through a traditional credit line.

Can I fund Privacy.com with a credit card to earn points?
Privacy’s support article says it cannot support credit cards as a funding source at this time.

What’s the difference between single-use and merchant-locked cards?
Single-use cards close after a successful purchase. Merchant-locked cards tie to a specific merchant so attempts elsewhere are declined, and they’re positioned as ideal for subscriptions and recurring payments.

Do spend limits apply instantly, and can I reset them?
Privacy describes spend limits as rolling and notes both account-level and card-level limits. It also states account limits are subject to change based on review processes and aren’t something you can reset whenever you want.

Does Privacy.com make me anonymous to merchants?
It mainly protects your underlying payment details by substituting a virtual card number. Merchants can still collect other identifying information during checkout (name, shipping, email, device and network signals), so it’s not full anonymity.