Privacy policy
GPU Economy publishes cloud GPU prices. It sells nothing to readers, needs no account, and collects as little as it can: no IP address and no user agent is stored anywhere below, and nothing is sold or used for advertising. Published September 29, 2026. Any change is dated on this page.
Reading the site
- Page views, through our own server. When our server sends a page to a browser it reports the view to PostHog (EU cloud): the page address without its query string, the referring site's domain, any
utm_tags, whether you came from an AI assistant's answer, the country Cloudflare attaches to the request, your browser's first language as a two-letter code, and since October 26, 2026 the device class (Mobile, Tablet or Desktop), worked out by our server from the user agent, which itself is not sent. A provider-offer click carries the same device class. - Browser confirmation and controls (November 3, 2026). A script hosted on this site sends one page-ready acknowledgement, changes to GPU, memory, quantity, duration, rental type and price basis, opening offer details, shortlist selections and opening a comparison to our own server. Only these named actions and their public control values are accepted. Our server attaches the existing visitor and session codes and forwards them to PostHog. No additional page view, IP address, user agent, arbitrary text, full URL or query string is sent. The script cannot read the HttpOnly cookies and loads no third-party code. The acknowledgement confirms a browser even when it reads one page and leaves; a cookie returned on a provider click also confirms a first-page conversion.
- Three first-party cookies.
ge_vid, a random visitor code kept 13 months;ge_sid, a session code that expires 30 minutes after your last page or recorded interaction; and, since October 11, 2026,ge_last, the address of the last page you opened on this site and when, kept for the same 30 minutes, so that the next page tells us how long you stayed on the one before. All are set by our server, HttpOnly and HTTPS-only, and carry nothing else. A browser that refuses them is counted by a code computed from the day, IP address and user agent with a secret key, which changes daily; the IP address and user agent are used for that computation and then discarded. The full description is in What we count about readers. - Arrivals from AI assistants. When a page is opened from an assistant's answer, we record the time, the page and which assistant (table
assistant_referrals). - Deploy buttons. A click on a Deploy button records the time, which price it was for, the page it was on and whether your browser returned our visitor cookie - yes or no, not the code itself (table
deploy_clicks), then sends you to the provider. Only clicks with the cookie are counted as a reader's: a script walking the buttons returns none. - Crawlers and agents are not counted as readers; their requests are read in aggregate from Cloudflare's logs.
- Embedded widgets set no cookie.
The “Add your GPU cloud” form and email
The form stores the work email and the pricing-page link you send, the page you sent it from and the time (table provider_submissions). The email is used only to reply about that listing, never shared, never added to a mailing list, and never sent to PostHog. The same holds for mail you send to data@gpueconomy.com.
The “Get reserved quotes” form
The form on /reserved stores what you type - work email, company if given, the card, the number of GPUs, the term, region, start month and notes - with the page and the time (table reserved_requests). Unlike anything else on this page, it is sent on: with your consent, which the form asks for, a person at GPU Economy passes it to up to three providers that list a rate for the card and tells you which. It goes to no one else, is never published, never added to a mailing list, and PostHog is told only that a request for a card and term was sent - never your email, company, region or notes. The weekly backup counts these rows and does not copy them. Added October 1, 2026.
The MCP server
The MCP server needs no key or account. For each request it records the time, the method (initialize or a tool call), the tool, the GPU or provider asked about, and the name the client declares for itself, such as claude-ai (table mcp_calls). Since October 1, 2026 the server answers a new connection with a session code - that name and a random number, which your client sends back with each request - so a call can be counted with the client that made it; nothing is stored to issue it, and it is not tied to you, your IP address or a cookie. It also records whether the request could be answered. Links to our pages in its answers carry utm_source=mcp, so a visit from one is counted like a visit from an assistant's answer (above). It does not record the conversation, the prompt, your IP address or your user agent, and it sets no cookie. Its answers are built from the same public data files as the site.
Who else handles it
- Cloudflare serves the site and runs our server code; it sees each request as any host does.
- Supabase hosts the database holding the tables named above.
- PostHog (EU cloud) receives the page views described above, with no person profiles.
- Porkbun forwards mail sent to our address.
We sell no data, share none with advertisers, and give none to the providers we list - except a reserved-quote request, which goes to the providers named to you, because you asked us to send it (above).
How long it is kept
The cookies last as stated above. The tables are kept while the project runs, to compare demand over time, and are copied into a weekly backup kept 90 days. PostHog keeps events for the period of our plan with it.
Your choices, and contact
Delete the two cookies in your browser at any time to start as a new reader. To have a form submission, a reserved-quote request or an email deleted, or with any question about this policy, write to data@gpueconomy.com. Nothing else above can be tied to you: no name, IP address or user agent is stored with it.
Data updated: