Privacy policy
Effective date: October 27, 2026
Last updated: October 29, 2026
This policy explains what personal information InferGauge ("InferGauge," "we," "us") collects when you use our website at https://www.infergauge.com (the "Website"), the InferGauge console (the "Console"), the InferGauge command-line agent (the "Agent"), and InferGauge's apps for ChatGPT and Claude (delivered through an MCP connector, see Using InferGauge in ChatGPT and Claude), and how we use, share, and protect it.
1. Who we are
InferGauge is operated by Nexus Corporation DBA InferGauge, 9772 Athletic Way, Gaithersburg, MD 20878, USA. For privacy questions, contact alimalik@nexusadvisors.ai.
2. The short version
InferGauge tests run on your own machines, not on our servers. Your prompts, model responses, API keys, and private endpoint URLs never leave your infrastructure. They are stripped by the Agent before upload and again by our server.
The Console stores your account details and the metrics and summaries of the tests you run, so we can authorize runs, meter your subscription, and show you your history. The Console itself runs no analytics and no ad tracking: nothing watches what you do around your keys, passwords, or payments.
Tracking lives on the Website only. We use Cloudflare Web Analytics and Vercel Web Analytics there (cookieless, no profile built on you), and an OpenAI Ads pixel to measure our own ad campaigns (a first-party identifier, plus a one-way hash of your email, never the email itself, shared with OpenAI only if you sign up after clicking one of our ads). Section 3.3 below spells out exactly what each one sees. We do not sell your personal information.
3. Information we collect
3.1 Information you give us
Account information: name, email address, and password. Passwords are stored only as a salted hash, never in plain text.
Subscription information: your plan (free, developer, team, enterprise), license token, and license expiry date. Payments are processed by Stripe. We store only Stripe customer and subscription IDs and your subscription status, never full card numbers.
Communications: messages you send us for support, and access or upgrade requests, including anything submitted through the Website's contact form (name, work email, company, and your message), which we receive by email and don't additionally store in a database.
3.2 Information collected when you use the Console and Agent
Test run data (metrics and summaries only): run name, test type, number of simulated users, duration, AI provider and model name, start and end time, status, score, SLA pass/fail result, aggregate result summary, and run progress.
Agent and device information: a random device identifier (used to bind your license seat to a machine), the hostname and operating system of the machine running the Agent, and the endpoint label for the test. Private base URLs and credentials are removed before upload.
Usage metering: number of runs per billing period, used to enforce plan limits.
API tokens: a hash and short prefix of tokens you create, their name, when they were created and last used. We cannot recover the full token after creation.
Account activity: sign-up time, last login time, email verification status, and password-reset requests.
3.3 Information collected automatically, and exactly where
Security and abuse-prevention logs: IP address and timestamp of sign-ups and password-reset requests, and the outcome and time of login attempts, used for rate limiting and fraud prevention. This happens on the Console only.
Server logs: our hosting infrastructure may record IP addresses, request times, and user-agent strings for security and reliability, on whichever product's servers handled the request.
Beyond that, here is every cookie, identifier, or tracker in InferGauge, and which product it runs on. Nothing below applies to the Console beyond the one session cookie: your keys, passwords, and payment details on the Console are never touched by analytics or ad tracking of any kind.
| Where | What | Purpose | Cookie? |
|---|---|---|---|
| Console | infergauge_session | Keeps you signed in. Strictly necessary. HttpOnly, SameSite=Lax, Secure. | Yes, one cookie |
| Website | Cloudflare Web Analytics | Page views, referrers, rough device/browser/country. | No, cookieless |
| Website | Vercel Web Analytics | Same as above. | No, cookieless |
| Website | OpenAI Ads pixel | Connects an ad click to a later visit, so we can measure our own ad campaigns. | A first-party identifier, not a traditional tracking cookie |
The OpenAI Ads pixel has one further step, which is the only place Website tracking and Console data ever meet: if you create a Console account after arriving from one of our ads, we share a one-way cryptographic hash of your email (and, where available, other identity fields) with OpenAI Ads at the moment of signup, never your actual email address, so OpenAI can tell whether its ads led to a real signup. Apart from this, and the data you choose to send through our ChatGPT or Claude integrations (see Using InferGauge in ChatGPT and Claude), nothing from your Console activity is shared with OpenAI, Anthropic, or any other advertising or analytics service.
An ad blocker or a tracking-prevention browser setting will make our analytics and ad measurement less accurate. Nothing in InferGauge breaks because of it.
3.4 What we do not collect
Prompts, model responses, test payload content, provider API keys, and private base URLs. If you believe such data has reached us, contact us and we will delete it.
4. Using InferGauge in ChatGPT and Claude
If you connect InferGauge to ChatGPT or Claude, that assistant can use InferGauge's tools on your behalf. Nothing is shared until you connect, and you decide when it uses them.
4.1 What we receive from ChatGPT and Claude
Only the details of each request, such as the number of users, duration, and targets for a new test, or which of your runs to look up. We do not receive your conversation with either assistant. We never accept API keys, passwords, or other credentials through ChatGPT or Claude, and our tools reject them.
4.2 What we send to ChatGPT and Claude, and therefore to OpenAI and Anthropic
Your account's email address, plan, and usage; results of runs you ask about, including scores, latency, throughput, error rates, cost, our written findings, and a link to the full report; comparisons between your own runs; and test configurations and CI workflow files we generate for you. Raw provider error messages and second-by-second measurements are left out. Prompts, model responses, API keys, and private endpoint URLs are never collected in the first place (section 3.4), so they cannot be shared. Once in ChatGPT, this data is covered by OpenAI's privacy policy; once in Claude, it's covered by Anthropic's privacy policy. Through either assistant you can only ever see your own account's data.
4.3 Sign-in and access tokens
You connect by signing in to the InferGauge console. ChatGPT or Claude then receives an access token that works only for InferGauge's tools in that assistant; it cannot sign in to the console or change your account. We store only a hash of the token, and it expires after 90 days. Disconnecting the app or connector in either assistant stops it using the token. To cancel the token itself, revoke it in the console under Settings, MCP tokens. We record when each token is used, to enforce rate limits.
5. How we use information
We use the information above to create and secure your account and authenticate you; to authorize test runs, meter usage, and enforce subscription limits; to show you your run history, results, and usage reports; to send service emails such as verification, password reset, and license and account notices (we do not send marketing email without your consent); to prevent abuse, enforce license terms, and keep the service secure; to maintain and improve InferGauge using aggregate, non-identifying statistics; and to comply with legal obligations.
Legal bases (EEA/UK users): performance of our contract with you (account, runs, subscription); our legitimate interests (security, abuse prevention, product improvement); legal obligation; and consent where we ask for it.
6. How we share information
We share personal information only with the service providers that help us run InferGauge, under confidentiality and data-protection terms, each scoped to the one product it actually touches:
| Provider | Used by | What it's for | What it sees |
|---|---|---|---|
| Vercel | Website | Hosting, plus analytics | Page views, referrer, device/browser/country |
| Cloudflare | Website | Analytics | Same as above |
| OpenAI Ads | Website, and the Console at the single moment described in 3.3 | Ad performance measurement | Page views and clicks tied to ad campaigns, plus a hashed email on signup |
| OpenAI (ChatGPT connector) | Console, only if you connect it yourself | Lets ChatGPT use InferGauge's tools on your behalf | See section 4: your account's email, plan, and usage, plus the results of any runs you ask about |
| Anthropic (Claude connector) | Console, only if you connect it yourself | Lets Claude use InferGauge's tools on your behalf | Same as the row above, for Claude instead of ChatGPT |
| Resend | Website and Console | Sends and receives our transactional email | Whatever you type into the Website's contact form; the verification, password-reset, and license emails the Console sends you |
| Fly.io | Console | Application hosting | Hosts the Console application, including the code that triggers your account emails, and its in-memory database holding your account, run, and subscription data |
| GoDaddy | Website and Console | Domain registration, DNS, and the mailboxes behind our email addresses | Domain/DNS records, and the content of any mail sent directly to or from an address on our domain |
| Stripe | Console | Payment processing | Your billing and card details. We don't see these ourselves. |
Fly.io is one provider that, by hosting the Console's own database, necessarily has access to everything the Console stores: your account, your run history, your subscription status. It doesn't see this data for any purpose of its own, only as the infrastructure the Console runs on. The ChatGPT and Claude connectors are different: each only ever receives what you ask it to look up, and only after you've connected it yourself (see section 4). No provider in this table ever sees your password, and nobody other than Fly.io and, where you've connected one, the ChatGPT or Claude connector sees your test results.
Legal and safety: where required by law or to protect rights, safety, and the security of the service.
Business transfers: in connection with a merger, acquisition, or sale of assets, with notice to you.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
7. Data retention
Account and run data are kept while your account is active.
When you delete your account, we delete your profile, sessions, API tokens, devices, and run history within 30 days, except where we must retain limited records for legal, tax, or fraud-prevention reasons.
Security logs (sign-up IPs, login attempts, password-reset requests) are kept for 90 days.
Backups are overwritten within 35 days.
8. Security
We use TLS in transit, hashed passwords, hashed session and API tokens, HttpOnly/SameSite session cookies, CSRF protection, rate limiting, and server-side enforcement of quotas. No system is perfectly secure; if a breach affects your data, we will notify you and regulators as required by law.
9. Your rights and choices
Depending on where you live (for example under GDPR, UK GDPR, or the CCPA/CPRA), you may have the right to access, correct, delete, or export your personal information, to object to or restrict certain processing, to withdraw consent, and not to be discriminated against for exercising these rights. You can delete your account from the Console, or email alimalik@nexusadvisors.ai. We will respond within the period required by law (generally 30 to 45 days). EEA/UK users may also complain to their local data-protection authority.
10. International transfers
We are based in the United States, and our services and providers are located in the United States. Your information is processed and stored in the United States. If you access InferGauge from outside the United States, you understand that your information will be transferred to and processed in the United States.
11. Children
InferGauge is a business and developer tool not directed to anyone under 16. We do not knowingly collect information from children; contact us if you believe we have, and we will delete it.
12. Self-hosted and enterprise deployments
If your organization runs InferGauge on its own infrastructure, that organization controls the data in its deployment, and its own privacy policy applies to that data. This policy covers the hosted Console and Website operated by us. Enterprise customers may request a Data Processing Agreement at alimalik@nexusadvisors.ai.
13. Changes to this policy
We may update this policy. We will post the new version here with a new "Last updated" date and, for material changes, notify you by email or in the Console.
14. Contact
Nexus Corporation DBA InferGauge
9772 Athletic Way, Gaithersburg, MD 20878, USA