Last updated: 2026-06-17

Privacy Policy

This Privacy Policy explains how AIAgenHub (“AIAgenHub”, “we”, “us”) collects, uses, stores, and protects personal data when you use our reverse-proxy and marketplace service (the “Service”). AIAgenHub resells access to upstream LLM subscriptions (for example Claude and Codex via OAuth, Command Code, z.ai GLM Coding Plan, and OpenCode Go) and settles usage with pay-per-token billing in USDC on Solana. We are committed to collecting only what we need to operate the Service and to being transparent about how it is handled.

Overview

AIAgenHub is operated by its developer as an individual (the “Operator”), with a primary contact address of contact@aiagenku.app. We process personal data for the sole purpose of providing an OpenAI/Anthropic-compatible inference proxy and marketplace, authenticating your account, routing requests to upstream subscription providers, recording the usage needed to bill you and pay publishers, and securing the platform. We do not sell your personal data.

Information We Collect

We collect only the data required to run the Service, secure your account, and maintain an auditable financial trail.

Account information

When you create an account we store your email address and display name, plus a password. Passwords are never stored in plaintext — they are protected with a bcrypt hash. We use your email to send transactional messages such as sign-in, password reset, and security notifications.

API keys

API keys you create to call our endpoints are stored only as an irreversible hash together with a short non-secret prefix used for display. The full secret value is shown to you exactly once at creation time and is never retrievable by us afterward.

Publisher upstream credentials

If you act as a publisher and attach an upstream subscription, we store the associated API key or OAuth refresh token. These credentials are encrypted at rest with AES-256-GCM and are decrypted only in-process, in memory, when a request is routed through that upstream. Outbound proxy credentials are protected with the same AES-256-GCM encryption.

Request and usage logs

For every proxied request we record the model used, token counts (prompt, completion), the computed cost, the HTTP status, and timestamps plus the caller's region. These logs are necessary for billing, publisher payouts, rate limiting, and abuse prevention.

When an upstream provider rejects a request with a security-policy error we cannot otherwise explain, we additionally retain, for 7 days, the scaffolding of that one request — the system prompt, the tool definitions and the request parameters your client sent — so we can find out what the provider objected to. Your messages, tool results, file contents and attachments are not retained here. The text is encrypted at rest, is read only by an administrator investigating that specific failure, and is never used to train models or shared with third parties.

Safety screening

Before a request is sent to an upstream provider we screen the text you authored — your messages and system prompt — against a keyword and pattern list, to keep content prohibited by our Acceptable Use terms off the provider accounts that serve you. This screening happens entirely inside our own infrastructure: no part of your request is sent to any third-party classification or moderation service. Tool results, file contents and attachments are excluded from the screen.

When the screen flags a request we record the model, the rules that matched, and a score, retained for 90 days. We also retain, for 14 days, the text the screen actually read, so that we can tell a genuine problem from a false alarm and correct the screen. That retained text is encrypted at rest, is readable only by an administrator reviewing that specific flag, and every such access is recorded in our audit log. It is used only to investigate abuse and reduce false positives — never to train models, and never shared with third parties.

Billing and ledger

We keep USDC balance amounts and a transaction history (deposits, usage deductions, publisher earnings, platform fees, and withdrawals). For financial-integrity and audit reasons, ledger entries are retained even after an account is closed.

Technical logs and audit trail

We keep server and application logs containing technical details needed to operate and secure the Service, and audit logs that record the actor, action, target, source IP, and user-agent for sensitive events. These support incident response, fraud detection, and compliance.

How We Use Information

We use the data we collect to:

• Create, authenticate, and manage your account and sessions.
• Issue, verify, and revoke your API keys and route requests to upstream providers.
• Measure token usage, compute cost, and settle balances in USDC.
• Pay publishers their margin and account for the platform fee.
• Enforce rate limits, detect abuse, and protect the Service from fraud.
• Maintain an audit trail for security, financial integrity, and compliance.
• Send transactional and security emails related to your account.
• Comply with legal obligations where applicable.

We do not use your request content to train models, and we do not sell personal data to third parties.

Cookies & Local Storage

AIAgenHub uses strictly-necessary cookies and local storage only. This includes your session cookie, which keeps you signed in, and a short-lived cookie used during the OAuth PKCE handshake when attaching an OAuth-based upstream subscription. These are required for the Service to function and cannot be disabled without breaking authentication.

We do not use analytics, advertising, or cross-site tracking cookies. A consent banner is shown on first visit to make this strictly-necessary use explicit; because no optional cookies are set, there is nothing to opt out of beyond the functional session cookie.

Data Retention

We retain personal data only as long as necessary for the purposes described in this policy and to meet legal, accounting, and security obligations:

• Account data is kept while your account is active and is soft-deleted on request.
• API keys are revoked when you rotate/revoke them or close your account.
• Publisher upstream credentials are deleted when the upstream is removed or the account is closed.
• Request/usage logs are retained for the period needed for billing, payouts, and abuse detection, then aggregated or deleted.
• Ledger and transaction history, plus audit logs, are retained for the longer of the period required by financial/accounting law or our audit obligations, even after account closure.

Data Security

We apply layered technical and organizational safeguards to protect your data:

• Sensitive secrets (API keys, OAuth refresh tokens, outbound proxy credentials) are encrypted at rest with AES-256-GCM and decrypted only in-process.
• Passwords are hashed with bcrypt; your API keys are hashed and never stored in retrievable form.
• Authentication, API, and account endpoints are rate-limited and protected with security headers.
• Sessions can be invalidated globally via a token version, and OAuth PKCE is used.
• Outbound requests are guarded against SSRF, and access to administrative functions is logged in an append-only audit trail.

No method of transmission or storage is fully secure. While we work to protect your data, we cannot guarantee absolute security.

Your Rights

Depending on where you live, you may have rights to access, export, rectify, or erase your personal data, to object to certain processing, and to withdraw consent. You can export your data and delete your account directly from your account settings. For any other request, contact us at contact@aiagenku.app. We will respond in accordance with applicable law, typically within 30 days. Erasure is a soft-delete: we preserve ledger and audit records required for financial-integrity and legal obligations.

Service Providers / Sub-processors

We rely on third-party providers to operate the Service, in categories including:

• Hosting & compute — the server infrastructure that runs the application.
• Database — a PostgreSQL provider for primary relational storage.
• Cache & queues — Redis and NATS providers for caching and job queues.
• Solana RPC — a Solana RPC provider for USDC payment settlement on mainnet.
• DNS & delivery — a DNS/CDN provider (Cloudflare) for domain and edge delivery.

We will provide the named sub-processors and the current list on request. We contract with sub-processors under terms consistent with this policy.

International Transfers

Your data may be transferred to and processed in countries other than your own, including the jurisdictions where our infrastructure and sub-processors are located. When we transfer data outside of the Operator's jurisdiction, we use appropriate legal mechanisms such as Standard Contractual Clauses or other recognized transfer safeguards.

Children's Privacy

The Service is intended for developers and businesses and is not directed at children. We do not knowingly collect personal data from anyone under the age of 16 (or the minimum age required to consent in their jurisdiction). If you believe we have collected data from a child in error, please contact contact@aiagenku.app and we will delete it.

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above. For material changes that affect your rights we will provide notice through the Service or by email where practical. Continued use of the Service after a change takes effect constitutes acceptance of the updated policy.

Contact

If you have questions, requests, or concerns about this Privacy Policy or your personal data, please contact the Operator at contact@aiagenku.app. The data controller is the Operator, in the Operator's jurisdiction of residence.