Privacy policy

Published 2026-10-26 · Last updated 2026-11-03

The gateway does not write your prompts or the model's outputs to its database or its logs; they pass through its memory on the way to the model provider that serves the request: abliteration.ai, Refuseless or Experiential Labs. abliteration.ai states that it does not store prompts or completions by default. Refuseless may pass content to third-party providers it chooses, which it says generally operate under zero data retention. Experiential Labs says its models are not zero retention. Their privacy policies apply; we cannot verify or control them. We keep the numbers needed to bill and prove billing. We set no cookies ourselves and run no analytics or advertising trackers.

Who is responsible

Controller: Inkwell Finance, Inc. d/b/a Dagon, a Delaware corporation. Contact: privacy@inkwell.finance. We have not appointed a Data Protection Officer.

What we store

Keys: a hash of each key secret, its name and its balance.
Holds: the amount reserved while a request is in flight.
Credits: top ups and their payment references.
Receipts: request id, key id, time, endpoint, model, token counts, usage source, price version, charge, the provider that served the request, the upstream request id and a SHA 256 of the output. Never the text.
Payment references: for each checkout top up, the checkout session id and the onchain transaction signature, which publicly identifies the paying wallet. For each x402 payment, the paying wallet address, the transaction signature, the amount, the key it funded and whether it settled. A key that x402 creates is named after the first and last four characters of the paying wallet, and later x402 payments without a key from the same wallet are credited to that same key.
Sanctions records: when a payment is refused because a wallet matches the sanctions list, the wallet address, the time, the payment method, the key concerned and the version of the list.
Key records: key id, name, creation and expiry time, when it was last used or topped up, funding, spend and the account that minted it, plus a log of moves of funds between your account and the keys you mint. Credits an operator grants by hand are recorded too.
Request ids, statuses and error codes.
If you sign in with a passkey: for each passkey, its credential id, public key, signature counter, transports, the name you gave it, a random user handle and creation time, and a hash of each console session. We never receive anything that could unlock your passkey, and no biometric data reaches us.
If you use wallet login, an encrypted list of your keys under an id derived from your wallet signature. We do not hold the key that decrypts it.
Backups: an encrypted copy of this database and our receipt signing key is stored at Cloudflare (R2). Backups expire on a schedule we set.

What the gateway does not keep

Your prompts.
The model's outputs.
Your wallet address at login.
For private leases, which deposit funded the lease.

Keys and passkeys are linked to the names you give them, so do not put personal details in those names.

What others can see

While a request is in transit, we see its content, your IP address and timing, and the provider that serves it (abliteration.ai, Refuseless or Experiential Labs) sees its content and timing and the gateway's network address (we do not forward your IP address). We use your IP address in memory for rate limits and location checks.

For prepaid keys we forward user, safety_identifier, any metadata and the x-abliteration-session-id header to abliteration.ai if you send them; for private leases we remove user and safety_identifier. These fields and that header go only to abliteration.ai: on requests routed to Refuseless or Experiential Labs we remove user, safety_identifier and metadata and do not send the header. Do not put personal identifiers in those fields unless you intend abliteration.ai to receive them.

Requests made with one lease can be linked to each other. Paying with a wallet links that wallet to the key it funds, onchain and in our checkout and x402 payment records.

Location checks and sanctions screening

The service is not offered in the European Union, the European Economic Area or the United Kingdom, or in the other locations listed in the terms. To enforce this, we look up the country and region of your IP address in memory when you make a request or open a page. The lookup uses DB-IP's IP geolocation database, held on our own server, so your IP address is not sent to DB-IP. We do not store your IP address or the location we derive from it. IP geolocation by DB-IP.

Before a top up is credited, the paying wallet address is screened against the US Treasury OFAC list of Specially Designated Nationals. Our checkout at pay.dagon.so, which we run using Zoneless open source software, performs this screening. The result is kept with the payment as a sanctions compliance record.

When you pay per request with x402, the gateway itself screens the paying wallet against the same list before it accepts the payment, and keeps the paying wallet address, the transaction signature, the amount and the key it funded as the payment record.

Who else handles data

abliteration.ai: model provider. Receives request content, timing, the gateway's network address and the fields above. Its privacy policy applies.
Refuseless (DPLS Systems LLC, Wyoming): model provider for the models labeled Refuseless. It receives request content and timing, and the gateway's network address. It may pass content to third-party model providers it chooses, which we cannot name; Refuseless says these generally operate under zero data retention. Its privacy policy applies.
Experiential Labs (Resolute Labs AI, Inc., Delaware): model provider for the models labeled Experiential Labs. It receives request content and timing, and the gateway's network address. It is a multi-provider platform; for its uncensored models it says they run on its own GPUs (Experiential Cloud), and it says its models are not zero retention, so it may keep content. Its privacy policy applies.
Railway: hosting. Handles network traffic and may keep operational logs.
pay.dagon.so: our hosted USDC checkout, which we run using Zoneless open source software. It processes the paying wallet address, the transaction signature, the key id attached to the checkout and, if you enter one, your email address. Until 2026-11-03 the checkout required an email address; it is now optional. We use a checkout email only to deal with that payment and do not send marketing. To check your location, it uses your IP address or, for a purchase made with POST /v1/credits/purchase, the caller's IP address, which the gateway passes to it for that purpose only; it does not store either. Its wallet buttons load third-party code from WaaP and connect to your browser wallet.
WaaP and WalletConnect or Reown: wallet login in the console, only if you open it, and the WaaP wallet button on the checkout.
Circle: the issuer of USDC and operator of the Cross-Chain Transfer Protocol, which sees cross-chain payments you make through the checkout.
zkAPI servers: optional private leases.
Public blockchains: transactions are public and permanent, and we cannot erase them.

If you send personal data of other people in prompts, you decide what is sent and are responsible for having the right to send it.

Why we use data

Run the API and console, bill, issue receipts: key records, holds, receipts, payment references, checkout email addresses if given, passkeys, sessions and the vault. Basis: contract.
Security, rate limiting and abuse prevention: client IP (memory only), request ids and statuses. Basis: legitimate interests.
Financial and audit records, legal process and sanctions compliance: ledger, receipts, payment references and sanctions records. Basis: legal obligation and legitimate interests.
Forwarding your prompts to the model provider: content in transit. Basis: contract, because you ask for it.

We do not rely on consent for any processing today. Sharing with WaaP or WalletConnect happens when you choose wallet login or a wallet button at checkout. Rate limits and abuse controls are automated; they do not produce legal effects beyond blocking requests or keys. We do not sell or share personal information.

Where data is processed

Data is processed in the United States and wherever our providers operate. We do not claim a specific transfer mechanism for data that leaves your country.

How long we keep it

Your IP address: in memory only, in rate limit windows of up to one hour, and cleared on restart. It is not written to our database or application logs.
Passkey challenges: 5 minutes.
Holds: released when a request settles, or swept after the reservation timeout.
Console sessions: 30 days.
Wallet vault: until you delete it.
Email addresses entered at checkout: kept with the checkout record until we delete them, which we do on request.
x402 payment records and sanctions records: kept as financial and sanctions compliance records until we delete what is not needed, and for at least as long as the law requires us to keep them.
Keys, balances, receipts, transfers and payment references: kept as records until we delete or detach what is not needed, as described below.
Backups: encrypted, kept for a limited period.
Logs at Railway and Cloudflare: on their own schedules.

Cookies and local storage

We set no cookies ourselves and use no analytics or advertising trackers. The console stores in your browser: your theme choice; if you use wallet login, which wallet you used last; a flag that you have used a passkey here; and, in session storage for the life of the tab, your passkey session token and (during a checkout) your key so you stay connected after returning from payment. These are needed to provide what you ask for and are not shared. Wallet login in the console and the wallet buttons on our checkout load third-party code (WaaP, WalletConnect or Reown) and connect to your browser wallet; those third parties may set their own cookies or storage; see their policies.

Passkeys, vault and payments

A passkey's credential id and public key are persistent pseudonymous identifiers, which are personal data. They are not biometric data: the authenticator checks your fingerprint or face locally and no private key or template reaches us. The wallet vault holds an id derived from a wallet signature, a write token hash, a revision number, the encrypted contents and an update time. The code that encrypts it runs in your browser and is served by us, so you trust our site as you would any web wallet frontend. Blockchain data is public and permanent.

Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict, export or object to use of data about you (for example under GDPR Articles 15 to 21), to withdraw consent where we rely on it, and to complain to your supervisory authority (in the UK, the ICO). If you are in California, you may have the right to know, delete and correct personal information, to opt out of its sale or sharing (we do not sell or share it), to non discrimination, and to use an authorized agent.

To make a request, write to privacy@inkwell.finance. Because we hold no identity data, you must prove control of the key or account: for a passkey account, make the request while signed in or sign a challenge; for a key, give the key id and make a request with that key. We respond within one month, or within 45 days for California requests, and may extend where the law allows. We hold little that identifies a person.

Deleting your data

You can delete your wallet vault, passkeys and sessions yourself in the console. Keys, balances, receipts, and credit and payment references are kept as financial and audit records, because balances and signed receipts depend on them and to meet legal duties. On request we will delete or detach what is not needed for that, for example key and passkey names. Deleted data remains in encrypted backups until they expire. We cannot erase blockchain transactions.

Children

The service is not for anyone under 18 and we do not knowingly collect their personal data. If you believe a child has used it, contact us and we will delete what we can.

Security, breaches and legal requests

We protect data with the controls described on the security page, which describe controls, not guarantees. Because we hold no contact details for most users, we would give notice of a personal data breach by posting it on this site and in the console, and to regulators where required.

We respond to valid legal process and emergency requests. We can typically provide key ids and names, creation and expiry times, funding and spend totals, payment references including onchain transaction identifiers, passkey public data and receipt metadata (model, token counts, timestamps, output hash). We do not store prompts or outputs and cannot produce them. We may preserve account data on request or when we suspect unlawful use, and we notify affected users of legal process unless prohibited or unsafe.

Changes

We will update this page when what we do changes, and the date above will change with it.