1. Who we are and what this covers
GPUStrategy operates GPU Router and is responsible for the account and operational personal information described here. This policy covers our website, workspace, API, and support interactions. Contact hi@gpustrategy.fun for privacy questions or requests. If you use an application built by someone else, that application's operator also determines how it handles your information. A signed data-processing agreement, where applicable, may govern processing on a business customer's behalf.
2. Information we process
Account and contact information: email addresses, account identifiers, linked sign-in details, wallet addresses, preferences, and information you provide in support messages. Sources include you and authentication services you choose to use.
Transaction information: purchases, balances, earned-credit records, payment status, transaction identifiers, and public blockchain records associated with a connected wallet. Payment and authentication services also process information under their own policies. Never send us wallet recovery phrases or private keys.
Usage and device information: model and request identifiers, token counts, cost, timing, status, errors, API-key identifiers, and operational diagnostics. Web and infrastructure services may process IP addresses, browser information, and access logs to deliver and protect the Service.
Request content: prompts, conversation history, files, images, tool messages, and other inputs you submit, together with generated outputs, are processed to fulfill your requests. The content may include personal information about you or others. Submit only information you are authorized to share; avoid sensitive or regulated data unless you have confirmed the necessary protections.
Shared content: configurations and other material you choose to publish or share can be accessible to recipients or the public. Public blockchain information remains visible independently of your GPU Router account.
3. Purposes and legal bases
We use information to authenticate users, route requests, return results, meter and bill usage, manage balances, provide support, and communicate service changes. Where data-protection law requires a legal basis, processing necessary to provide the Service relies on performance of our agreement with you.
We also use operational information to investigate failures, prevent fraud and abuse, secure accounts, and improve reliability. Where applicable, these activities rely on our legitimate interests in running a safe, reliable service, balanced against your rights. Accounting, lawful requests, and required records rely on legal obligations. The website measurement described below helps us understand traffic sources and conversions.
Automated routing uses model requirements, availability, price, and request settings to choose how a request is served. Fusion features may inspect request content to choose a model or workflow. We do not use request content or outputs to train models, or for advertising or profiling. This is distinct from making employment, lending, or similar decisions about you. You may contact us about access restrictions or billing decisions you believe are incorrect.
4. Content, retention, and ZDR
Our ordinary usage ledger records billing and operational metadata rather than full prompt and response bodies. This does not mean content is never processed or stored anywhere: stored or deferred features, including batch jobs, must retain the inputs and results needed to complete and deliver the work. Support messages and material you deliberately share are also separate from the ordinary usage ledger.
Standard routing does not promise zero retention or a universal restriction on model training by the serving provider. Data handling depends on the serving route and feature. Receipts do not identify the serving provider, so use a ZDR request when content must not be retained. A ZDR request restricts routing to routes designated as not retaining prompt and response content under their applicable policies. The restriction stays with retries; a request fails if no eligible route is available. Temporary memory caching may occur. Billing and operational metadata remain, and ZDR does not erase data from your application, browser, external tools, or stored workflows.
Account, transaction, usage, security, and support records are retained for the time needed to provide the relevant feature, reconcile payments, investigate issues, meet legal obligations, and establish or defend claims. Retention depends on the purpose, sensitivity, outstanding disputes, and applicable requirements; there is no single retention period for all data. Deletion requests may be subject to these limits and backup lifecycles. Public blockchain records cannot be deleted by us.
5. Who receives information
We disclose request content to inference-serving and routing service providers as needed to fulfill a request. Hosting, database, authentication, wallet-connectivity, payment, security, and support providers receive the information relevant to their functions. This disclosure is necessary to deliver the Service and does not imply that requests are processed solely on our own infrastructure. Some routes use a marketplace seller's own account with a model provider; that provider's policies and the seller's account settings then govern how the request is handled.
We may disclose relevant records to professional advisers, authorities, or other parties when legally required or reasonably necessary to protect rights and investigate abuse. A merger, acquisition, or transfer of the business may involve disclosure subject to appropriate protections. Information you choose to share with another person, application, or public network is available to that recipient.
We do not sell personal information for money. When website measurement is configured, Google Analytics receives site-visit and conversion events, and Reddit and X receive ad-measurement events. These providers may process browser identifiers, cookies, network information and page context under their own privacy policies. Conversion events describe a completed signup or credit purchase, including an opaque order identifier, currency and amount paid. Our event payloads do not include prompts, model outputs, API keys, email addresses or wallet addresses. We do not use sensitive information to infer personal characteristics for advertising.
7. Security and international processing
We use access controls and other safeguards designed to protect information, but no system is perfectly secure. Keep credentials confidential and contact us promptly about suspected compromise.
Infrastructure and service providers may process information in the United States and other countries with different privacy laws. A ZDR designation is not a data-residency commitment. Contact us before sending information subject to a particular residency, transfer, or contractual requirement so the applicable arrangements can be confirmed. Where European or UK data-protection rules apply, you may request information about applicable transfer safeguards and a copy where available. This policy does not represent a certification or itself create a data-processing or transfer agreement.
8. Your choices and privacy rights
You may request access, correction, deletion, account closure, or a portable copy of your personal information by emailing hi@gpustrategy.fun. Depending on your location and the law that applies, you may also restrict processing, withdraw consent, opt out of sale, sharing, targeted advertising or certain profiling, limit certain uses of sensitive information, and appeal a denied request. We do not discriminate against you for exercising applicable rights.
Right to object: where European or UK law applies, you may object to processing based on legitimate interests and to direct marketing. Contact us to exercise this right. You may also complain to your local data-protection authority, including the UK Information Commissioner's Office where appropriate.
Please identify your account and the request without sending secrets. We may ask for information reasonably needed to verify your identity or an authorized agent's authority. We respond within applicable legal deadlines and explain any permitted refusal or limitation. To appeal a decision, reply to our response with your reasons. California and other applicable state privacy notices use the categories, sources, purposes, recipients, and retention criteria set out above.
You can decline to provide information, but we may be unable to create an account, process payment, or fulfill requests without the information needed for those functions.
9. Children and changes
The Service is intended for adults aged 18 or older. If you believe a child has provided personal information, contact us so we can investigate and address it under applicable law.
We update the revision date when this policy changes. For material changes, we provide notice through the Service or an account contact as appropriate and obtain consent when required. Questions and privacy requests can be sent to GPUStrategy at hi@gpustrategy.fun.