ArkAPI is designed for privacy. No accounts, no email addresses, no personal information required.
ArkAPI provides anonymous, pay-per-call API access. Sessions are created with a token and funded with Bitcoin. We collect the minimum data needed to operate the service.
Receipts contain billing amounts, an endpoint, a timestamp, a random receipt ID, and signing metadata. They exclude prompts, query contents, session tokens, wallet addresses, and balances. They are not anonymous: timing and endpoint information can reveal usage. Save receipts privately in your client; this version has no server receipt-history or lost-receipt recovery endpoint. Read the verification guide.
Sessions use a rolling 30-day inactivity window. Session expiry is not a guarantee of immediate deletion from billing records or encrypted backups. Server logs are rotated on a standard schedule. There are no registration accounts to delete.
API endpoints may call external services to fulfill requests (e.g., DNS lookups, WHOIS queries). These requests are made server-side by ArkAPI — your IP is not exposed to these services.
The public HTTPS site uses TLS. Native Tor and I2P origins use their encrypted network transports. Keep session tokens and receipts private, and never send credentials through a public Tor-to-web gateway. Report security issues to [email protected].
We may update this policy. Changes will be reflected in the "last updated" date above.
Questions about privacy: [email protected]
