Privacy policy

This policy explains how Game Hosting handles personal information on gamehosting.app and our account, waitlist and email services. For privacy questions or requests, contact contact@gamehosting.app.

Information we use

When you create an account, we store your name, email address, email verification status and account settings. If you use a password, we store a password hash, not the password itself. We also process session information, including IP address and browser information, to keep you signed in and help protect your account.

When you join a waitlist or subscribe to emails, we store your email, selected game interests, subscription preferences and confirmation records. Delivery, bounce and complaint events help us operate the email service and avoid sending unwanted messages.

Signing in with Google or Discord

If you choose Google or Discord, we receive the basic identity information that provider makes available: your provider account identifier, name, email address, email verification status and profile image. We use this information to create or authenticate your account and connect the sign-in methods you select. OAuth tokens stored for these connections are encrypted.

Our sign-in integration requests basic identity and email permissions. It does not request access to your Gmail messages, Google Drive files, Discord messages or Discord server membership. We do not use information received through these sign-in integrations for advertising, and we do not sell that information.

You can disconnect a provider in your account settings while keeping another way to sign in. You can also revoke access in your Google or Discord settings. Disconnecting a provider does not by itself delete your Game Hosting account.

Why we process information

We use account information to provide access, verify email addresses, recover accounts, respond to support requests, prevent abuse and maintain the service. Account emails, such as verification and password recovery messages, are separate from marketing.

Creating an account or signing in with Google or Discord does not subscribe you to the waitlist or marketing emails. Marketing subscriptions have their own confirmation flow, and you can unsubscribe using the link in those emails.

Service providers and cookies

Our hosting and infrastructure providers process information needed to run the service. Cloudflare supports website delivery and abuse protection; Amazon Web Services supports email delivery and backups. We operate Listmonk for email management and Hatchet for background tasks on our infrastructure. Our team receives support tickets, their replies, and new account and purchase notices (name, email, server, plan and amount) in Slack, our internal messaging tool. Google and Discord process their own sign-in flows under their respective privacy policies. Information may be processed in countries other than where you live.

The account service uses essential cookies for sessions and sign-in security. Security services may also process technical information or use cookies to distinguish legitimate requests from abuse.

Website analytics

We use Sentry, hosted in the United States, to diagnose technical failures in the client panel, API and background tasks. Reports contain error types, locations in our code, release versions, limited technical error codes and random request references used for support. We exclude account identifiers, email addresses, free-text error messages, form contents, cookies, request headers and bodies, SQL values and local variables. Sentry does not record sessions, console logs or performance traces in this integration. Browser error reporting respects Global Privacy Control and Do Not Track. Server error reporting operates separately to maintain the service.

To diagnose problems in the client panel, we record form visits, game and plan selections, visible blockers, request results and JavaScript error types and code locations. When you are signed in, these diagnostics are linked to your internal account identifier. Reports exclude server names, form contents, passwords, verification tokens, free-text error messages and raw stacks. Browser diagnostics respect Global Privacy Control and Do Not Track. Separately, the API records purchase and trial attempts and their results to operate the service, even when browser diagnostics are disabled. These records include request references, selected game and plan, order identifiers when available, duration and release version, and are kept in our database for 30 days. Selected diagnostic failures also go to PostHog for reliability monitoring.

We also use PostHog to diagnose JavaScript failures on public pages, including unexpected waitlist failures. Reports include the browser, public page, error type and locations in our JavaScript code. Free-text error messages, request and response bodies, form values and local variables are excluded; explicitly reported failures use fixed technical descriptions. This uses the same cookieless collection and browser privacy opt-outs described below.

We use PostHog, hosted in the United States, to measure visits to our public website, clicks on calls to action, selected games and plans, and successful waitlist requests. Public website analytics exclude form contents, email addresses, account identifiers, arbitrary URL query values and email confirmation tokens. URLs exclude query strings and fragments. We separately keep only predefined referral campaign categories from tagged links: source, medium, campaign and placement. Free-text campaign values and other query parameters are excluded. Email confirmation pages are excluded. Session recording is disabled on the public website.

To resume interrupted server file uploads, we temporarily store the file contents, filename, destination, size and upload progress on our control-plane server, linked to your authenticated account. Connections use HTTPS. You can resume for 24 hours after the last upload activity by selecting the same file again. Completed temporary file contents are removed after verified delivery; inactive partial uploads expire after 24 hours and are removed by the next hourly cleanup, within 25 hours. Recovery records and completed file contents can be retained longer while an interrupted replacement is being resolved, so the original file can be restored safely; they are cleaned up after recovery. You can discard a partial upload from Files. Upload diagnostics retain byte counts, stages and request references, without filenames or file contents.

In the signed-in client panel, we also use PostHog session replay on server pages and the new-server form to understand navigation, clicks, scrolling, purchase blockers and usability problems, including mod management. Replays show game and plan choices, prices, mod names, server names and interface controls, and are associated with your internal account identifier and diagnostic request references. Your account email is visible in replays and saved on your PostHog person profile alongside your internal account identifier so our team can match a support ticket to the relevant sessions. Account names, other email addresses and email inputs, passwords, payment fields, webhook credentials, private sharing links and explicitly marked private content are masked in your browser before transmission. Console output, file contents, embedded frames and hidden or file inputs are blocked. Only public panel cover images and static image assets are allowed. We exclude authentication, account, billing, support, affiliate and invitation pages, and do not capture network request bodies, headers or console logs. Replay URLs exclude server identifiers, query values and fragments other than the selected server section. Browser replay respects Global Privacy Control and Do Not Track and uses identifiers held in memory rather than analytics cookies. Replay retention is managed separately in PostHog.

Our public audience measurement runs without analytics cookies. PostHog processes connection information, including IP address and browser information, to derive a daily identifier for audience measurement; cookieless events have the IP address stripped during ingestion. We also include an approximate country supplied by Cloudflare, without adding your IP address, city or precise coordinates to analytics properties.

To measure referrals and purchase completion, we keep a random purchase-journey identifier, a limited referral category (such as GamersWiki) and any predefined campaign categories from the first arrival in browser storage, with a 24-hour attribution window. The public website uses storage scoped to the current tab; our checkout also uses local storage so that email verification can continue in another tab. Signing out clears this checkout measurement. We transfer this context to our checkout and store it with an order so that a payment confirmed by Stripe can be linked to the purchase steps. Campaign categories also accompany public website events without adding the purchase-journey identifier to those events. PostHog receives the random identifier for purchase steps, game, plan, billing interval, referral and campaign categories, order identifier and payment amount and currency; it does not receive card details or account contact information. This measurement does not identify you across devices or connect audience identifiers across websites. We respect Global Privacy Control and Do Not Track by disabling browser analytics and creation of new purchase-journey links. Separately, we keep the selected game and plan temporarily so you can continue checkout after signing in.

The server control panel and our game servers use PostHog separately to monitor security and reliability. When the panel blocks an action (for example a request for a server that is not yours, an edit to a protected file, a refused command or a rate limit), and when purchases, payments, server setup, backups or emails fail or complete, we send the event type, your internal account identifier, the server identifier and technical details such as the affected setting name. We never send file contents, console text, passwords, payment details or your email address, and we send only a one-way hash instead of your IP address. We keep the full IP address of blocked actions in our own systems for 30 days to investigate abuse. For game servers we also record resource use and blocked network connections to detect abuse such as crypto mining or attacks.

Accounts need an email address you keep. When you sign up, sign in with Google or Discord for the first time, or change your email, we check the address’s domain against a public list of temporary email services and, through DNS, its mail servers. If we refuse an address, we keep the domain, the mail server that matched, the reason and a keyed one-way hash of the address for 90 days to count attempts and correct mistakes, and we send PostHog the domain and reason, never the address.

Creator links and the affiliate program

When you open a creator's link (an address like gamehosting.app/r/name), we record the visit so we can credit that creator: which creator, the page the link leads to, the website that sent you (its domain only), an optional campaign tag chosen by the creator and a one-way hash of your IP address. Link previews and automated visits are not recorded. We set two cookies on gamehosting.app for 60 days: one holds a random identifier for the visit, and the other holds the creator's name so we can show you their discount. These cookies do this job only; they are not used for advertising or analytics, and opening another creator's link replaces them.

If you create an account, sign in or buy within those 60 days, we link your account to that creator and record the payments you make so we can calculate their commission. Creators see you only as an anonymous code with your sign-up date, games, status and amounts; we never share your name, email or payment details with them.

If you join the affiliate program, we process your name or brand, channel, link name, the clicks, sign-ups and commissions it brings and, to pay you, your payout email, legal name, country and tax ID. The tax ID is stored encrypted. Payouts are sent through PayPal or Wise, which process the payment details under their own privacy policies. We keep payout records as long as tax and accounting rules require.

Storage and your choices

We keep information while it is needed to operate your account or subscriptions, provide support, protect the service or meet applicable obligations. Backups have a separate rotation schedule, so removal from active systems may not immediately remove a record from every backup.

You can request access, correction or deletion of your personal information by emailing contact@gamehosting.app. We may need to verify that a request comes from the account owner before making changes or sharing account information.

Changes to this policy

We will update this page as the service changes and revise the date above. Where appropriate, we will also notify affected account holders about material changes.