Private AI
The private way to use AI
The big-name models from Anthropic, OpenAI, Google and xAI, the best open-source models, end-to-end encrypted models where even the host is blind, and abliterated models built for the security work mainstream assistants refuse. No account. Pay with Monero, Bitcoin, Lightning or a card. Every chat is served inside a secure enclave that PayPerQ cannot read.
- PayPerQ never sees your prompts
- No sign-up, no email
- Monero, Bitcoin, Lightning, card
- E2EE models: host-blind too
Who can see what
Every chat request is decrypted only inside an AWS Nitro enclave running PayPerQ’s open-source, reproducibly built router. PayPerQ’s servers, staff and logs cannot read into it, and neither can AWS. The party that could read your prompt does not know who you are, and the party that knows how you paid cannot read your prompt.
| Party | Prompt content | Your identity | Your payment |
|---|---|---|---|
PayPerQ Sees a credit id, the model, token counts, timing and cost. Never the prompt or the reply. | No | No | Yes |
AWS (the enclave host) Nitro enclaves have no operator login; AWS states this holds even for law-enforcement requests. | No | No | No |
The model provider (Claude, GPT, Gemini, Grok…) Receives the prompt under PayPerQ’s credentials. It sees PayPerQ, not you. | Yes | No | No |
The model host for E2EE models End-to-end encrypted: the model itself runs inside a hardware enclave. Nobody outside your device reads the prompt. | No | No | No |
Payment processor Crypto: a wallet address. Card: Stripe holds your card details, linked to your credit id. | No | Card only | Yes |
One exception: OpenAI requires a per-customer identifier on every request, so OpenAI models carry a keyed hash of your credit id. OpenAI can tell requests came from the same customer, but cannot turn the hash back into a credit id or a person.
Using it safely
There is no sign-up, which also means there is no password reset. Four things to know before you fund.
- 1
Fund without an email
Open the chat, click top up, and pay with Bitcoin (on-chain or Lightning), Monero, Litecoin, Dogecoin, Ethereum, Solana, USDT or USDC. Or a card through Stripe if you don’t mind the link. Start with as little as 10 cents.
- 2
Your credit id is your key
PayPerQ gives you a credit id instead of an account. It is the only way back to your balance, so copy it from Settings and keep it somewhere safe. Without it, support can only help if you can prove a payment.
- 3
Pick a model by its privacy badge
Every chat model shows a tier. Anon the provider may retain prompts but cannot link them to you. ZDR only provider endpoints that contractually keep nothing. E2EE end-to-end encrypted: the model runs inside a hardware enclave and no one but you reads the prompt. For the strictest privacy, choose E2EE. For a frontier or abliterated model, turn on PII redaction so names, emails, phone and card numbers are swapped for placeholders before the request leaves.
- 4
Decide where your history lives
Conversations stay in your browser by default; PayPerQ stores nothing. If you want them on more than one device, sign in with a passkey: your history is encrypted on your device with a key PayPerQ never has, and no email is required.
E2EE models
End-to-end encrypted. Open-weight models that run inside a hardware enclave at the host, so your prompt is readable by you and the model and nobody else: not PayPerQ, not the host. Look for the E2EE badge in the model picker. The lineup grows as we add models.
Browse the modelsAbliterated models
Reasoning models with the refusals edited out of the weights, built for code audits, malware analysis, red-teaming and exploit work that mainstream assistants decline. They ride the same secure enclave, so PayPerQ still cannot read the request. Censorship and privacy are separate questions, though: check the badge, since most carry Anon or ZDR rather than E2EE.
About abliterated modelsAPI and coding tools
The same guarantees hold on api.ppq.ai: chat completions and Messages requests are served inside the enclave, so Claude Code, OpenCode, Cline, Codex and the rest get the same privacy as the web app.
Tor and VPNs
PayPerQ works in Tor Browser at the Standard and Safer levels. Your IP address is visible to the network edge like any web request and is not linked to your credit id; use Tor or a VPN if you want it hidden.
Verify it, don’t trust it
The enclave’s code is public and builds reproducibly to a published measurement. Before the web app sends a message, it checks the live enclave against that measurement and shows the result in the chat badge. You can run the same check yourself.
- Privacy Verifier
A small proxy you run locally. It attests the enclave, refuses to send if the measurement does not match, and encrypts every request to the verified key.
- Enclave source and measurement
The router that serves every chat, its reproducible build, and the published PCR0 the clients pin.
- How it works
The full write-up: what a Nitro enclave is, why neither PayPerQ nor AWS can read it, and what metadata remains.
What this does not protect
- On models without the E2EE badge the provider reads your prompt in plaintext. That is where the model runs. Use PII redaction or an E2EE model if the content itself is the concern.
- Image, video and audio generation, and the Auto model router, are not inside the enclave yet. PayPerQ’s servers can see those requests.
- PayPerQ keeps billing metadata per request: credit id, model, input and output token counts, user agent, timing and cost. Paying by card links your card details to your credit id at Stripe.
The legal version is the Privacy Policy. Found a gap? Report it privately to matt@ppq.ai or through GitHub’s private vulnerability reporting on the enclave repo.
Fund and go
No account, no subscription, no one reading over your shoulder. Top up from 10 cents and start.